From: David Acker <dacker@roinet.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
madwifi-users@lists.sourceforge.net,
Andrey Yurovsky <andrey@cozybit.com>,
madwifi-devel@lists.sourceforge.net
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Wed, 18 Nov 2009 10:35:11 -0500 [thread overview]
Message-ID: <4B04142F.6060101@roinet.com> (raw)
In-Reply-To: <4B03304C.2000403@openwrt.org>
Felix Fietkau wrote:
> David Acker wrote:
>> Also, I don't know if ath5k will work on products based on
>> Atheros WiSOCs like Ubiquiti's PicoStation and Bullet.
> I have some work in progress patches for that. They won't work yet (in
> fact I just ported them to a newer version of compat-wireless without
> testing, so they probably won't even compile yet *g*), but according to
> my rough estimation, they contain about 70-80% of what's necessary to
> support this hw. You can find them at http://nbd.name/ath5k-wisoc.tar.gz
> If anybody is seriously interested in hacking on this stuff, please take
> a look at this patch series and contact me afterwards...
Interesting. Time permitting, I will try to take a look at this a bit
this week.
>
>> A lesser issue
>> (more of a pain for me than an ath5k issue) is that I have some
>> platforms that use an older kernel and moving up to a newer kernel will
>> have to be done without hardware vendor support.
> What platforms with old kernels are you using? Maybe some of them are
> being worked on in OpenWrt already ;)
Perhaps. I have a CM-X255
http://www.compulab.co.il/x255/html/x255-cm-datasheet.htm combined with
a custom board for PCI with an intel pro 100 and a miniPCI slot holding
a ubiquiti card.
-ack
prev parent reply other threads:[~2009-11-18 15:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2205.95.222.251.107.1258282369.squirrel@webmail.otaku42.de>
2009-11-17 1:01 ` [Madwifi-devel] Survey: What are you using MadWifi for, and why? Luis R. Rodriguez
2009-11-17 14:05 ` John W. Linville
2009-11-17 22:08 ` Marcel Holtmann
2009-11-17 16:04 ` Michael Renzmann
2009-11-17 16:38 ` Luis R. Rodriguez
2009-11-17 17:51 ` Tom Sharples
2009-11-17 18:05 ` Luis R. Rodriguez
2009-11-17 21:51 ` Bob Copeland
2009-11-17 23:23 ` Pat Erley
2009-11-18 7:23 ` Michael Renzmann
2009-11-17 17:40 ` David Acker
2009-11-17 20:57 ` Andrey Yurovsky
2009-11-17 21:37 ` Luis R. Rodriguez
2009-11-17 21:44 ` David Acker
2009-11-17 21:45 ` Luis R. Rodriguez
2009-11-17 21:53 ` David Acker
2009-11-17 22:04 ` Luis R. Rodriguez
2009-11-17 22:28 ` David Acker
2009-11-17 22:39 ` Luis R. Rodriguez
2009-11-17 23:39 ` Tom Sharples
2009-11-17 23:44 ` Luis R. Rodriguez
2009-11-17 22:54 ` Jouni Malinen
2009-11-17 23:12 ` Luis R. Rodriguez
2009-11-18 21:58 ` Pavel Roskin
2009-11-18 22:08 ` Luis R. Rodriguez
2009-11-18 23:05 ` Jouni Malinen
2009-11-19 0:21 ` Luis R. Rodriguez
2009-11-18 23:12 ` Pavel Roskin
2009-11-19 0:05 ` Tom Sharples
2009-11-17 22:06 ` Marcel Holtmann
2009-11-17 22:32 ` David Acker
2009-11-17 23:22 ` Felix Fietkau
2009-11-18 15:35 ` David Acker [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=4B04142F.6060101@roinet.com \
--to=dacker@roinet.com \
--cc=andrey@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=madwifi-devel@lists.sourceforge.net \
--cc=madwifi-users@lists.sourceforge.net \
--cc=mcgrof@gmail.com \
--cc=nbd@openwrt.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.