linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Adam Turk <bofh1234@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: kernel 2.6.25-rc1 and no /dev/rt73usb
Date: Fri, 15 Feb 2008 22:24:33 +0100	[thread overview]
Message-ID: <200802152224.34055.IvDoorn@gmail.com> (raw)
In-Reply-To: <BAY101-W378CC14C633084DBF091A6C8260@phx.gbl>

On Friday 15 February 2008, Adam Turk wrote:
> 
> > You are completely missing the point of the concept "modules",
> > the module rt73usb is intended to support devices with the rt73 chipset.
> >
> > The rt73usb driver registers the device and creates an network interface
> > inside the kernel. This interface is visible to you as user. The name of this
> > interface is wlan, depending on the number of wireless network cards in
> > your system the interface number is attached to it so in your case wlan0.
> 
> Yep, I could be missing the concept of modules entirely.  
> 
> The driver I was using before had the interface name of rt73.  When I see 
> usbcore: registered new interface driver rt73usb

Seriously, I wonder with what driver you managed to pull that off.
As far as I know there is no rt73 driver that registers an interface called rt73.
Neither the Ralink drivers, the rt73 legacy driver or the rt73usb driver ever
did such a thing.

Granted the name did change. The Ralink driver and early legacy drivers
did create the interface with the name "rausb", this is still not the same
as "rt73".

Additionally:
> usbcore: registered new interface driver rt73usb

Using a different rt73 driver would also produce this line (replacing rt73usb
with rt73 or whatever the name of the driver was).
But like I said earlier, I know of no rt73 driver that registered a network
interface named rt73. It is either "wlan" or "rausb". Unless off course you
edited the /etc/modprobe.conf file to load the driver with the rt73 interface name,
but that can be considered "user configuration".

Ivo

  parent reply	other threads:[~2008-02-15 21:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAY101-W101FB386E1EF7402881964C8260@phx.gbl>
     [not found] ` <20080215050358.GA10363@gondor.apana.org.au>
2008-02-15 20:27   ` kernel 2.6.25-rc1 and no /dev/rt73usb Adam Turk
2008-02-15 20:33     ` John W. Linville
2008-02-15 20:46     ` Ivo van Doorn
2008-02-15 21:08       ` Adam Turk
2008-02-15 21:15         ` Luis Correia
2008-02-15 21:24         ` Ivo van Doorn [this message]
2008-02-15 21:53           ` Adam Turk
2008-02-16  0:22     ` Herbert Xu
2008-02-14 18:14 Adam Turk
  -- strict thread matches above, loose matches on Subject: below --
2008-02-14  1:14 Adam Turk
2008-02-14  1:25 ` Pavel Roskin
2008-02-14  2:28   ` Adam Turk
2008-02-14  9:49     ` Ivo Van Doorn
2008-02-14 13:56       ` John W. Linville
2008-02-14 17:52         ` Chatre, Reinette
2008-02-14 14:31       ` Johannes Berg
2008-02-14 23:41         ` Herbert Xu

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=200802152224.34055.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=bofh1234@hotmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).