Handling hardware solely from the android img files
The Ubuntu Touch rootfs should be as generic as it can get by moving all hardware specific files into the android system image.
This also requires having a mechanism to overlay the hardware specific device configurations inside the rootfs on boot (by copying or by bind mounting the properly configured files on top from /system/...)
Blueprint information
- Status:
- Not started
- Approver:
- Michael Frey
- Priority:
- Undefined
- Drafter:
- Oliver Grawert
- Direction:
- Approved
- Assignee:
- Oliver Grawert
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
currently used files:
* /lib/udev/
* /lib/modules (currently bind-mounted from /system/lib/modules by the touch initrd script)
* /usr/share/
* /etc/ubuntu-
* /usr/share/
* /usr/share/
* /etc/init/
* everything related to bluetooth ... while we have some basic bringup running inside the container we still need upstart jobs for bringing up per-device BT configs on the Ubuntu side)
* /usr/share/
---
A proposal:
Ship an ubuntu "Shadow filesystem" in the android system.img that is used to overlay the files on the rootfs and processed from the initrd script with something similar to:
for file in $(find /system/
target=$(echo $file|sed -e 's/^/system/
source=$file
# make sure target files and dirs exist etc ...
mount --bind $source $target
done