| 15 Aug 2021 |
 danielrf | samueldr: something like that, I just know that each new device comes with a bunch more modules than before--but I'm not sure when the switch over to GKI will be "complete" | 23:29:18 |
| danielrf | I haven't followed it too closely | 23:29:26 |
 pie_ | im not entirely afraid of kernel dev but i certainly dont have much experience with it | 23:29:49 |
 samueldr | my experience with GKI is that it's making OEM not provide all the modules source code, sometimes at all, sometimes in usable manner | 23:30:14 |
| danielrf | pie_: So there's two things here: 1) build kernels for generic emulation devices (and potentially switch the way we build kernels) and 2) build the android automotive emulator (https://source.android.com/devices/automotive/start/avd/android_virtual_device) | 23:30:59 |
| danielrf | those are hopefully two independent tasks | 23:31:44 |
| pie_ | what have i gotten myself into | 23:31:50 |
| danielrf | pie_: :D | 23:32:08 |
| danielrf | Ah, here's some automotive-specific instructions for the kernel: https://source.android.com/devices/automotive/start/avd/android_virtual_device#build-an-avd-kernel | 23:33:02 |
| pie_ | the question is really how dependent the bluetooth passthrough is on the automotice | 23:43:14 |
| pie_ | ´´´
AVD kernels are similar to other Android kernels in that all are pre-built images. Normally, you can use the standard goldfish kernel pre-built images as is from each Android release.
To experiment with kernel changes:
´´´ | 23:43:53 |
