ryantrinkle has quit [Read error: Connection reset by peer]
Acou_Bass has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 260 seconds]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
cirno-999 has quit [Ping timeout: 256 seconds]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
monk has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
Darkmatter66 has quit [Ping timeout: 240 seconds]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
srk has quit [Remote host closed the connection]
srk has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
cornu has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
Thra11 has quit [Ping timeout: 256 seconds]
lgcl has quit [Ping timeout: 260 seconds]
ryantrinkle has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
veleiro has quit [Ping timeout: 272 seconds]
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
<samueldr>
good news, there's no issues with kexec and the pinephone, I stupidly forgot to configure it to know about the LUKS container in the on-system configuration
<flokli>
clever: rpi question: how does dtparam=spi=on in config.txt work? I assume that's read by the GPU blob, too?
ryantrinkle has quit [Read error: Connection reset by peer]
<flokli>
uboot seems to have all these "firmware provided FDT" comments, so I'm scared
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
<samueldr>
flokli: that's basically it, the firmware applies overlays as needed
ryantrinkle has quit [Read error: Connection reset by peer]
<samueldr>
so you can get a different FDT according to what you pass to config.txt
<samueldr>
which is a perfectly cromulent way to implement device trees and features
<samueldr>
it's basically as if on x86 your bios sent different ACPI table data according to which features you turned on/off
ryantrinkle has joined #nixos-aarch64
<flokli>
but the dtbs are still coming from /boot?
ryantrinkle has quit [Read error: Connection reset by peer]
<flokli>
I mean, how can the firmware apply dtbs before uboot?
<flokli>
or does it simply set some magic bits somewhere, and u-boot looks at them to "configure" these dtparams?
<flokli>
/boot/firmware contains no .dtb files, only /boot/nixos/*-dtbs/ (which is on a separate partition, and the firmware blob can't read that)
<samueldr>
the firmware will load an initial FDT
<flokli>
firmware=the gpu blob?
<samueldr>
and has overlays it knows about
<samueldr>
not sure where it is, but I think it's part of the blob on the SD card
ryantrinkle has joined #nixos-aarch64
<samueldr>
and u-boot is too late to configure those dtparams
ryantrinkle has quit [Read error: Connection reset by peer]
<samueldr>
well, it could do something and overlay the equivalent itself
<samueldr>
but not "magically" as config.txt does
<samueldr>
(see: vendor proprietary bits again being harmful)
<flokli>
I'd like to provide my own overlay(s) via hardware.deviceTree.overlays
<flokli>
but if uboot can't load device trees for the kernel, I'm probably out of luck
<samueldr>
I still haven't taken time to look at the nixos deviceTree.overlays stuff
<samueldr>
u-boot will load device trees for the kernel
<flokli>
ah
<samueldr>
anyone at any time can change the FDT blob in memory
<flokli>
so I /can/ provide device tree overlays via NixOS
<samueldr>
assuming they apply to the kernel, yes
<samueldr>
to the dtb files*
<flokli>
yes they do
<flokli>
let me quickly verify this
<samueldr>
btw, I prefer using FDT for the in-memory blob, then dtb only for the files
<flokli>
hm?
<samueldr>
you load the device tree in memory as the FDT (flattened device tree) from a dtb file
ryantrinkle has joined #nixos-aarch64
<samueldr>
terminology is annoying with device tree :)
<flokli>
ah. sorry
<samueldr>
no worries, I'm stating it so hopefully we can start using the same terms
ryantrinkle has quit [Read error: Connection reset by peer]
<samueldr>
AFAIUI it's they are the proper way to use them
<samueldr>
like: "you apply the device tree overlays (dtbo files) to the FDT or build them to a pre-compiled dtb file"
<samueldr>
the FDT is more than the .dtb files; it is meant to be edited in-place as needed
<samueldr>
like the proprietary bits of the raspberry pi does
<flokli>
makes sense
ky0ko has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
<flokli>
ouch, the bcm2708_spi driver isn't in mainline so far?
ryantrinkle has quit [Read error: Connection reset by peer]