On Monday 26 November 2007 23:15:53 Larry Finger wrote:
Based on the code in the rtx200 directories that has a call to
input_allocate_device() that was not
present in b43, I made a modification to drivers/net/wireless/b43/rfkill.c as
follows:
Index:
Michael Buesch wrote:
On Monday 26 November 2007 23:15:53 Larry Finger wrote:
Based on the code in the rtx200 directories that has a call to
input_allocate_device() that was not
present in b43, I made a modification to drivers/net/wireless/b43/rfkill.c
as follows:
Index:
Since addition of the rfkill callback, the LED associated with the off
switch on the radio has not worked because essential data in the rfkill
structure was missing. This hack adds the necessary data and places direct
calls to turn the leds on/off.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
On Tuesday 27 November 2007 17:03:57 Larry Finger wrote:
Since addition of the rfkill callback, the LED associated with the off
switch on the radio has not worked because essential data in the rfkill
structure was missing. This hack adds the necessary data and places direct
calls to turn the
A patch to make the modifications for ssb and b43 necessary to use the
BCM94311MCG rev02 and BCM4312
rev02 cards with kernel 2.6.24-rc2 (and later) mainline kernels may be obtained
from
http://linuxwireless.org/download/b43/patch_2.6.24_for_4311_2
Larry
On Tuesday 27 November 2007 17:28:33 Larry Finger wrote:
Michael Buesch wrote:
On Tuesday 27 November 2007 17:03:57 Larry Finger wrote:
This is not how led triggers work.
You are shortcutting the whole thing here. So you could as well
remove the whole rfkill and LEDs code.
It just
Ivo van Doorn wrote:
Hi,
On Monday 26 November 2007 23:15:53 Larry Finger wrote:
Based on the code in the rtx200 directories that has a call to
input_allocate_device() that was not
present in b43, I made a modification to drivers/net/wireless/b43/rfkill.c
as follows:
Index:
Michael Buesch wrote:
On Tuesday 27 November 2007 17:28:33 Larry Finger wrote:
Michael Buesch wrote:
On Tuesday 27 November 2007 17:03:57 Larry Finger wrote:
This is not how led triggers work.
You are shortcutting the whole thing here. So you could as well
remove the whole rfkill
On Tuesday 27 November 2007 19:33:41 Larry Finger wrote:
Ivo van Doorn wrote:
Hi,
On Monday 26 November 2007 23:15:53 Larry Finger wrote:
Based on the code in the rtx200 directories that has a call to
input_allocate_device() that was not
present in b43, I made a modification to
Michael,
I'm getting a little closer. The problem I discovered now is that
b43_leds_init() was being called
before b43_rfkill_init(), which prevented registration of the radio LED. Now,
the LED is flashed
on for about 1 second, then it goes off. Changing the switch does nothing.
This version
On Tuesday 27 November 2007 21:02:47 Larry Finger wrote:
Michael,
I'm getting a little closer. The problem I discovered now is that
b43_leds_init() was being called
before b43_rfkill_init(), which prevented registration of the radio LED.
Now, the LED is flashed
on for about 1 second,
2007/11/27, Larry Finger [EMAIL PROTECTED]:
A patch to make the modifications for ssb and b43 necessary to use the
BCM94311MCG rev02 and BCM4312
rev02 cards with kernel 2.6.24-rc2 (and later) mainline kernels may be
obtained from
Rafał Miłecki wrote:
2007/11/27, Larry Finger [EMAIL PROTECTED]:
A patch to make the modifications for ssb and b43 necessary to use the
BCM94311MCG rev02 and BCM4312
rev02 cards with kernel 2.6.24-rc2 (and later) mainline kernels may be
obtained from
Michael Buesch wrote:
On Tuesday 27 November 2007 21:02:47 Larry Finger wrote:
Is the switch properly polled and is the status change properly reported
upstream?
If yes, you might want to check (add printk to rfkill code) if the LED
is properly triggered.
I know that b43_rfkill_poll() is
I use openSUSE 10.3 with 2.6.24-rc3 and b43+4.80.53.0 firmware.
I noticed that someone created new AP on my channel (6) so I wanted to
change my AP's channel to 13. I made it and after that I was not able
to connect anymore. I was getting
Nov 27 22:12:35 acer kernel: [ 501.221868] wlan0_rename:
Rafał Miłecki wrote:
every 5 seconds. After changing channel to 1 b43 connected to my AP
again. So it looks for me like problem with connecting to AP working
on high channel. Could someone with 4318 check how it works for your
broadcom?
What happens if you use channel 11 rather than 13? The
On Nov 27, 2007 10:50 PM, Larry Finger [EMAIL PROTECTED] wrote:
Rafał Miłecki wrote:
every 5 seconds. After changing channel to 1 b43 connected to my AP
again. So it looks for me like problem with connecting to AP working
on high channel. Could someone with 4318 check how it works for
Frederik wrote:
Well, according to http://en.wikipedia.org/wiki/List_of_WLAN_channels,
channel 13 would be permitted in Europe (where I live). So mac80211
will never permit this, even if it's legal to use?
I am having the same problem connecting to my wireless access point on
channel 13:
18 matches
Mail list logo
