07:47 <kuruczgy[m]> mynery: If you are looking for upstream kernel and you already have an installed system, nixos-hardware recently landed x13s support: https://github.com/NixOS/nixos-hardware/pull/1444

07:47 <kuruczgy[m]> My repo also has an x13s PR open, if you are looking to build an install ISO or you want Johan's rc kernels: https://github.com/kuruczgy/x1e-nixos-config/pull/108

08:01 <mynery[m]> never knew about nixos-hardware, i will look into it

08:41 <mynery[m]> i honestly don't get how i would change the bluetooth mac there. it seems like a weirdly made module, but oh well

08:46 <travmurav[m]> this should've probably been some tool like https://gitlab.com/postmarketOS/bootmac (idk if nixos has a heuristic for installation-stable value)

08:46 <travmurav[m]> otherwise I've merged dpp based mac detection into dtbloader recently, works fine on x13s

08:49 <mynery[m]> i mean, yeah, ideally this isn't necessary, but if i do change my address, all of my pairings are probably broken

09:18 <kuruczgy[m]> Yep there's no way those hardcoded MACs are right, and indeed there doesn't seem to be a way to change them.

09:18 <kuruczgy[m]> You could do a local clone of nixos-hardware and change it there, but at that point it might be less work to just copy all the relevant parts to your own config and not use any external module.

09:19 <kuruczgy[m]> Detection of installation-stable stuff probably belongs in nixos-generate-config, but someone has to do the work to integrate the MAC detection script into it...

09:20 <travmurav[m]> fwiw I don't think we know how to access dpp from linux (I only know how to read it from efi boot services) but probably could at least generate a random one similar to bootmac

09:21 <kuruczgy[m]> Oh so how do other installers do it then?

09:22 <travmurav[m]> I believe noone has /real/ macs on x13s apart from dtbloader at this time

09:22 <travmurav[m]> either hardcoded or randomly generated

09:27 <kuruczgy[m]> Hm and how does MAC detection work on other devices? (e.g. I have seen that on the SP11 Linux also can't set the MAC by itself.)

09:27 <kuruczgy[m]> Does support in slbounce have to be added individually for all devices?

09:27 <travmurav[m]> on x1e things I think pcie card just holds it, not sure

09:28 <travmurav[m]> s/slbounce/dtbloader/ but I think most qcom things that don't have it in the card use DPP and I have that implemented, just the matter of testing and allowlisting

09:31 <kuruczgy[m]> yeah sry dtbloader ofc...

09:31 <kuruczgy[m]> I mean x13s + x1e are all the snapdragon laptops I am aware of. But good to know, one more reason to integrate dtbloader into distros. I should really try doing it at some point for NixOS...

09:32 <travmurav[m]> well there are more than that, and for older things like 7c1 that have emmc, dpp is just a partition (though dtbloader treats it the same so it's all done similar)

09:34 <travmurav[m]> kuruczgy: also jfyi you don't need dtbloader to /load/ the dtb that will be used in the end, just load /any/ dtb and then when sd-boot reloads a different one, it will call into dtbloader to get same fixups (like mac address)

09:40 <kuruczgy[m]> Hm so how does dtbloader provide the dtb exactly? I get the part that it looks through a list of dtb files on the ESP and picks one, applies various fixups, but how does it then provide it to sd-boot/Linux? (Also, how will this work when I use the boot menu to deliberately select some dtb flavor, e.g. el2 and non-el2?)

09:41 <travmurav[m]> well there is a efi DT configuration table it sets the dtb into (same way as acpi is passed to the OS) and i.e. x13s linux-mode does the same

09:41 <travmurav[m]> but

09:42 <travmurav[m]> for sd-boot it's a bit different as there is a special efi protocol for dt fixups, so sd-boot erases whatever dtbloader loaded and replaces it with dtb it wants, then calls into dtbloader and asks it to run fixups on the new dtb

09:42 <travmurav[m]> so on x13s you cold have like linux-mode loads -> dtbloader replaces -> sd-boot replaces

09:43 <travmurav[m]> for el2 it will be more complicated I guess but as long as in the end your sd-boot just has "devicetree blah-el2.dtb" it will just load it and ask dtbloader to fixup the mac, it should be fine

09:46 <kuruczgy[m]> Yeah but I also want dtbloader for its device detection functionality, so I can't really provide a dtb from sd-boot since I don't know what device we are on. (Well okay this is only important for the installer (which on NixOS is grub, I hope this all also works with grub), in theory you could set the dtb as an "installation-stable value", but if you need dtbloader anyway why not just use it to detect the device on every boot.)

09:46 <travmurav[m]> yes that's a problem indeed to interop with el2/slbounce

09:46 <travmurav[m]> as in, as long as you ignore that case, you just omit "devicetree" in sd-boot and it will use what dtbloader loaded

09:47 <travmurav[m]> but if you want el2 it's kind of an ordering problem as dtbloader can't know what dtb to load before you picked the mode, and there is nothing about devicetree-dir for more close cooperation between sdboot and dtbloader

09:49 <travmurav[m]> grub would also be fine as long as you can load the dtbloader.efi somehow before it

09:59 <travmurav[m]> oh lol lol dpp on old winphone is literally fat, not some custom "fs" they have nowdays

10:00 <travmurav[m]> I hope I don't ever need to deal with that in dtbloader haha