Return-path: Received: from mail.atheros.com ([12.36.123.2]:52018 "EHLO mail.atheros.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751855AbZCQWye (ORCPT ); Tue, 17 Mar 2009 18:54:34 -0400 Received: from mail.atheros.com ([10.10.20.108]) by sidewinder.atheros.com for ; Tue, 17 Mar 2009 15:54:23 -0700 Date: Tue, 17 Mar 2009 14:36:39 -0700 From: "Luis R. Rodriguez" To: Bob Copeland CC: Xose Vazquez Perez , linux-wireless , Luis Rodriguez , Subject: Re: ids missing in ath5k ? Message-ID: <20090317213639.GF6061@tesla> (sfid-20090317_235437_489958_833A8A49) References: <49BC0DBE.90209@gmail.com> <49BC6C21.6020807@gmail.com> <49BC7117.1010107@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 > 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. Luis