ubuntu-phone team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

Hi Florian,

On Sat, Jan 18, 2014 at 02:50:54PM +0100, Florian Will wrote:
> 2014/1/16 Chris Wayne <chris.wayne@xxxxxxxxxxxxx>

> > After some digging around the system, the following types of
> > device-specific files are currently living in our rootfs:

> >    - upstart jobs in /etc/init
> >    - udev rules (in /etc/udev/rules.d and /lib/udev/rules.d)
> >    - ubuntu-touch-session configs (basically just telling the system the
> >    number of pixels in a GU IIRC) (in /etc/ubuntu-touch-session.d/)
> >    - lxc container configs (in /var/lib/lxc/android/pre-start.d and
> >    /usr/lib/lxc-android-config/)
> >    - powerd configs (/usr/share/powerd/device_configs/)
> >    - apparmor policies (/usr/share/apparmor/hardware/)
> >    - binaries/scripts (i.e. /usr/bin/brcm_patchram_plus)
> >    - ofono plugins/configs (not in the image now, but there will likely
> >    be device/modem-specific files for these in the future AIUI)

> I realize this won't help with finding a solution, but for completeness
> sake, let me add three more things to this list that I (as a porter) change
> in the rootfs:

Thanks for the input, that's very helpful.

>  * Alsa ucm files for msm-audio in /usr/share/alsa/ucm (I'm not sure if the
> same files can be used for all devices using the msm chipset, may need to
> be adapted for each device?)

I can't speak to these files.  Perhaps Mathieu knows, or someone else on the
list.

>  * /etc/fstab to specify the system partition device node because
> auto-detection fails for some devices (possible fix is
> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1199084
>  )

Yes, this should be fixed in the initramfs, not by patching /etc/fstab.  In
fact, for production devices, I expect that the system partition will be the
root filesystem, so this would certainly need to be handled from the
initramfs...

>  * /home/phablet/.display-mir to enable Mir by default (I've seen a script
> that does this for official devices, but the device names are hard coded so
> a rootfs change is needed anyway if you don't want surfaceflinger)

Glad to hear that Mir is working well for you on your port!

In the long term, we should sunset surfaceflinger support entirely and focus
100% on Mir; at that point there should be no need to modify the rootfs to
trigger its use because it will be the only thing we use.

I understand that supporting unity on surfaceflinger is already a burden
today.  I imagine we'll drop it entirely before 14.04.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@xxxxxxxxxx                                     vorlon@xxxxxxxxxx

Attachment: signature.asc
Description: Digital signature