| 12 Feb 2025 |
 waltmck | how you told me to do it was to add my device to supported_devices and run the update script | 22:38:24 |
| waltmck | there's a better way? | 22:38:28 |
 atemu12 | Someone added a handy CLI flag for that very recently | 22:38:31 |
| atemu12 | Only the device dir updater | 22:38:48 |
| atemu12 | You could update repo too but you don't have to | 22:39:12 |
| waltmck | so I just run update_device_dirs.py instead of update.sh? | 22:39:31 |
| atemu12 | Yes but the -s flag is easier | 22:39:51 |
| atemu12 | And the update script sets up some smaller things you probably want such as TMPDIR | 22:40:35 |
| waltmck | got it I see the flag, coolio | 22:41:10 |
| waltmck | I'll try that | 22:41:13 |
| waltmck | it looks like according to lineage's naming conventions there should be a https://github.com/LineageOS/android_kernel_google_lynx but there isn't | 22:50:13 |
| 13 Feb 2025 |
| atemu12 | Check lineage.dependencies in the device dir | 10:06:25 |
| atemu12 | The Google device kernels might be in the AOSP tree though | 10:06:52 |
|  @pshirshov:matrix.org left the room. | 14:11:50 |
 Tristan Ross | Android's tools and stuff are starting to support aarch64 I heard. There's work being done to enable this in nixpkgs. It might become possible to build AOSP on aarch64 with Nix not too long from now. | 15:50:50 |
| atemu12 | Cool | 15:58:01 |
| atemu12 | There are a few x86 assumptions in robotnix but those should be easy enough to strip out | 15:58:38 |
