On Fri, 2010-01-08 at 14:06 -0600, LAMBA Jaideep wrote:
> My bad. Bullet M5 is based on AR928X chipset rather than AR9160. Here is
> the lspci information from Bullet M5. I compiled and installed
> madwifi-trunk r4099 on the board. This doesn't attach to chipset as
Correct, its PCI ID is in not in the table of the supported devices
because HAL used in MadWifi doesn't support it.
> So now correct question would be are we planning to support AR9280 in
> madwifi and how can I help. Or did I miss turning on some other flag in
> madwifi which didn't allow madwifi to associate with this radio.
FreeBSD HAL supports AR928X, so it should be possible, but it's would be
quite a big effort.
One approach would be to port MadWifi to the new channel API used by
FreeBSD. That would be the best thing if we want to stay in sync with
FreeBSD. But in terms of code changes, it's a major effort, and I don't
see it happening, especially since we don't have many active developers
and testers to deal with possible bugs. Changes will be needed
Another approach would be to backport FreeBSD HAL to the old channel
API. That would be less labor intensive, and it would bring us all
fixes from FreeBSD HAL. I think it could be done, at least partly,
using an automated patching tool, such as cochinelle.
Finally, we could backport only the files for AR928X support and their
dependencies. That's would be the easiest in terms of changes, but it
would still take several iterations before it compiles, and I'm not sure
it would work right away. It tried it and gave up due to lack of time.
You can get FreeBSD HAL by
svn co http://svn.freebsd.org/base/head/sys/dev/ath