From: Johannes Berg <johannes@sipsolutions.net>
To: Martin Pitt <martin.pitt@ubuntu.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, dcbw@redhat.com
Subject: Re: mac80211_hwsim driver attribute
Date: Wed, 03 Apr 2013 15:44:45 +0200 [thread overview]
Message-ID: <1364996685.8351.46.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130403133802.GK2960@piware.de>
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.
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.
johannes
next prev parent reply other threads:[~2013-04-03 13:44 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 [this message]
2013-04-08 9:01 ` Martin Pitt
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=1364996685.8351.46.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=martin.pitt@ubuntu.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).