Hi Arnaud, Arnaud Ferraris <aferra...@debian.org> (2025-02-04): > My apologies for not posting to debian-boot@, I would have expected > such information to be available either in the policy or developer's > reference but couldn't find much on the topic of udebs there.
I'm happy to support the addition of such mention where you think you should have found it. As a general rule, if I'm going to operate in a particular Debian area, I tend to put the relevant team(s) in the loop anyway. :) > Now let me give you a bit more context about this: here are the source > packages generating udebs I've recently uploaded to NEW: > * qrtr (generating udebs for libqrtr1 and qrtr-tools) > * protection-domain-mapper > * rmtfs > * tqftpserv > > Please note the latter 3 depend on libqrtr1. OK, thanks. In the end, having packages around is not going to be sufficient anyway, they would need to be made available in this or that image, and integrated in some way (hardware detection → software dance at the right moment(s)), maybe it's already on your todo list? In any case, it'd be nice to have some kind of plan/picture on how things would fit together. It's not common (as far as I can remember) to have extra tools for hardware support (firmware packages being a rather separate topic). > Those udebs were created per request (see #1076725 and #1076726) in > order to allow installer support for Qualcomm-based devices, > especially recent Snapdragon laptops. Alright, maybe #1091799 is an example of such hardware? Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
