From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: wireless device and udev
Date: Tue, 08 Dec 2009 20:05:04 +0000 [thread overview]
Message-ID: <20091208200504.GC16303@tuxdriver.com> (raw)
In-Reply-To: <1260300551.32227.1.camel@johannes.local>
On Tue, Dec 08, 2009 at 08:29:11PM +0100, Johannes Berg wrote:
> On Tue, 2009-12-08 at 13:52 -0500, John W. Linville wrote:
>
> > So, probably we need to map from the wlanX name to the phyY name,
> > then determine whether or not this is the first wlanX for phyY.
> > If not, then the name should be left alone.
> >
> > Now, how do we figure out how many wlanX's belong to phyY?
>
> And what's the "first" one? :)
I suppose I was figuring that if there was only one, it was the
first. :-) But you're right, I suppose that could be racy...
> ls /sys/class/net/wlan0/device/net/
>
> will give you the list of interface associated with this device.
Cool...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-12-08 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091207172616.7470ed2b@nehalam>
2009-12-08 14:29 ` wireless device and udev John W. Linville
2009-12-08 15:24 ` Marco d'Itri
2009-12-08 18:43 ` Stephen Hemminger
2009-12-08 18:50 ` Luis R. Rodriguez
2009-12-08 18:59 ` Stephen Hemminger
2009-12-08 19:51 ` Luis R. Rodriguez
2009-12-08 20:07 ` Marcel Holtmann
2009-12-08 18:52 ` John W. Linville
2009-12-08 19:29 ` Johannes Berg
2009-12-08 20:05 ` John W. Linville [this message]
2009-12-09 3:54 ` Andrey Borzenkov
2009-12-09 8:30 ` Johannes Berg
2009-12-09 15:05 ` John W. Linville
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=20091208200504.GC16303@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).