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.
> Just in case you want to experiment, i have a working port of ar5k
> that works on madwifi-old before the BSD - HEAD merge...
Just to mention it: madwifi-old is no longer officially supported, and is
a bad ground to start working on IMO (at least for anything that goes
beyond a quick
Hi.
Just in case you want to experiment, i have a working port of ar5k
that works on madwifi-old before the BSD - HEAD merge...
Just to mention it: madwifi-old is no longer officially supported, and is
a bad ground to start working on IMO (at least for anything that goes
beyond a quick test).
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.
Sam Ravnborg wrote:
[EMAIL PROTECTED] linux-2.6.10 $ make kernelrelease
make: *** No rule to make target `kernelrelease'. Stop.
I works with the 2.6 kernel.
As Andreas Gruenbacher pointed out, this feature has been implemented
just about 8 weeks ago. He also gave the following snippet as a
Hi.
Andreas Gruenbacher wrote:
A backward-compatible replacement for the new kernelrelease (which was added
only 8 weeks ago) rule is:
echo -e 'foo:[EMAIL PROTECTED] $(KERNELRELEASE)\ninclude Makefile' \
| make -f-
Thanks a lot, that works great!
Bye, Mike
-
To unsubscribe from this list:
Hi.
Andreas Gruenbacher wrote:
A backward-compatible replacement for the new kernelrelease (which was added
only 8 weeks ago) rule is:
echo -e 'foo:[EMAIL PROTECTED] $(KERNELRELEASE)\ninclude Makefile' \
| make -f-
Thanks a lot, that works great!
Bye, Mike
-
To unsubscribe from this list:
Hi.
Sam Ravnborg wrote:
[EMAIL PROTECTED] linux-2.6.10 $ make kernelrelease
make: *** No rule to make target `kernelrelease'. Stop.
I works with the 2.6 kernel.
As Andreas Gruenbacher pointed out, this feature has been implemented
just about 8 weeks ago. He also gave the following snippet as a
Hi.
Sam Ravnborg wrote:
But... what is the right way to do this?
I think you are looking for:
make kernelrelease
[EMAIL PROTECTED] linux-2.6.10 $ make kernelrelease
make: *** No rule to make target `kernelrelease'. Stop.
[EMAIL PROTECTED] linux-2.6.10 $ cd ..
[EMAIL PROTECTED] src $ cd
Hi all.
(Please CC: me, I'm not subscribed - although I'm following the list
through gmane.org)
I'm working on Madwifi (a driver for wireless lan cards with Atheros
chipset), which isn't part of the kernel (and probably won't ever be due
to the binary-only HAL). As every third-party device
Hi all.
(Please CC: me, I'm not subscribed - although I'm following the list
through gmane.org)
I'm working on Madwifi (a driver for wireless lan cards with Atheros
chipset), which isn't part of the kernel (and probably won't ever be due
to the binary-only HAL). As every third-party device
Hi.
Sam Ravnborg wrote:
But... what is the right way to do this?
I think you are looking for:
make kernelrelease
[EMAIL PROTECTED] linux-2.6.10 $ make kernelrelease
make: *** No rule to make target `kernelrelease'. Stop.
[EMAIL PROTECTED] linux-2.6.10 $ cd ..
[EMAIL PROTECTED] src $ cd
12 matches
Mail list logo
