mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, jonathan@jonmasters.org,
	Shaohua Li <shaohua.li@intel.com>,
	greg@kroah.com, arjan@infradead.org
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
Date: Thu, 03 Jul 2008 09:54:49 -0400	[thread overview]
Message-ID: <76430.1215093289@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 03 Jul 2008 15:03:32 +0200." <1215090212.9721.91.camel@linux.site>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

On Thu, 03 Jul 2008 15:03:32 +0200, Kay Sievers said:
> On Thu, 2008-07-03 at 13:45 +0100, David Woodhouse wrote:
> > On Thu, 2008-07-03 at 14:41 +0200, Kay Sievers wrote:
> > > Headers are not needed for bootup, firmware might be. :) But /usr
> > > might be on a different partition/disk/storage at the time we need it,
> > > right?
> > > 
> > > I would say /usr/lib/firmware should not even exist, udev does
> > > intentionally not even look there.
> > 
> > Not /usr/lib/firmware. Currently, when you run 'make firmware_install',
> > it gets installed to usr/lib/firmware _within_ the kernel build
> > directory. And you're expected to copy it from there (or override with
> > 'make INSTALL_FW_PATH=/lib/firmware firmware_install')
> 
> Ah, ok. So by default "make modules_install" installs in the rootfs, but
> "make firmware_install" installs in the build directory? Hmm ...

The *odd* part is that make firmware_install isn't symmetric - it drops it
in $O/usr/lib/firmware, but you don't want the final result in /usr/lib,
you want it in /lib.  Maybe it should be dropping it in $O/lib/firmware
instead?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2008-07-03 13:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  1:32 Valdis.Kletnieks
2008-07-03  1:43 ` Andrew Morton
2008-07-03  6:17 ` Tigran Aivazian
2008-07-03  6:35   ` Valdis.Kletnieks
2008-07-03  6:44     ` Tigran Aivazian
2008-07-03  9:23       ` David Woodhouse
2008-07-03 10:17         ` Valdis.Kletnieks
2008-07-03 10:30           ` David Woodhouse
2008-07-03 11:34             ` Valdis.Kletnieks
2008-07-03 12:21               ` David Woodhouse
2008-07-03 12:41                 ` Kay Sievers
2008-07-03 12:45                   ` David Woodhouse
2008-07-03 13:03                     ` Kay Sievers
2008-07-03 13:26                       ` David Woodhouse
2008-07-03 13:54                       ` Valdis.Kletnieks [this message]
2008-07-03 15:23                         ` David Woodhouse
2008-07-03 13:48                 ` Valdis.Kletnieks
2008-07-03 10:22         ` Kay Sievers
2008-07-03 10:42           ` David Woodhouse
2008-07-03 11:32             ` Kay Sievers
2008-07-03  9:24       ` Giacomo A. Catenazzi
2008-07-03 13:56         ` Arjan van de Ven
2008-07-03 15:54           ` David Woodhouse
2008-07-03 16:22             ` Giacomo A. Catenazzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76430.1215093289@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=jonathan@jonmasters.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=tigran@aivazian.fsnet.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®