Re: [PATCH] b43: Add PIO support for PCMCIA devices

PIO is needed for 16bit PCMCIA devices, as we really don't want to poke with the braindead DMA mechanisms on PCMCIA sockets. Additionally, not all PCMCIA sockets do actually support DMA in 16bit mode (mine doesn't). Oddly, my CF card still doesn't work. Is there anything else I need in a

Re: rfkill radio button do not work (SOLVED)

i continue search and found that i forgot enable the CONFIG_INPUT_POLLDEV option. Thanks Shouldn't this be done automatically by a proper entry in the Kconfig file? ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de

Regarding HP notebooks with disappearing WLAN interfaces

I just got an E-mail from HP announcing a free repair for certain laptop models. The appropriate URL is http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=encc=usdlc=endocname=c01087277. They also announced a BIOS update that changes the fan control to be more aggressive. Reading between

Re: [PATCH] b43: Add PIO support for PCMCIA devices

On Thursday 03 April 2008 12:36:48 Johannes Berg wrote: PIO is needed for 16bit PCMCIA devices, as we really don't want to poke with the braindead DMA mechanisms on PCMCIA sockets. Additionally, not all PCMCIA sockets do actually support DMA in 16bit mode (mine doesn't). Oddly, my CF

Re: Range issue using b43 legacy

That sure sounds more likely to be related to fixing the problem. How do I see your changes and know where to change the source code I have to test it out? Regards, Kurt - Date: Wed, 2 Apr 2008 21:29:19 +0200 From: Michael Buesch [EMAIL PROTECTED] Subject: Re: Range issue using

Re: rfkill radio button do not work (SOLVED)

El Jue 03 Abr 2008, Holger Schurig escribió: i continue search and found that i forgot enable the CONFIG_INPUT_POLLDEV option. Thanks Shouldn't this be done automatically by a proper entry in the Kconfig file? yes, but i forgot mark this option in menuconfig and CONFIG_B43_RFKILL depends

Re: rfkill radio button do not work (SOLVED)

On Thursday 03 April 2008 17:27:16 Fernando Toledo wrote: El Jue 03 Abr 2008, Holger Schurig escribió: i continue search and found that i forgot enable the CONFIG_INPUT_POLLDEV option. Thanks Shouldn't this be done automatically by a proper entry in the Kconfig file? yes, but i

Re: Range issue using b43 legacy

Michael Buesch wrote: On Thursday 03 April 2008 17:10:15 KURT PETERS wrote: That sure sounds more likely to be related to fixing the problem. How do I see your changes and know where to change the source code I have to test it out? Well, you need to port b43's b43_phy_xmitpower() to

[PATCH] b43: Add more N-PHY stuff

This adds some minor stuff for N-PHY support. Nothing special. Adds Analog switching and some TODOs for RSSI processing. Just a patch I had floating around for quite some time now. Signed-off-by: Michael Buesch [EMAIL PROTECTED] Index: wireless-testing/drivers/net/wireless/b43/xmit.c

[PATCH] b43: Fix TBTT and PU timings

This fixes some timings for pre-TBTT and synthetic PU. Signed-off-by: Michael Buesch [EMAIL PROTECTED] --- John, please queue for 2.6.26 Stefano, you might want to port this. Index: wireless-testing/drivers/net/wireless/b43/b43.h

[PATCH] b43legacy: Partial Fix for Range issue

When the mac80211 channel tables were recently changed, the power_level member was removed. As a result, the value passed to b43legacy in conf-power_level became zero. This value is transferred to phy-power_level and used in calculating the desired TX power, which thus became zero. This patch

Re: [PATCH] b43legacy: Partial Fix for Range issue

Michael Buesch wrote: In b43 I set this value to 30. I dunno what the real HW upper limit is, so I set it so something that's way above the actual value mac80211 will ever try anyway (because mac80211 won't try illegal rates, if implemented correctly). I used 20 (0x14) because 20 dBm is