From: Ivo van Doorn <ivdoorn@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: rt2400-devel@lists.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org, mwallis@serialmonkey.com
Subject: Re: [Rt2400-devel] rt73usb: support for wireless in Kohjinsha subnotebook
Date: Sun, 21 Oct 2007 15:56:29 +0200 [thread overview]
Message-ID: <200710211556.29469.IvDoorn@gmail.com> (raw)
In-Reply-To: <20071021092048.GA25270@elf.ucw.cz>
Hi,
> > If rt2x00 is loaded and detected the device, it should print out a debug message that starts with:
> > "Chipset detected - " What is in your case the complete line?
>
> Ok, I guess I should include more complete debug output.
>
> phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x09 failed for offset 0x0000 with error -32
- Vendor requests error with the -32 errors often indicate the incorrect device.
> phy0 -> rt73usb_validate_eeprom: EEPROM recover - MAC: 66:76:2b:e8:68:e7
- Incorrect MAC address read from the device. Another hint that the device is not rt73.
> phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3000 with error -32
> phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0000, rev: c03c0ae0
- A incorrect RF chipset. (valid values are: 1, 2, 3 or 4). Another indication of a incorrect device.
- A completely bogus chipset revision. A valid rt73 device has the revision "2573X" Where only the
X is a variable.
> phy0 -> rt73usb_init_eeprom: Error - Invalid RF chipset detected
>
> ...so, I think hardware is indeed quite similar to what rt73usb driver
> expects...?
No. You can assume you are forcing rt73 to control a non-rt73 device.
The fact that you had to hack to bypass the RT and RF chipset validation also confirms that,
those checks were there for a reason. Namely to make sure the corect driver was being used for the device.
Ivo
next prev parent reply other threads:[~2007-10-21 11:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 18:41 rt73usb: support for wireless in Kohjinsha subnotebook Pavel Machek
2007-10-20 22:12 ` [Rt2400-devel] " Ivo van Doorn
2007-10-21 9:20 ` Pavel Machek
2007-10-21 13:56 ` Ivo van Doorn [this message]
2007-10-21 9:21 ` Pavel Machek
2007-10-21 13:49 ` Ivo van Doorn
2007-10-21 11:38 ` Pavel Machek
2007-10-21 14:09 ` Ivo van Doorn
2007-10-21 11:58 ` Luis Correia
2007-10-21 15:02 ` Luis Correia
2007-10-21 20:04 ` ISSC W89C35 802.11bg (was Re: rt73usb: support for wireless in Kohjinsha subnotebook) Pavel Machek
2007-10-22 0:09 ` rt73usb: support for wireless in Kohjinsha subnotebook Pavel Machek
2007-10-22 15:44 ` Dan Williams
2007-10-22 21:13 ` Pavel Machek
2007-10-22 21:52 ` Ivo van Doorn
2007-10-22 21:42 ` Daniel Hazelton
2007-10-22 22:00 ` Pavel Machek
2007-10-23 9:08 ` Christoph Hellwig
2007-10-23 9:11 ` Luis Correia
2007-10-30 11:22 ` Licensing of IS89C35 WLAN USB driver [was Re: rt73usb: support for wireless in Kohjinsha subnotebook] Pavel Machek
2007-10-30 15:11 ` Dan Williams
2007-10-31 0:25 ` Pavel Machek
2007-11-04 19:00 ` Pavel Machek
2007-10-23 14:05 ` rt73usb: support for wireless in Kohjinsha subnotebook Dan Williams
2007-10-23 17:07 ` Daniel Hazelton
2007-10-23 18:54 ` Dan Williams
2007-10-23 19:41 ` Daniel Hazelton
2007-10-23 21:27 ` Dan Williams
2007-10-23 22:19 ` Daniel Hazelton
2007-10-23 16:13 ` Arjan van de Ven
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=200710211556.29469.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mwallis@serialmonkey.com \
--cc=pavel@ucw.cz \
--cc=rt2400-devel@lists.sourceforge.net \
/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