From: Pavel Roskin <proski@gnu.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Future handling of AR5416
Date: Tue, 05 Aug 2008 22:53:27 -0400 [thread overview]
Message-ID: <1217991207.4426.6.camel@dv> (raw)
In-Reply-To: <4899106A.9060103@lwfinger.net>
On Tue, 2008-08-05 at 21:46 -0500, Larry Finger wrote:
> In my helping with wireless on the openSUSE Forums, I recently tried to help a
> user with an AR5416 (Vendor ID 168c, PCI ID 0023). The user has kernel 2.6.25.11
> and gets the "Device not yet supported." message. By looking at the code, I see
> that same situation still exists in wireless-testing.
>
> So that I may advise the OP accurately, will this chip be supported in the near
> future, or should I recommend that he use ndiswrapper?
That's a nicely timed question! Today's (but not yesterday's :-))
wireless-testing does support AR5416 with the new ath9k driver.
Unfortunately, ath9k is not in compat-wireless. I heard it may be hard
to backport the current wireless drivers.
Anyway, MadWifi trunk (not 0.9.4) supports AR5416, and it's a nicer
driver than ndiswrapper IMHO.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-08-06 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 2:46 Future handling of AR5416 Larry Finger
2008-08-06 2:53 ` Pavel Roskin [this message]
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=1217991207.4426.6.camel@dv \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--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 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.