linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: absolute firmware paths
Date: Fri, 04 Jul 2008 08:30:25 +0000	[thread overview]
Message-ID: <1215160225.23812.8.camel@violet.holtmann.net> (raw)
In-Reply-To: <200806302204.05544.seb@highlab.com>

Hi Sebastian,

> > Also since you are talking about development here. So what has this to
> > do with the upstream kernel and why do we need it there. You can always
> > install your own firmware.sh file that does special things in case files
> > are requested for your driver. And actually you don't even have to
> > overwrite firmware.sh for it. Simply install a new udev rule for only
> > that driver.
> 
> Yeah, our own udev rule and our own firmware.sh is one of the options
> we're considering.  It'd be easy to do.  I just think it's a generally
> good idea and I thought that upstream udev might be interested.

using your own firmware.sh and an udev rule is so simply. So don't
bother the kernel with any changes. Also the kernel does not make policy
decisions. The /lib/firmware location is a userspace policy.

Regards

Marcel



  parent reply	other threads:[~2008-07-04  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  4:04 absolute firmware paths Sebastian Kuzminsky
2008-07-01  5:20 ` Marcel Holtmann
2008-07-04  3:04 ` Sebastian Kuzminsky
2008-07-04  4:50 ` Marcel Holtmann
2008-07-04  6:20 ` Sebastian Kuzminsky
2008-07-04  8:30 ` Marcel Holtmann [this message]
2008-07-05 16:13 ` Sebastian Kuzminsky
2008-07-05 17:24 ` Marcel Holtmann
2008-07-05 18:42 ` Sebastian Kuzminsky

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=1215160225.23812.8.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).