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@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
