bennofs__ has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 240 seconds]
<samueldr> oh no
<colemickens> I just meant implementing toram would largely start with copying bits from netboot :)
<samueldr> dtb file names might change
<samueldr> allwinner files will end up renamed
<samueldr> ugh, if this happens we'll have a major breaking change in the mainline-based images :<
<colemickens> I'm a smidge confused, it seems like you linked a pretty old thread?
<samueldr> they were talking about it in the devicetree channel
<samueldr> (I hadn't seen the date)
<samueldr> hm, misinterpreted I think
<samueldr> they're thinking of moving the arm (not 64 bit) device trees to follow the same structure as arm64 did in ~2018 I think
<samueldr> same breakage, but arm (32 bit)
cole-h has quit [Ping timeout: 272 seconds]
rajivr has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
<elvishjerricco> Hm... I need to modify the cm4 dtb file... that's going to be annoying.
<samueldr> dtc can both decompile and compile a device tree
<samueldr> you can also merge trees with it
<elvishjerricco> samueldr: Yea, it's not going to be hard to change it, just annoying to automate it in nix
<samueldr> e.g. `/ { a = "b"; }; / { b = "c"; };` will compile
<samueldr> so you can chain (dtc that.dtb; cat your-additions.dts) | dtc
<samueldr> to do the jankiest edits :)
<samueldr> (oh, that's how mobile nixos will forward nodes and properties)
<elvishjerricco> the cm4 doesn't have enough BAR space for most devices, so you have to do this: https://gist.github.com/geerlingguy/9d78ea34cab8e18d71ee5954417429df
<samueldr> I see
<samueldr> I believe you can "just" overwrite the property with my method without needing to `sed` or `patch` or edit
<elvishjerricco> samueldr: Basically it's just changing the `ranges` property of some node. Can that be done without doing something like decompile+sed+recompile?
<elvishjerricco> Yea so how exactly does that work?
<samueldr> basically, you can do like in nix you can do `{ a = "a"; } // { b = "b"; }
<samueldr> but there's no "operator" for it, you just... concatenate two source files lol
<elvishjerricco> oh so i decompile the regular dtb, write a source file that sets the ranges field as I want, and then compile their concatenation?
<samueldr> the latter source file would have something like `/path/to/node { ranges = <...>; };` }
<samueldr> I'm not 100% sure it will replace the property, I haven't tried it yet
<samueldr> but I believe it will
<samueldr> I'm about to try
<elvishjerricco> I read a bit about dtbs on the rpi site, and they said that later definitions take precedence
<elvishjerricco> They also said something about "overlays" or something like that, which I think are dtbs that take precedence?
<elvishjerricco> Could I just install one of those or something?
<samueldr> yeah, I was just making sure you knew I didn't _try_ it yet
<samueldr> an overlay would work
<samueldr> I think
<elvishjerricco> So I could just use populateFirmwareCommands or whatever it is to add an overlay.
<elvishjerricco> Seems cleaner to me
<elvishjerricco> do overlays have to be enabled in config.txt, or do they just take effect if they have the right file path or something?
<samueldr> they need to be activated at some point on top of the FDT
<samueldr> likely here you need it before the kernel runs
<samueldr> so either by the pi4 firmware, or u-boot
<elvishjerricco> I do not know what that means :P
<samueldr> yeah, it's a bit annoying
<samueldr> the overlay... is just that, an overlay
<samueldr> it needs to be overlaid by something
<samueldr> it could be the pi4 firmware
<samueldr> but if you run u-boot
<samueldr> u-boot will replace the in-memory FDT with the dtb it loads from the generation
<samueldr> which means that previously applied overlay... isn't overlaid anymore!
<elvishjerricco> oh I see
<samueldr> so if you're using u-boot... you will need to do something...
<samueldr> I don't know what :)
<samueldr> you can pre-"bake" an overlay into a dtb file too
<elvishjerricco> luckily I am not using u-boot
<elvishjerricco> Ugh. Doing this smartly is starting to seem like yak shaving, since I'm not well versed in device tree stuff. Probably just going to make the change manually and refer to a prebuilt file in the nix expression.
<samueldr> that'll get you testing it faster
<samueldr> probably the better way to confirm things will work
<samueldr> just like my situation with kexec+fdt, I ended up manually making one, editing the scripts to point to that one
<samueldr> I was about to put back the task on the backburner, but my work today showed me a totally working way to handle this
ky0ko has quit [Read error: Connection reset by peer]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
cole-h has joined #nixos-aarch64
<patagonicus> Ah, ok, I was wrong, the change is not losing the extraConfig. But it looks like it's changing preferBuiltin, which also doesn't make sense.
<patagonicus> Lol, no it makes sense. Because there's a typo in the new version of the armv7l-hf-multiplatform platform: kernelPreferBuiltin got moved to linux-kernel.PreferBuiltin instead of linux-kernel.preferBuiltin.
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bpye9 has joined #nixos-aarch64
bpye has quit [Read error: Connection reset by peer]
bpye9 is now known as bpye
dtz has quit [Quit: Idle for 30+ days]
Darkmatter66 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
monk has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 264 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
zupo has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
nicoo has quit [Remote host closed the connection]
nicoo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
h0m1 has quit [Quit: WeeChat 3.0.1]
h0m1 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
superherointj has joined #nixos-aarch64
srk has quit [Remote host closed the connection]
srk has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
nicoo has quit [Ping timeout: 268 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
nicoo has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
Darkmatter66 has quit [Read error: Connection reset by peer]
cole-h has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
superherointj has quit [Quit: Leaving]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<colemickens> it'd be cool if you could make the rpi4 boot from a different netboot prefix on next boot, or when a gpio pin is down
<colemickens> I'm setting up netboot and then thinking I should be able to netboot it into either aarch64 or armv7l depending on what I want to do.
Darkmatter66 has quit [Ping timeout: 264 seconds]