linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, dcbw@redhat.com
Subject: Re: mac80211_hwsim driver attribute
Date: Mon, 8 Apr 2013 11:01:52 +0200	[thread overview]
Message-ID: <20130408090152.GA2818@piware.de> (raw)
In-Reply-To: <1364996685.8351.46.camel@jlt4.sipsolutions.net>

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

Hello Johannes,

Johannes Berg [2013-04-03 15:44 +0200]:
> Martin,
> 
> >  /sys/class/net/wlan0/device/driver -> ../../../../bus/pci/drivers/iwlwifi
> > 
> > But /sys/class/net/wlan1/device/ only has the default "uevent" and
> > subsystem link.
> 
> I suspect this is because there's no real "device", and therefore no
> real driver.

There are real devices (wlan0, wlan1, etc.); there is also a real
driver (mac80211_hwsim), the only thing that's a bit tricky is that
there is no real bus. My impression is that such devices might belong
to /sys/bus/platform/ ?

> We do play with device_create() in hwsim, which was likely intended to
> address something like this, but I have no idea how this should really
> work.

I figured it out, it works well now. I'll send the patch to the
lists/maintainers, and CC: Dan and you.

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

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

      reply	other threads:[~2013-04-08  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130403133802.GK2960@piware.de>
2013-04-03 13:42 ` mac80211_hwsim driver attribute Johannes Berg
2013-04-03 13:44 ` Johannes Berg
2013-04-08  9:01   ` Martin Pitt [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=20130408090152.GA2818@piware.de \
    --to=martin.pitt@ubuntu.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).