From: David Dillow <dave@thedillows.org>
To: David Miller <davem@davemloft.net>
Cc: brice@myri.com, sgruszka@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] myri10ge: allow per-board firmware overriding
Date: Sun, 19 Apr 2009 00:41:39 -0400 [thread overview]
Message-ID: <1240116099.5342.18.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <20090418.210927.229687293.davem@davemloft.net>
On Sat, 2009-04-18 at 21:09 -0700, David Miller wrote:
> From: David Dillow <dave@thedillows.org>
> Date: Sat, 18 Apr 2009 20:56:57 -0400
>
> > It seems like this could be done in user space, using the PCI bus ID as
> > a key to select the firmware.
>
> PCI BUS ID's are not in any way unique, you would need to include the
> PCI Domain as well.
I had that in mind, but I wasn't precise in my wording. I think that
info is there as well. IIRC, and brief glance at the code suggests, that
the uevent for the firmware requests gets the environment variable
DEVPATH that would contains that info:
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:09:01.0
Now I'm curious, so I'll probably re-verify that with udevmonitor, a
recent kernel and the typhoon driver, since it is the only thing I have
that requests firmware. But sometime after I sleep...
next prev parent reply other threads:[~2009-04-19 4:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49E7239B.4000309@myri.com>
2009-04-17 7:50 ` Stanislaw Gruszka
2009-04-18 18:36 ` Brice Goglin
2009-04-19 0:56 ` David Dillow
2009-04-19 2:36 ` David Dillow
2009-04-20 9:40 ` Stanislaw Gruszka
2009-04-20 9:55 ` Brice Goglin
2009-04-20 11:53 ` Stanislaw Gruszka
2009-04-19 4:09 ` David Miller
2009-04-19 4:41 ` David Dillow [this message]
2009-04-19 5:25 ` Kyle Moffett
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=1240116099.5342.18.camel@obelisk.thedillows.org \
--to=dave@thedillows.org \
--cc=brice@myri.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.com \
/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®