linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [rt2x00] rt3070 fails to initialize with rt2800usb
@ 2010-04-19 16:13 Walter
  2010-04-19 16:25 ` Ivo van Doorn
  0 siblings, 1 reply; 11+ messages in thread
From: Walter @ 2010-04-19 16:13 UTC (permalink / raw)
  To: Ivo van Doorn; +Cc: linux-wireless, users

> Thats odd, in compar-wireless, it already contains the
> lines:
> 
> #ifdef CONFIG_RT2800USB_RT30XX
>     <..snip..>
>     /* Ralink */
>     { USB_DEVICE(0x148f, 0x2070),
> USB_DEVICE_DATA(&rt2800usb_ops) },
>     { USB_DEVICE(0x148f, 0x3070),
> USB_DEVICE_DATA(&rt2800usb_ops) },
>     { USB_DEVICE(0x148f, 0x3071),
> USB_DEVICE_DATA(&rt2800usb_ops) },
>     { USB_DEVICE(0x148f, 0x3072),
> USB_DEVICE_DATA(&rt2800usb_ops) },
>     <..snip..>
> #endif
> 
> So adding the USB ID does not need to be added.
> 
> Ivo

It is odd. I followed exactly the same logic you have, but I'm adamant the module doesn't recognize the VID of card as it is. Lets get factual:

compat-wireless from March 28th. default install (make && make install) here is the output when the rt2800usb is loaded:

[21902.553231] Generic kernel compatibility enabled based on linux-next next-20100113
[21902.596351] cfg80211: Calling CRDA to update world regulatory domain
[21902.695076] usbcore: registered new interface driver rt2800usb
[21902.714019] cfg80211: World regulatory domain updated:
[21902.714026]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[21902.714032]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[21902.714036]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[21902.714041]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[21902.714045]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[21902.714050]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

modinfo rt2800usb |grep 3070 -- returns nothing

as soon as I add the 148f:rt3070 to: 

    /* Ralink */
    { USB_DEVICE(0x148f, 0x2770), USB_DEVICE_DATA(&rt2800usb_ops) },
    { USB_DEVICE(0x148f, 0x2870), USB_DEVICE_DATA(&rt2800usb_ops) },
    { USB_DEVICE(0x148f, 0x3070), USB_DEVICE_DATA(&rt2800usb_ops) }, <--- manually added
       /* Samsung */

rt2800usb recognizes the chip and initializes all operations:

[22310.272382] usb 5-2.4: new high speed USB device using ehci_hcd and address 10
[22310.381269] usb 5-2.4: configuration #1 chosen from 1 choice
[22310.416482] phy1: Selected rate control algorithm 'minstrel'
[22310.417403] Registered led device: rt2800usb-phy1::radio
[22310.417456] Registered led device: rt2800usb-phy1::assoc
[22310.417505] Registered led device: rt2800usb-phy1::quality
[22310.479159] udev: renamed network interface wlan0 to wlan2
[22310.483779] rt2800usb 5-2.4:1.0: firmware: requesting rt2870.bin

Now, modinfo rt2800usb |grep 3070 -- shows its OK:

alias:          usb:v148Fp3070d*dc*dsc*dp*ic*isc*ip*


This is a longstanding bug from at least few months or so,  I thought you were experimenting/adjusting the code and I figured it would be temporary, but it has been so long that I thought I had to report this now.

Walter.



      

^ permalink raw reply	[flat|nested] 11+ messages in thread
* [rt2x00] rt3070 fails to initialize with rt2800usb
@ 2010-04-17 12:26 Walter
  2010-04-17 12:45 ` Ivo van Doorn
  0 siblings, 1 reply; 11+ messages in thread
From: Walter @ 2010-04-17 12:26 UTC (permalink / raw)
  To: linux-wireless, users

I've been monitoring the community's work for the rt3070 chips and especially your recent success towards improving the driver.

I would like to share something with the rt2x00 development team which may or may not be known.

The rt3070 card I own fails to initialize with the latest (working) compat-wireless release. When I plug the USB card, rt2800usb doesn't automatically load and when I manually modprobe the driver it does not recognize it as well.

Looking in to the rt2800usb.c file I found the 'problem'. The VIDs aren't properly set. Mine shows 148f:3070. Although a line is included in the "#ifdef CONFIG_RT2800USB_RT30XX", the module won't initialize the card.

I fixed the problem by adding my device here:

	/* Ralink */
	{ USB_DEVICE(0x148f, 0x2770), USB_DEVICE_DATA(&rt2800usb_ops) },
	{ USB_DEVICE(0x148f, 0x2870), USB_DEVICE_DATA(&rt2800usb_ops) },
	/* Samsung */ 

which now looks like:

	/* Ralink */
	{ USB_DEVICE(0x148f, 0x2770), USB_DEVICE_DATA(&rt2800usb_ops) },
	{ USB_DEVICE(0x148f, 0x2870), USB_DEVICE_DATA(&rt2800usb_ops) },
        { USB_DEVICE(0x148f, 0x3070), USB_DEVICE_DATA(&rt2800usb_ops) },
	/* Samsung */

This pertains to the rt3071 as well.

Regards.


      

^ permalink raw reply	[flat|nested] 11+ messages in thread
end of thread, other threads:[~2010-04-23  8:46 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-19 16:13 [rt2x00] rt3070 fails to initialize with rt2800usb Walter
2010-04-19 16:25 ` Ivo van Doorn
2010-04-21  8:17   ` Walter Goldens
2010-04-21 21:10     ` Gertjan van Wingerde
2010-04-22  9:05       ` Walter Goldens
2010-04-22 20:51         ` Gertjan van Wingerde
2010-04-23  8:46           ` Walter Goldens
  -- strict thread matches above, loose matches on Subject: below --
2010-04-17 12:26 Walter
2010-04-17 12:45 ` Ivo van Doorn
2010-04-17 13:09   ` Walter
2010-04-17 13:16     ` Ivo van Doorn

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).