linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Piter PUNK <piterpunk@unitednerds.org>, linux-wireless@vger.kernel.org
Subject: Re: rt2500usb vs rt73usb
Date: Sun, 28 Dec 2008 17:14:54 -0500	[thread overview]
Message-ID: <1230502494.25726.26.camel@dv> (raw)
In-Reply-To: <200812281034.07373.IvDoorn@gmail.com>

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

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.

I have a device that works with rt73usb, but not rt2500usb.  I'm
attaching the output of "lsusb -v" for the device.  If we look at
similar information for other devices, we could find out how to
distinguish them.

-- 
Regards,
Pavel Roskin

[-- Attachment #2: rt73 --]
[-- Type: text/plain, Size: 2369 bytes --]

Bus 001 Device 004: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x148f Ralink Technology, Corp.
  idProduct          0x2573 RT2501USB Wireless Adapter
  bcdDevice            0.01
  iManufacturer           1 Ralink
  iProduct                2 802.11 bg WLAN
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

  reply	other threads:[~2008-12-28 22:14 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 [this message]
2008-12-28 22:32     ` Ivo van Doorn
2008-12-28 22:44       ` Luis Correia
2009-01-06 20:27     ` John W. Linville

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=1230502494.25726.26.camel@dv \
    --to=proski@gnu.org \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=piterpunk@unitednerds.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).