Re: Building vanilla kernel .debs
Hi,
On Mon, Oct 26, 2009 at 02:58:08PM +0100, Marc Haber wrote:
> On Tue, Oct 20, 2009 at 01:42:02PM +0200, maximilian attems wrote:
> > On Tue, Oct 20, 2009 at 11:35:01AM +0200, Marc Haber wrote:
> > > So the most current version is in the upstream kernel git?
> >
> > kernel guys are currently in the summit so latest 2 patches
> > related to fakeroot didn't yet land in kbuild git and linux-next.
> > http://marc.info/?l=linux-kbuild&m=125561337922614&w=2
> > http://marc.info/?l=linux-kbuild&m=125561358622933&w=2
>
> After applying these two patches to scripts/package/builddeb from
> current upstream kernel git (they don't apply to 2.6.31.4), make
> deb-pkg KBUILD_PKG_ROOTCMD="fakeroot -u" produces packages (which I
> haven't tested yet). Thanks.
Is it a feature that the linux-firmware package doesn't have the
upstream kernel version in its name?
$ make deb-pkg
(...)
dpkg-deb: building package linux-firmware-image' in ../linux-firmware-image_2.6.31.4.20091026.4_all.deb'.
dpkg-deb: building package linux-image-2.6.31.4-zgws1' in ../linux-image-2.6.31.4-zgws1_2.6.31.4.20091026.4_i386.deb'.
I could imagine that, a driver in kernel 2.6.x would need different
firmware than the same driver in kernel 2.6.y, where it would be very
helpful to have multiple firmware packages installed. Does the
firmware infrastructure cater for this need?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
Reply to: