orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-aarch64
tilpner_ has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
tilpner has quit [Ping timeout: 244 seconds]
tilpner_ is now known as tilpner
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
<samueldr>
whew, I think I'm lucky, only one regression for "cross-system", systemd looks like it won't currently cross-compile for aarch64 on nixos-unstable
<samueldr>
regression since the last time
<samueldr>
I still haven't booted it, but it's now building the disk image, which means everything at least built
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
<samueldr>
blah, u-boot doesn't support usb on pi4 it looks like
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
<samueldr>
:/ looks like I can't figure out why u-boot won't boot a raspberry pi foundation's own kernel
<samueldr>
(on the pi 4)
<clever>
samueldr: have you tried enabling earlyprintk?
<samueldr>
that's what I'm looking for now
<samueldr>
proper serial invocation and earlyprintk
<samueldr>
but I'm still bummed by u-boot not doing usb yet
<samueldr>
hm, absolutely nothing
<samueldr>
though I'm not sure the earlyprintk invocation is right
<clever>
i tend to do it by baking the uart into the kernel at compile time
<clever>
the rpi4 also has mmio at a diff base addr
<clever>
oh, 32bit or 64bit?
<samueldr>
64 bit
<samueldr>
it seems everyone just uses "earlyprintk"
ninjin has joined #nixos-aarch64
<samueldr>
bit that could be 32 bit?
<samueldr>
but*
<samueldr>
blah, I guess I'll fall back to tianocore
<samueldr>
it started grub, but the boot actually failed after grub, but I didn't investigate at the time as it was more work than absolutely no work
orivej_ has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
<samueldr>
hmm, though I guess that also could be solved by using my mobile nixos stage-1
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
wavirc22_ has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 258 seconds]
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej_ has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
<dan_b`>
makes me wonder if the reason that setting the led trigger to "default-on" dosn't work is that i don't have that trigger available
FRidh has joined #nixos-aarch64
<dan_b`>
(side note: the charging led on this phone is the tiniest dimmest led I have ever seen, and i have to hold the phone ounder the table to be sure it's even on)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
<sphalerite>
dan_b`: wouldn't taking out the heartbeat line make it stay on?
<sphalerite>
oh, nvm, I see there's some more context here
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
<samueldr>
dan_b`: interesting, I'll try the heartbeat config on mine, maybe it's worth it to make "quirk" that sets it to default-on for `leds-ats` during stage-1, but sets it to heartbeat during hardware initialization
<samueldr>
to make a quirk*
<samueldr>
I know that for my device setting it to default-on at runtime works
<samueldr>
interesting though that yours doesn't show default-on in the triggers
<samueldr>
Thra11: it tries to build asus-flo, but only the cross-compiled bits are on hydra, there is no native armv7l
<samueldr>
so that means that the examples/demo system isn't built
<dan_b`>
I do now have default-on in the triggers, but only after I enabled CONFIG_LEDS_TRIGGER_DEFAULT_ON in config.aarch64
<samueldr>
right, I wasn't sure about the order of the events and that commit
<samueldr>
I guess what is going on is that with heartbeat the kernel refreshes it every so often
<samueldr>
while default-on it doesn't need to, it shouldn't be reset
<dan_b`>
that was my assumption. d efault-on turns it on once and then something else resets it
<dan_b`>
hearbeat makes it flicker maddeningly forever
<samueldr>
heh :) I think it'll be fixed with a quirk to set it at runtime
<samueldr>
during stage-1, once /sys/ is available
<samueldr>
and btw, the something that resets it doesn't use the kernel codepaths to configure leds-atc, as I had a kernel trace in there and nothing changed
<samueldr>
so I guess it's something that happens "out of order" that resets whatever "atc" is
<samueldr>
a real proper fix would be, at the kernel leve, to make sure it happens after whatever resets it, but... that's likely a lot of work
<samueldr>
for not much returns
<dan_b`>
yeah. i'd quite like to know what's resettting it, just because it cold also be scribbling on something else possibly more important
<dan_b`>
but not going to dig into it now
<samueldr>
I guess it would be time better put into mainlining the device, if a good chunk of its SoC is already supported
<dan_b`>
there is that too
<dan_b`>
though personally I'd like to poke at the userland a bit first
<samueldr>
definitely :)
alp has quit [Ping timeout: 246 seconds]
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]