netdev - Re: The future of the TI ACX wireless driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Jun 2007 10:21:32 -0500 (CDT)
From:	Jeff Williams <angelbane@...edu>
To:	David Planella <david.planella@...glemail.com>
cc:	acx100-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org
Subject: Re: The future of the TI ACX wireless driver

> * Mac80211 driver, which uses the seemingly
> soon-to-be-included-in-kernel mac80211 stack, available on the
> wireless-dev tree (the stack, not the driver).
> This release is only available here [2] and needs some work before
> being included in wireless-dev, since it was released at the time when
> mac80211 was still called d80211. In any case, having had a quick look
> at the code, I believe that replacing the d80211.h header reference to
> mac80211.h and maybe refactoring some functions might be all what is
> needed for an initial compilation. Note that I haven't got any
> previous driver or kernel module development experience, so I might be
> wrong here. What would also be needed is to merge all changes from the
> softmac and plain drivers.
>
You can find a updated-as-of-last-month mac80211 pci driver at 
http://airgo.wdwconsulting.net/acx-mac80211-20070510.patch.bz2
it may or may not work, it compiles, it responds with aps to iwlist sc. 
Enabling ACX_MAC80211_USB will cause the build to fail. I'll be happy to 
take patches and bug reports.

thanks,

Jeff Williams
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html