Just in case you want to experiment, i have a working port of ar5k
that works on madwifi-old before the BSD - HEAD merge...
well i'm no good programmer (yet), i did what i could (i'm sure those
define macros are nasty for most people :P) and hope that helps...
you can git clone from the
On Wed, 2006-11-15 at 14:39 -0500, Pavel Roskin wrote:
Hello!
On Wed, 2006-11-15 at 14:21 -0500, John W. Linville wrote:
On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote:
Now that it seems to be ok to use these openbsd sources, should I port
them to my driver
Hi.
At least, this way we have a chance to get USB working as well (See
http://madwifi.org/ticket/33).
It's not the HAL that prevents MadWifi implementing USB support. Replacing
the binary-only HAL with OpenHAL and/or dissolving the HAL functionality
in the driver source does not get us any
Michael Buesch wrote:
Yeah, ok. I'll look what I can do. First I'll have to read the code.
and understand it. DMA stuff seems to be really obfuscated though
dozens of callbacks, heh. :)
I'd certainly like to see solid Atheros chipset support in mainline.
If you need any hardware or other
Hello!
On Wed, 2006-11-15 at 14:21 -0500, John W. Linville wrote:
On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote:
Now that it seems to be ok to use these openbsd sources, should I port
them to my driver framework?
I looked over the ar5k code and, well, I don't like it. ;)
On Wednesday 15 November 2006 20:39, Pavel Roskin wrote:
Hello!
On Wed, 2006-11-15 at 14:21 -0500, John W. Linville wrote:
On Wed, Nov 15, 2006 at 07:42:14PM +0100, Michael Buesch wrote:
Now that it seems to be ok to use these openbsd sources, should I port
them to my driver
Hi.
Michael Buesch wrote:
Well, it never worked for me. But I gave up trying about
half a year ago. But maybe it's just stupid me. ;)
Well, we have various support channels (an IRC channel besides two
mailing lists, for example) that you are welcome to make use of in case
of problems :)
