Hi all.
To make things easier for development I'd like to suggest a few madwif
ibranches created:
* madwifi-1152-openhal: based on madwifi-1152, patched with my patch,
added openhal, old hal removed. Working free solution. Should exist
just as a reference and to allow users to checkout a
Hi.
On Wednesday 29 November 2006 16:24, David Kimdon wrote:
There is absolutely no reason why dadwifi can't be merged into the
mainline once the hal issue is resolved.
Last time we talked about that stuff, it was decided that
we don't want a HAL... See archives.
IIRC Pavel already
Hi.
Michael Buesch wrote:
IIRC Pavel already explained that getting rid of the HAL per se should be
no problem - it could easily be dissolved into the driver, if that is one
of the requirements to be fulfilled before the driver (MadWifi or DadWifi)
is considered for mainline inclusion. As soon
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
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 :)
Hi.
On Mon, 2005-12-05 at 19:00 +0100, Jiri Benc wrote:
Why yet another attempt to write 802.11 stack? Sure, the one currently
in the kernel is unusable and everybody knows about it. But why not to
improve code opensourced by Devicescape some time ago instead of
inventing the wheel again and
Hi.
On Mon, 2005-12-05 at 13:46 -0500, Jeff Garzik wrote:
Although I'm a bit biased towards MadWifi, I'd second your suggestion to
make use of the Devicescape code. The benefit of having a fully-blown
802.11 stack in the kernel that drivers can make use of has been
discussed before, so I
Hi.
On Tue, 2005-11-22 at 15:26 -0800, Ben Greear wrote:
Connected to eth0 is a PC with MAC address AA, which is exactly the
same MAC address as ms1 has (this is to work around the fact that
a wifi interface can't really go into promisc mode or send frames with
a different source MAC
Hi.
Mateusz Berezecki wrote:
Im sending a series of 8 patches splitted and diffed as in
SubmittingPatches documentation.
Patch 4/8 is missing here.
Bye, Mike
--
Use PGP/GPG!
My key: http://keys.indymedia.org/cgi-bin/lookup?op=getsearch=62C29B94
Fingerprint: BC2E 79BF 0C8F 0282 864B 9CEC 8343
