Petter Reinholdtsen <p...@hungry.com> (2016-01-10): > [Cyril Brulebois] > > Probably. I read your previous mail as “let's use isenkram-cli from > > d-i”, which we can't for the reason I mentioned. Reusing its logic > > (contents and/or shell scripts) could make sense though. > > One idea is to create a new isenkram-udeb with the relevant parts, and > make it a dependency of hw-detect, and either call > isenkram-autoinstall-firmware from hw-detect to install the wanted > firmware packages, or provide a script to list relevant firmware > packages and their sections for hw-detect to show to the user. Not > quite sure which approach is best.
I haven't thought much about how to approach this, but I had the isenkram-udeb part in mind as well: probably the easiest/best way to share the logic here. > To install firmware in /target/, I suspect using the tasksel tasks provided > by isenkram-cli might be a good approach, and for those to work we just need > to install isenkram-cli in /target/ before calling tasksel, so the need for > an isenkram-udeb package is only to handle firmware loading before creating > /target/. I'm not sure there's a need for a task; we have apt-install which handles a queue (/var/lib/apt-install/queue) until apt has been configured in /target; see apt-install in src:debian-installer-utils. We could also just copy firmwares from d-i to /target using a finish-install script. I haven't checked what isenkram-cli does or how; I'm just mentioning various ideas. Mraw, KiBi.
signature.asc
Description: Digital signature
