On Mon, May 11, 2009 at 3:22 PM, Dale <rdalek1...@gmail.com> wrote: > Paul Hartman wrote: >> On Mon, May 11, 2009 at 2:39 PM, Arnau Bria <ar...@emergetux.net> wrote: >> >>> On Mon, 11 May 2009 21:33:23 +0200 >>> Marc Blumentritt wrote: >>> >>> >>>> Hi, >>>> >>> Hi, >>> >>> >>>> when I try to compile a kernel again (meaning after compiling it and >>>> building the modules), I get this error message: >>>> >>>> hive linux # make && make modules_install && make >>>> >>> just one question about your compiling command, why make && ... && make? >>> I just do make all && make modules_install ... >>> >> >> I do: >> >> make all >> make install >> make modules_install >> make firmware_install >> >> seperately :) >> >> >> > > I do like Arnau does. It works here. What is that "firmware_install" > part anyway? I haven't ever seen that before.
Why, it installs firmware of course. :) It looks like it was added almost a year ago. Here are the patch check-in notes: From: David Woodhouse <dw...@...> To: <linux-ker...@...> Subject: [PATCH 03/18] firmware: Add 'firmware_install' make target Date: Thursday, May 29, 2008 - 4:01 am This installs all the in-kernel-tree firmware into $(INSTALL_FW_PATH), which defaults to $(objtree)/usr/lib/firmware and is intended end up in /lib/firmware for udev to find the files. This, in conjunction with the builtin-firmware support, makes it simple for drivers with associated firmware to move over to request_firmware() and give the user a choice of whether to have it built in to the kernel image or loaded separately from userspace. As with kernel header installation for userspace, it intentionally pays no attention to configuration variables -- it installs _all_ available firmware blobs, unconditionally.
