[Bug 1187616] Re: udev firmware handler needs to support multiple firmware sources for Ubuntu Touch

[Oliver Grawert]

i'm not actually sure you want to handle the device initialization at
all on the ubuntu side,

device initialization should rather be handled inside the container and
udev should only provide the device nodes and platform-api sockets for
us (see the lxc-android-config package which ships a udev rule to
provide symlinks and permission settings for android handled devices)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1187616

Title:
  udev firmware handler needs to support multiple firmware sources for
  Ubuntu Touch

Status in “systemd” package in Ubuntu:
  Fix Committed

Bug description:
  Currently, udev has a hardcoded firmware search path of /lib/firmware.
  This prevents it from being usable to load all firmware on ubuntu
  touch images, which necessarily have separate partitions for vendor-
  provided firmware vs. system-provided firmware - we can't expose both
  of these sets of firmware in /lib/firmware.  So to address this, udev
  would need to be configured to search more than one firmware path.
  This appears to be supported using a space-separated list of
  directories as the argument to --with-firmware-path.

  The logical directories to search in an Ubuntu Touch context would be
  /lib/firmware, /system/firmware, and /vendor/firmware.  If we want to
  avoid the latter two as being non-standard directories, we can use
  bind mounts or symlinks to the appropriate places and only search
  "standard" directories like /lib/firmware and /usr/local/lib/firmware.
  But at minimum we need one extra search path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1187616/+subscriptions