Linux wireless drivers development
 help / color / mirror / Atom feed
From: "u2@whoplays.asia" <u2@whoplays.asia>
To: linux-wireless@vger.kernel.org
Subject: [Driver] NEC WL300NU-G
Date: Sun, 16 Jan 2011 00:49:09 +0900	[thread overview]
Message-ID: <4D31C1F5.7080306@whoplays.asia> (raw)

hi,

According to the list linuxwireless.org/en/users/Devices/USB, Wireless 
USB adapter NEC WL300NU-G[0x409:0x093f] is supported by ar9170usb.

But the one I bought via 
www.amazon.co.jp/NEC-Aterm-WL300NU-G-PA-WL300NU-G is [0x409:0x0249] and 
not detected by any drivers...

$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 006: ID 0a5c:2101 Broadcom Corp. Bluetooth Controller
Bus 002 Device 005: ID 0853:0100 Topre Corporation HHKB Professional
Bus 002 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 003: ID 0409:0249 NEC Corp.
Bus 002 Device 002: ID 2019:ab50 PLANEX GW-US54Mini2
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ uname -a
Linux localhost 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 
x86_64 GNU/Linux

Plz anyone describe me why this one has another vendor-productID, and 
will this one supported?

Regards,
Miyagi

             reply	other threads:[~2011-01-15 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 15:49 u2 [this message]
2011-01-15 17:39 ` [Driver] NEC WL300NU-G Gertjan van Wingerde
2011-01-15 22:47   ` u2
2011-01-15 23:14     ` Sedat Dilek
2011-01-15 23:38       ` u2

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=4D31C1F5.7080306@whoplays.asia \
    --to=u2@whoplays.asia \
    --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