From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
Piter PUNK <piterpunk@unitednerds.org>,
linux-wireless@vger.kernel.org
Subject: Re: rt2500usb vs rt73usb
Date: Tue, 6 Jan 2009 15:27:40 -0500 [thread overview]
Message-ID: <20090106202740.GE3544@tuxdriver.com> (raw)
In-Reply-To: <1230502494.25726.26.camel@dv>
On Sun, Dec 28, 2008 at 05:14:54PM -0500, Pavel Roskin wrote:
> On Sun, 2008-12-28 at 10:34 +0100, Ivo van Doorn wrote:
> > On Sunday 28 December 2008, Piter PUNK wrote:
>
> > > If the those 148f:2573 USB devices doesn't exists or
> > > if they exists and works fine with rt73usb, can we
> > > remove 148f:2573 from rt2500usb?
> >
> > No we can't, you can blame manufacturers for shipping
> > USB sticks with different chipsets but the exact same USB ID.
>
> Maybe there are some hints on the USB level that would make it possible
> to distinguish between the devices without loading the driver?
> Something like the number of endpoints? Then we could ask USB
> developers to provide a way to specify them in the USB devece table.
Seems like a trouble to solve a non-problem...
> > On Sunday 28 December 2008, Piter PUNK wrote:
> > > Loading rt2500usb AND rt73usb don't have any functional
> > > problem. All wireless devices works fine. But is very
> > > annoying the additional modules loaded.
I'm not sure I see how it is annoying, but I'm sorry it annoys you.
Nevertheless, I don't think it is worth much effort to fix it.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
prev parent reply other threads:[~2009-01-06 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 6:35 rt2500usb vs rt73usb Piter PUNK
2008-12-28 9:34 ` Ivo van Doorn
2008-12-28 22:14 ` Pavel Roskin
2008-12-28 22:32 ` Ivo van Doorn
2008-12-28 22:44 ` Luis Correia
2009-01-06 20:27 ` John W. Linville [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=20090106202740.GE3544@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=piterpunk@unitednerds.org \
--cc=proski@gnu.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).