Public bug reported:
In LP:1849493 we enabled support for CONFIG_ANDROID_* on the gcp kernels
to support Anbox Cloud. However checking on the latest rolling kernel on
GCP (5.8.0-1038-gcp #40~20.04.1-Ubuntu ) gives
morphis@anbox0:~$ cat /boot/config-5.8.0-1038-gcp | grep CONFIG_AND
# CONFIG_ANDROID is not set
This is a regression and already affects customers of Anbox Cloud which
intend to deploy on GCP and currently fail as the binder and ashmem
kernel modules are missing. From the git history I wasn't able to figure
out where the options got dropped.
The following options are what we need
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=m
CONFIG_ANDROID_BINDER_DEVICES=""
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
CONFIG_ASHMEM=m
These options should be set by default in all our cloud kernels,
regardless which Ubuntu version.
Can we get some regression testing in place for this too?
Thanks!
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937987
Title:
Latest GCP kernel has Android related config options disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1937987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
