public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:49:44 +0200	[thread overview]
Message-ID: <200710211549.44955.IvDoorn@gmail.com> (raw)
In-Reply-To: <20071021092138.GC25270@elf.ucw.cz>

On Sunday 21 October 2007, Pavel Machek wrote:
> Hi!
> 
> > > Kohjinsha subnotebook seems to contain wifi with USB IDs 0x18e8,
> > > 0x6206... I hope that to be compatible with
> > > net/wireless/rt2x00/rt73usb.c .
> > 
> > Is there any reason you assume it is a rt73usb device,
> > or are you just making wild guesses about what the chipset is?
> 
> Wild guess. I've seen 18e8:6XXX being handled by rt73usb, so..

Thats an incorrect assumption. USB ID's listed in rt73usb don't even
guarentee that the device contains a rt73usb chipset since some manufacturers
produce cards with different chipsets while keeping the USB ID the same.
So the case that the card false in the 6xxx range says absolutely _nothing_.

Ivo

  reply	other threads:[~2007-10-21 11:31 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
2007-10-21  9:21   ` Pavel Machek
2007-10-21 13:49     ` Ivo van Doorn [this message]
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=200710211549.44955.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