Petter Reinholdtsen <p...@hungry.com> writes:
> [Ben Hutchings]
>> I think the plan was that any firmware package that is available
>> during installation and that satisfies a firmware request will get
>> installed. However, I have not worked on this and I don't know what
>> has actually been implemented.
>
> At the moment hw-detect as part of d-i will look in CDROM/firmware/
> for .debs providing the files requested by a kernel module, and
> install any such .deb into the installed system. The correct .deb is
> found by unpacking the deb and looking at its content. hw-detect will
> not detect which firmware to install from APT sources, as there is
> currently no way to figure out which packages contain firmware and it
> is out of the question to unpack all packages to look for firmware
> packages.
>
> We should find a better way to identify firmware packages, allowing
> hw-detect to find the correct ones without unpacking.
>
> Happy hacking,
Isn't that a non-issue (for now)?
Here's my reasoning:
1) The non-free deb is only in apt if non-free is in sources.list.
2) AN earlier mail stated that the kernel recommends the non-free firmware deb.
3) Recommends are to be installed by default.
Shouldn't the non-free firmware deb end up installed just from that?
For the general case of firmware debs how specific do you want to
be. Should they just add "Provides: linux-firmware-x.y" or a new field
"Firmware: yes" or something? Or do you want each firmware deb to
somehow export hardware info so hw_detect can see if the relevant
hardware is present before installing firmware?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ipxb7vzd.fsf@frosties.localnet
