Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: John Ranson <ranson@analager.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Unable to load iwlagn module: Failed to register hw (error -17)
Date: Wed, 15 Jul 2009 18:21:20 +0200	[thread overview]
Message-ID: <1247674880.10754.22.camel@johannes.local> (raw)
In-Reply-To: <1247674573.17896.1989.camel@rc-desk>

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

On Wed, 2009-07-15 at 09:16 -0700, reinette chatre wrote:

> > -EEXIST should only happen if something has already claimed something in
> > sysfs, but not with netdevs (i.e. wlan0 would just be renamed to wlan1)
> > and phy0 is numbered all the time so that can't be it either. I don't
> > know.
> 
> fyi ... I based my response on register_netdevice() being able to return
> -EEXIST at the time it checks for the existence of "name".

Yes, it does that, but we don't ask it for a fixed name -- we allocate
"wlan%d" and in the same rtnl-locked section register it, so we should
always get a new number and be able to register that number.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-07-15 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  4:25 Unable to load iwlagn module: Failed to register hw (error -17) John Ranson
2009-07-15 16:02 ` reinette chatre
2009-07-15 16:11   ` Johannes Berg
2009-07-15 16:16     ` reinette chatre
2009-07-15 16:21       ` Johannes Berg [this message]
2009-07-15 16:25     ` Luis R. Rodriguez
2009-07-16  3:58       ` John Ranson
2009-07-16 16:13         ` Luis R. Rodriguez
2009-07-26  2:41           ` John Ranson

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=1247674880.10754.22.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ranson@analager.net \
    --cc=reinette.chatre@intel.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