<samueldr>
we were previously setting it on the kernel command-line
<pbb>
so you would need both to actually do something?
<pbb>
or is one of them enough?
<samueldr>
but it's not great because of reasons that we've seen in the PR you rebased
* samueldr
re-opens the PR to remember what failed
<pbb>
let me rephrase the question: what would be the best way to set the gpu memory size / cma (assuming that's essentially the same thing) when using u-boot?
<pbb>
I would like to update the wiki with a new example using dtmerge and u-boot
<pbb>
(for enabling gpur
<pbb>
*gpu)
<samueldr>
I'm pretty sure you don't set it at all on Linux's side
<samueldr>
I'm not sure if gpu_mem from the firmware ends up used though
<samueldr>
that's a raspberry pi specific that I don't know
<samueldr>
clever maybe knows, depending on whether earlier raspberry pis did the same
<samueldr>
(though clever might not be around)
<pbb>
okay, thanks. let's see if someone else knows
<samueldr>
though, now that cma= is not set on the command-line, it will use the defaults from the platforms
<samueldr>
which the device trees can set
<samueldr>
AFAIUI we now shouldn't touch nor recommend touching the cma parameter by default
<samueldr>
I guess if the user needs it for *reasons* they can
veleiro has quit [Remote host closed the connection]
Asmadeus has joined #nixos-aarch64
wavirc22_ has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 256 seconds]
<gchristensen>
guh this machine won't boot b/c its clock is skewed and my cert is "expired" or not yet valid
lgcl has joined #nixos-aarch64
<simpson>
Hm, a curious puzzle.
cole-h has joined #nixos-aarch64
<gchristensen>
ah ha, I can ask ipxe to ntp before chaining to https
alpernebbi has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
Cadey is now known as Guest57365
Guest57365 has quit [Killed (egan.freenode.net (Nickname regained by services))]
<DigitalKiwi>
i have a laptop that keeps resetting the time to the distant future :/
<DigitalKiwi>
Wed Jan 1 12:08:32 AM UTC 2098
<DigitalKiwi>
think it maybe needs a new bios battery? lol
<simpson>
Possibly.
<DigitalKiwi>
why's it go to the future though shouldn't it got to 1970? maybe it's too powerful
<FireFly>
huh, good question
<FireFly>
weird timestamp
alpernebbi has quit [Quit: alpernebbi]
<lgcl>
i am trying to boot get a rockpro64 setup with an encrypted root fs. i have an unencrypted fat /boot and see the boot menu and u-boot retrieving the kernel/initrd, but after starting the kernel, the attached screen just turns off. does anyone has an idea what i might be doing wrong?
<flokli>
gchristensen: ipxe doesn't write to hwclock, only to ipxes clock.
<flokli>
so you might still want to disable resolved, so timesyncd can resolve the NTP server address :-P
<lgcl>
Ke: yes, i see a u-boot version number, boot menu and messages that kernel/initrd are being retrieved. the last message is "Starting kernel ..." and then the screen turns off
Darkmatter66 has joined #nixos-aarch64
<clever>
pbb: the firmware bootloader will use gpu_mem to heavily patch start.elf and determine where to load it into ram
<clever>
pbb: so gpu_mem has major effects on the system, before it even looks for uboot
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<Ke>
heh, just heard a nice idea of using trustzone to isolate spi-nor from Linux and use that for secure boot write protect
<clever>
Ke: in the case of the rpi, the dram controller doesnt have the right features to implement trustzone correctly
<Ke>
heh, what about rk3399?
<clever>
not famaliar with that one
Darkmatter66 has quit [Ping timeout: 272 seconds]
andi- has quit [Quit: WeeChat 2.8]
andi- has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]