Re: Dealing with drivers that need firmware on the filesystem
- To: email@example.com
- Subject: Re: Dealing with drivers that need firmware on the filesystem
- From: Steve McIntyre <firstname.lastname@example.org>
- Date: Mon, 10 Jan 2005 17:14:12 +0000
- Message-id: <[🔎] E1Co37Memail@example.com>
- In-reply-to: <20050110165822.GB5683@suffields.me.uk>
- References: <1105238163.13044.22.camel@tyrosine> <1105238163.13044.22.camel@tyrosine> <20050109184458.GA2870@suffields.me.uk> <E1Cnj6Ufirstname.lastname@example.org> <E1Cnj6Uemail@example.com>
Andrew Suffield writes:
>On Sun, Jan 09, 2005 at 07:51:58PM +0000, Matthew Garrett wrote:
>> > You also need to turn this question around and ask it the other way:
>> > does having these drivers in contrib actually hurt anything?
>> Yes. It currently means that we can't ship an installer with support for
>> this hardware, because we don't use material from contrib and non-free
>> by default.
>Putting these drivers into main instead of contrib would not alter
>this, because it still wouldn't work without non-free. Any *practical*
Yes, quite a lot actually - we can then ask people to feed a floopy or
CD containing the vendor-supplied firmware. Do keep up...
Steve McIntyre, Cambridge, UK. firstname.lastname@example.org
"Because heaters aren't purple!" -- Catherine Pitt