From: Gene Heskett <gene.heskett@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: zd1211b question.
Date: Sat, 28 Jul 2007 07:55:34 -0400 [thread overview]
Message-ID: <200707280755.34930.gene.heskett@gmail.com> (raw)
Greetings all;
A net friend of mine has a Gateway m305CRV laptop, with this radio in it:
Bus 003 Device 003: ID 050d:705c Belkin Components
Its apparently sitting on the usb bus, and from my grepping of the kernel
srcs, it looks as if the zd1211b driver might be the correct one:
drivers/net/wireless/zd1211rw/zd_usb.c: /* ZD1211B */
drivers/net/wireless/zd1211rw/zd_usb.c: { USB_DEVICE(0x0ace,
0x1215), .driver_info = DEVICE_ZD1211B },
drivers/net/wireless/zd1211rw/zd_usb.c: { USB_DEVICE(0x157e,
0x300d), .driver_info = DEVICE_ZD1211B },
drivers/net/wireless/zd1211rw/zd_usb.c: { USB_DEVICE(0x079b,
0x0062), .driver_info = DEVICE_ZD1211B },
drivers/net/wireless/zd1211rw/zd_usb.c: { USB_DEVICE(0x1582,
0x6003), .driver_info = DEVICE_ZD1211B },
drivers/net/wireless/zd1211rw/zd_usb.c: { USB_DEVICE(0x050d,
0x705c), .driver_info = DEVICE_ZD1211B },
This last one is the right set of numbers. However, I'll be dipped but I
can't find anyplace in a make xconfig in the 2.6.22.1-rt9 tree, to turn on
the building of that driver.
Am I blind, don't know how to run grep, or does the xconfig script need more
tlc?
Can somebody toss me a bone of info here?
Thanks everybody.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Thus spake the master programmer:
"When a program is being tested, it is too late to make design changes."
-- Geoffrey James, "The Tao of Programming"
next reply other threads:[~2007-07-28 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 11:55 Gene Heskett [this message]
2007-07-28 13:57 ` zd1211b question Jan Engelhardt
2007-07-28 14:26 ` Daniel Drake
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=200707280755.34930.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.