On Mon, 2013-01-14 at 18:33 +0100, Stefan Lippers-Hollmann wrote: [...] > As mentioned in [1], I'd be willing to maintain or co-maintain a > firmware packages for carl9170, but this would need coordination (and > an ack) from you (as linux-firmware maintainer) and the kernel-team, > given that driver and firmware are both under development (and require > minimum versions of each). My preliminary packaging[2] (which I'm using > personally for quite a while) does build the cross-toolchain from > Debian's source packages for gcc/ newlib/ binutils during the package > build process[3]. This procedure is certainly not nice and needs > adapting whenever gcc changes (minor) versions, but it does build > everything from source - adding a formal sh-2/ newlib based > cross-toolchain would imho be overkill, especially as this wouldn't > be useful for anything else. As I said before, you should ask the FTP team for their interpretation of policy. Does section 2.2.1 only cover package relationships, as the second part implies, or should the first part be read literally? Am I cheating or just being pragmatic with firmware-free? Anyway, the source and binary are now in linux-firmware.git and in firmware-free (version 3.2). I have requested that firmware-free be unblocked so this will be fixed in wheezy. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports.
Attachment:
signature.asc
Description: This is a digitally signed message part