From: "Christoph .J Thompson" <cjsthompson@gmail.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless@vger.kernel.org, Hin-Tak Leung <hintak.leung@gmail.com>
Subject: Re: Sitecom WL-608 USB WiFi
Date: Thu, 12 Feb 2009 03:38:17 +0100 [thread overview]
Message-ID: <20090212033817.22d0a4ae.cjsthompson@gmail.com> (raw)
In-Reply-To: <200902112332.53480.IvDoorn@gmail.com>
On Wed, 11 Feb 2009 23:32:53 +0100
Ivo van Doorn <ivdoorn@gmail.com> wrote:
> Hi,
>
> Looks like a new USB id. Since it isn't an 11n device it can only be a rt73usb or rt2500usb device.
> Could you try below patch? My current bet is that the device contains the rt73 chipset,
> so this will enable rt73usb to use the device.
I have tried to add the id of the Sitecom WL-608 to the rt73usb, rt2500usb and zd1211rw drivers but so far no luck. I turned debugging on for the aforementioned drivers and here is what I got:
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - Antenna: 0x09aa
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - NIC: 0xffef
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET BG: 0x0000
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET A: 0x0000
phy4 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0001, rev: d5af900a.
phy4 -> rt73usb_init_eeprom: Error - Invalid RT chipset detected.
phy4 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt73usb
phy5 -> rt2500usb_validate_eeprom: EEPROM recovery - Antenna: 0x0002
phy5 -> rt2500usb_validate_eeprom: EEPROM recovery - NIC: 0xfff0
phy5 -> rt2x00_set_chip: Info - Chipset detected - rt: 1201, rf: 0000, rev: 00002080.
phy5 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
phy5 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2500usb
zd1211rw usb_init()
usb 1-1.1: print_id() 0df6:003f v0101 high
usb 1-1.1: reset high speed USB device using ehci_hcd and address 6
zd1211rw 1-1.1:1.0: zd_chip_read_mac_addr_fw()
usb 1-1.1: read over firmware interface failed: -32
zd1211rw 1-1.1:1.0: probe() couldn't initialize mac. Error number -32
usb 1-1.1: reset high speed USB device using ehci_hcd and address 6
zd1211rw: probe of 1-1.1:1.0 failed with error -32
usbcore: registered new interface driver zd1211rw
zd1211rw initialized
--
Christoph .J Thompson <cjsthompson@gmail.com>
prev parent reply other threads:[~2009-02-12 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:17 Sitecom WL-608 USB WiFi Christoph .J Thompson
2009-02-11 22:32 ` Ivo van Doorn
2009-02-11 22:51 ` Hin-Tak Leung
2009-02-12 1:07 ` Christoph .J Thompson
2009-02-12 3:22 ` Christoph .J Thompson
2009-02-12 8:00 ` Ivo Van Doorn
2009-02-12 8:05 ` Luis Correia
2009-02-12 8:21 ` Thomas d'Otreppe
2009-02-12 8:43 ` Christoph .J Thompson
2009-02-12 9:48 ` Luis Correia
2009-02-12 8:26 ` Christoph .J Thompson
2009-02-12 8:40 ` Ivo Van Doorn
2009-02-12 14:33 ` Christoph .J Thompson
2009-02-12 17:59 ` Ivo van Doorn
2009-02-12 2:38 ` Christoph .J Thompson [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=20090212033817.22d0a4ae.cjsthompson@gmail.com \
--to=cjsthompson@gmail.com \
--cc=hintak.leung@gmail.com \
--cc=ivdoorn@gmail.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).