On 20/05/2025 at 23:21, Holger Wansing wrote:
Pascal Hambourg <pas...@plouf.fr.eu.org> wrote (Tue, 20 May 2025 22:13:54
+0200):
On 20/05/2025 at 21:54, Holger Wansing wrote:
If I understand correctly, there are two ways, why those firmware files are
copied/installed to the target system:
- via some mechanism, when speech synthesis is used during installation (only
loose firmware files are copied, no deb installed officially the apt way),
- via firmware-detect mechanism, when involved hardware is found (officially
installing via apt).
(...)
The second case should be solid enough to rely on, so why copy the files to
/target in the first case at all?
There is no need for the (apt-un-aware) copy of the firmware files to /target,
since the usual firmware detect mechanism would take care of this (in an
apt-clean way).
Did I got the facts right?
Not entirely. Firmware files in the installer may come from four
different sources:
- loose firmware files embedded in the installer initramfs
- firmware packages retrieved from the installation media (on demand)
- firmware packages retrieved from additional media (on demand)
- loose firmware files retrieved from additional media (on demand)
Currently, all those firmware files are eventually copied to the target
system. Additionnally, firmware packages are installed on the target
system. But I think I get your point: in theory, not all loose firmware
files but only loose firmware files and packages which were retrieved on
demand need to be copied to the target system. Am I correct ?
