Actually the best way would be to unpatch our packages and follow the
upstream way of installing this particular firmware.

Or

Keep our current patches against ubuntu's alsa-tools
(firmware_locations.patch) and medibuntu's alsa-firmware
(02_move_hdsploader.patch) in place and use the previously proposed
patch against our kernels.

Both ways are pretty trivial but I'd like to know why alsa-tools was patched in 
the first place?
Maybe should we dig the debian bugtracker for a clue.
It seems it was patched to move the firmwares from an old location 
(/usr/share/alsa/firmware) to a new one (/lib/firmwares) to follow some kind of 
new policy but AFAIK upstream vanilla alsa-tools (at least as of 1.0.20) now 
installs the firmwares in both places!

I'll dig up a bit and propose a patch to unpatch (yes!) our tools if
there is no serious drawback.

-- 
rme hdsp firmware is not loaded at system startup
https://bugs.launchpad.net/bugs/222663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to