linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:42:54 +0200	[thread overview]
Message-ID: <1364996574.8351.43.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130403133802.GK2960@piware.de>

On Wed, 2013-04-03 at 13:38 +0000, Martin Pitt wrote:
> Hello John, hello Johannes,
> 
> first, many thanks for this great mac80211_hwsim module! I am
> currently working on automatic test cases for the Linux network stack
> (wpa_supplicant, dhclient, NetworkManager, etc.), and this is of great
> help.
> 
> One issue is that NetworkManager does not get along with these
> simulated interfaces:
> 
> NetworkManager[24027]: <warn> /sys/devices/virtual/mac80211_hwsim/hwsim0/net/wlan1: couldn't determine device driver; ignoring...
> 
> It calls udev_device_get_driver() on the net device (wlan0) (and
> failing that, on its parent), but that fails because hwsim doesn't
> have a driver attribute. My real intel wifi does:
> 
> lrwxrwxrwx 1 root root 0 Apr  3 06:19 /sys/class/net/wlan0/device/driver -> ../../../../bus/pci/drivers/iwlwifi
> 
> But /sys/class/net/wlan1/device/ only has the default "uevent" and
> subsystem link.
> 
> Other drivers call something like pci_register_driver() or
> usb_register(), I figure those will register the driver symlink in
> sysfs? But admittedly I'm a kernel n00b, so I'd appreciate a hint
> where to look for.
> 
> Thank you in advance!
> 
> Martin



       reply	other threads:[~2013-04-03 13:43 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 ` Johannes Berg [this message]
2013-04-03 13:44 ` mac80211_hwsim driver attribute Johannes Berg
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=1364996574.8351.43.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).