| 9 Aug 2023 |
 @angryant:envs.net | This is where the device tree in that repo comes in? | 11:01:55 |
 atemu12 | Device Tree is part of the kernel | 11:02:20 |
| @angryant:envs.net | Ah. It was just weirdly called out separately in the repo description. | 11:02:42 |
| atemu12 | I'm not too knowledgable about that but AFAIK ARM devices don't have standardised device discovery via PCIe and the like, so you need to declare where which device is upfront | 11:02:52 |
| atemu12 | This bus is where x is, this memory range is mapped to device y and so on | 11:03:26 |
| atemu12 | If someone has ported Android to your device (and open sourced that), you could build that using Robotnix | 11:04:11 |
| atemu12 | Again, Robotnix "just" runs the AOSP build inside a Nix sandbox; the AOSP build still needs to work in general | 11:05:29 |
| atemu12 | We can then inject custom kernels, µG, F-droid or custom webviews into that build process in a somewhat generic way | 11:06:07 |
| @angryant:envs.net | Cool. Thanks for the overview :) My knowledge of android is quite limited and I clearly made some Linux assumptions about it. Looks like there's some unofficial progress on Lineage on the Nothing phone, so it seems promising that eventually a robotnix path will be available :) | 11:10:43 |
