Hello,
I'm following the article at https://wiki.freebsd.org/WiFi
Do you have any information about current status on Ralink 802.11n chipset
support at Freebsd 9 ?
Thank you.
--
Best regards,
Vadim
___
freebsd-wireless@freebsd.org mailing list
http:/
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
Cedric, Adrian,
Thanks.
load: 0.48 cmd: ping 92340 [select] 55334.70r 1.28u 4.48s 0% 1528k
53094/54469 packets received (97.5%) 9.345 min / 44.002 avg / 3404.123 max
iwn_tx_data: qid 11 idx 180 len 76 nsegs 2 rate 008a plcp 0xe10a
iwn5000_tx_done: qid 11 idx 180 retries 0 nkill 0 rate e10a
Cool!
Next is fixing linkq/MRR handling.
I've been told by Johannes at Intel that we don't have to do software
retry ourselves. Just do MRR, then send BAR frames if we ever get a
"you lost!" notification.
Also, we _can_ do background scans with active traffic. The firmware
does this. So, we have
On Thursday, November 07, 2013 5:22:03 pm clutton wrote:
> On Wed, 2013-11-06 at 11:59 -0500, John Baldwin wrote:
> > On Tuesday, November 05, 2013 5:17:30 pm John Baldwin wrote:
> > > On Tuesday, November 05, 2013 2:33:50 pm Bernhard Schmidt wrote:
> > > > On Tue, Nov 5, 2013 at 5:54 PM, John Bald
John Baldwin wrote
in <201311051154.18872@freebsd.org>:
jh> I also tested vlans created via vlans_ and they should use the same fix
as
jh> well. Note that this model is more consistent with how cloned_interfaces
jh> works where ifn_start is not explicitly run when each interface is create
Hi,
I've just committed Cedric's stuff to -HEAD. I also fixed the MRR stuff to work.
It's been fun. Kinda.
There are still issues with the driver. I bet the TX handling for
aggregation frames isn't entirely correct. I bet the bluetooth
coexistence isn't right. There's still the bugs with scannin
