[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <483F1232.4010003@linux.intel.com>
Date: Thu, 29 May 2008 13:29:38 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Greg KH <greg@...ah.com>
CC: David Woodhouse <dwmw2@...radead.org>,
James.Bottomley@...senPartnership.com,
ksummit-2008-discuss@...ts.linux-foundation.org,
David Miller <davem@...emloft.net>,
linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the
kernel.
Greg KH wrote:
>> And at that point I'd like to remove them completely, to a separate git
>> tree and tarball. Those who really want to build them in to their static
>> kernel would still be able to, but it wouldn't be the default behaviour.
>
> This I disagree with. Leaving it in a single directory makes it easier
> for some distros to patch it away to apease their feelings about the
> issue. But for some of use, we like the firmware in our kernels, it
> makes it easier to boot for one, and we don't have to deal with
> different firmware packages. So I say leave them in, with the option to
> get them elsewhere, like you are doing.
>
I very much would like to see a kernel-firmware or something tarbal that contains
a copy of all relevant "freely distributable" firmware, that users can just install
independent of the actual kernel version (and that kbuild would just pick up somehow).
That way we can deal with a lot more firmware without having to pollute the kernel / kernel release process
(after all, the timing is different in terms of releasing) while making it easy
to get the lot of it.
Now.. of course what "freely distributable" means is a huge debate. I don't care ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists