public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: The request_firmware() changes causing problems with make-kpkg
Date: Fri, 18 Jul 2008 11:21:07 -0400	[thread overview]
Message-ID: <20080718152107.GA18847@mit.edu> (raw)
In-Reply-To: <1216390475.31897.36.camel@shinybook.infradead.org>

On Fri, Jul 18, 2008 at 07:14:35AM -0700, David Woodhouse wrote:
> > Given that Ubuntu's firmware loader already tries to find firmware at
> > /lib/firmware/<kpkg> and only if that fails, to load it from
> > /lib/firmware, it seems like the obvious thing to do is to add a
> > quickie CONFIG option which changes the default setting of
> > INSTALL_FW_PATH in the top-level makefile from /lib/firwmare to
> > /lib/firmware/<kver>.
> 
> I assume those are actually the same -- <kpkg> vs. <kver>?

Yes, sorry.  I was typing too fast.

> Hm. The way we normally override such paths is with make variables.
> 
> If you really can't just fix make-kpkg to set INSTALL_FW_PATH when
> installing modules, you could export MAKEFLAGS=INSTALL_FW_PATH=/foo
> before invoking make-kpkg.
> 
> Your logic is that it's easier for you to update your config than to
> override $(INSTALL_FW_PATH) by either method above? 

Well, make-kpkg is a little easier to follow and modify than say, Red
Hat's kernel-building rpm macros (a task which I wouldn't wish on my
worst enemy, having done it once in the RHEL4 era), but that's not
saying much.  But *yes*, much easier to modify my config.  :-)

       	      	  	      	     	       - Ted

      reply	other threads:[~2008-07-18 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 11:58 The request_firmware() changes causing problems with make-kpkg Theodore Tso
2008-07-18 12:42 ` Marcel Holtmann
2008-07-18 14:14 ` David Woodhouse
2008-07-18 15:21   ` Theodore Tso [this message]

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=20080718152107.GA18847@mit.edu \
    --to=tytso@mit.edu \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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