Re: Building vanilla kernel .debs
hello David,
I have a question on howto ship firmware build out of
make deb-pkg in linux-2.6.
On Mon, 26 Oct 2009, Ben Hutchings wrote:
> On Mon, 2009-10-26 at 21:27 +0100, Marc Haber wrote:
> > Hi,
> >
> >
> > Is it a feature that the linux-firmware package doesn't have the
> > upstream kernel version in its name?
>
> Possibly not.
>
> > $ 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.
>
> The linux-firmware repository
> <git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git>
> contains multiple versions of some firmware for just this reason.
> However, Linux source trees do not.
>
> > Does the firmware infrastructure cater for this need?
tried to pass INSTALL_FW_PATH to modules_install call in
scripts/packages/builddep, but this is happily ignored there.
is it an anachronism that the INSTALL_FW_PATH defaults to
$(INSTALL_MOD_PATH)/lib/firmware and not
$(INSTALL_MOD_PATH)/lib/firmware/$(KERNELRELEASE)/
kind regards
max
Reply to: