linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: ids missing in ath5k ?
Date: Sat, 14 Mar 2009 21:04:14 +0100	[thread overview]
Message-ID: <49BC0DBE.90209@gmail.com> (raw)

hi,

why these ids are not supported in ath5k ? 

       { 0x168c, 0x101a, PCI_ANY_ID, PCI_ANY_ID }, /* some Griffin-Lite */
       { 0x168c, 0x9013, PCI_ANY_ID, PCI_ANY_ID }, /* sonicwall */


They are included in madwifi driver! Are there more of them missing ?


-thanks-


regards,
-- 
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...

             reply	other threads:[~2009-03-14 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 20:04 Xose Vazquez Perez [this message]
2009-03-15  2:46 ` ids missing in ath5k ? 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
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=49BC0DBE.90209@gmail.com \
    --to=xose.vazquez@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).