Re: request for help: 'fixing' the 802.11 TX path

2012-10-29 Thread Andre Oppermann
On 29.10.2012 04:53, Adrian Chadd wrote: On 28 October 2012 20:43, PseudoCylon wrote: Cannot we just add custom hand off function to ieee80211_start()? Yes. That's the general idea. But what I don't want to do is have it just wake up the driver TX taskqueue - well, unless we have to. That m

Current problem reports assigned to freebsd-wireless@FreeBSD.org

2012-10-29 Thread FreeBSD bugmaster
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker

Re: Wireless network Broadcom not connected.

2012-10-29 Thread Adrian Chadd
Hi, I honestly think this is a driver bug, I'm sorry. We're going to need someone to step up and take ownership of the broadcom wifi drivers. Adrian On 21 October 2012 05:46, George wrote: > On 21.10.2012 09:27, yo9...@yahoo.com wrote: >> >> I can connect but get this message at boot: >> >>

Re: request for help: 'fixing' the 802.11 TX path

2012-10-29 Thread PseudoCylon
On Mon, Oct 29, 2012 at 3:47 AM, Andre Oppermann wrote: > On 29.10.2012 04:53, Adrian Chadd wrote: >> >> On 28 October 2012 20:43, PseudoCylon wrote: >> >>> Cannot we just add custom hand off function to ieee80211_start()? >> >> >> Yes. That's the general idea. But what I don't want to do is have

Re: request for help: 'fixing' the 802.11 TX path

2012-10-29 Thread Adrian Chadd
The problem with this is that fragments need to be handed as an entire list to the driver. ath(4) looks ahead to the next fragment, calculates the rate, and then adds that to the NAV of the previous frame. So yeah what I'm thinking about for now is something like the following: * say that wifi d