Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

2005-04-05 Thread Arjan van de Ven
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote: > On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote: > > I don't think you did get a rejection, a few people said that _they_ > > weren't going to do it, but if you want to then go ahead. I think people > > are just fed up of pe

Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

2005-04-05 Thread Arjan van de Ven
> > Second step is to make the built-in firmware a > > config option and then later on when the infrastructure matures for > > firmware loading/providing firmware it can be removed from the driver > > entirely. > > I think the infrasturcture is quite mature. We have a lot of drivers > that requi

Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

2005-04-05 Thread Arjan van de Ven
> > I agree. And that really doesn't need a lot of infrastructure, > > basically just a tarball that unpacks to /lib/firmware, maybe a specfile > > and debian/ dir in addition. > > > At the moment there is -zero- infrastructure that would allow my tg3 to > continue working, when I upgrade to a

Re: [MeeGo-dev] [Pkg-meego-maintainers] Packaging the MeeGo stack on Debian - Use the name ?

2010-12-10 Thread Arjan van de Ven
On 12/10/2010 4:38 AM, Julian Andres Klode wrote: On Fr, 2010-12-10 at 11:24 +, MJ Ray wrote: Ibrahim Haddad wrote: We would ask you to move away from using {M,m}-e-e-{G,g}-o or any subset of those letters or sounds in that order, alone or in combination with other letters, words or marks t