I wanted to report that I've finally been successful at getting
b43legacy to beacon properly. Originally, I had configured hostapd to
use channel 1. After reading the list of bugs for the bwi driver,
shown here: http://leaf.dragonflybsd.org/cgi/web-man?command=bwi , I
had the inclination to try cha
David Ellingsworth wrote:
> I wanted to report that I've finally been successful at getting
> b43legacy to beacon properly. Originally, I had configured hostapd to
> use channel 1. After reading the list of bugs for the bwi driver,
> shown here: http://leaf.dragonflybsd.org/cgi/web-man?command=bwi
On Sat, Apr 11, 2009 at 11:35 AM, Larry Finger
wrote:
> David Ellingsworth wrote:
>> I wanted to report that I've finally been successful at getting
>> b43legacy to beacon properly. Originally, I had configured hostapd to
>> use channel 1. After reading the list of bugs for the bwi driver,
>> show
This patch ports the beaconing fixes from commit a82d992261f "b43: Beaconing
fixes" to b43legacy. Basically it prevents the card from triggering the beacon
IRQ over and over again.
Signed-off-by: Larry Finger
Acked-by: Michael Buesch
Tested-by: David Ellingsworth
---
John,
This is material fo
This patch ports commit c97a4ccc1fad35d3 "b43: Fix beacon BH update" to
b43legacy. It fixes beacon updating in the bottomhalf. In case the device
is busy, we will defer to later in the IRQ handler.
Signed-off-by: Larry Finger
Acked-by: Michael Buesch
Tested-by: David Ellingsworth
---
John,
Th
On Apr 10, 2009, at 2:02 PM, Gábor Stefanik wrote:
> On Fri, Apr 10, 2009 at 12:28 AM, Francesco Gringoli
> wrote:
>>
>>
>
> Can you please release the patch you used to transmit frames using b43
> directly, with a complete bypass of the stack? Also, what results do
> you get if you instead try t