From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Cc: Bob Copeland <me@bobcopeland.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
David Quan <David.Quan@Atheros.com>
Subject: Re: ids missing in ath5k ?
Date: Tue, 17 Mar 2009 15:36:32 -0700 [thread overview]
Message-ID: <20090317223632.GN6061@tesla> (raw)
In-Reply-To: <20090317213639.GF6061@tesla>
On Tue, Mar 17, 2009 at 02:36:39PM -0700, Luis Rodriguez wrote:
> On Tue, Mar 17, 2009 at 02:18:45PM -0700, Bob Copeland wrote:
> > On Sat, Mar 14, 2009 at 11:08 PM, Xose Vazquez Perez
> > <xose.vazquez@gmail.com> wrote:
> >
> > > [missing ids: 0x168c: { 0xff1a, 0x0020, 0x101a, 0x9013 } ]
> >
> > Luis, do you know anything about these devices? Are all of these
> > 802.11abg or are any .11h (I didn't see ath9k claiming any of
> > them either).
> >
> > Should be easy to add support, but would be nice to know if the
> > hardware exists and will work.
>
> ACK on FF1A -- 802.11abg, NACK on the others, we don't at least have
> them in our own windows driver INF file.
Actually so any 0xFF1x device ID where x is any value would
be the ID if the card has issues reading our EEPROM and in that
case you can expect the card to simply not be operational, so feel
free to add it but be sure to inform the user the card is having
issues reading the EEPROM and simply disable the device.
Luis
next prev parent reply other threads:[~2009-03-17 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 20:04 ids missing in ath5k ? Xose Vazquez Perez
2009-03-15 2:46 ` Xose Vazquez Perez
2009-03-15 3:08 ` Xose Vazquez Perez
2009-03-17 21:18 ` Bob Copeland
2009-03-17 21:36 ` Luis R. Rodriguez
2009-03-17 22:36 ` Luis R. Rodriguez [this message]
2009-03-18 0:06 ` Bob Copeland
2009-03-18 20:33 ` Xose Vazquez Perez
2009-03-18 20:38 ` David Quan
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=20090317223632.GN6061@tesla \
--to=lrodriguez@atheros.com \
--cc=David.Quan@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=xose.vazquez@gmail.com \
/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).