for long distance link support
(which requires tweaking slot timing, ACK/CTS timing, etc.)
Let me know if you'd like a mini-project to hack on.
Adrian
-- Forwarded message --
From: Adrian Chadd adr...@freebsd.org
Date: 13 September 2012 00:24
Subject: svn commit: r240448 - head/sys
Hiya,
That link doesn't work. CAn you please double-checK/
THanks,
Adrian
On 13 September 2012 14:24, Lev Serebryakov l...@freebsd.org wrote:
Hello, Freebsd-wireless.
AR9220 in AP mode, kernel r240324, WAP2, _two_ clients, both
802.11g.
One client sends data over TCP (bulk copy
Is this -HEAD? Did you define MALLOC_PRODUCTION?
Adrian
On 18 September 2012 07:11, Johann Hugo jh...@meraka.csir.co.za wrote:
On Wednesday 05 September 2012 01:20:10 Adrian Chadd wrote:
On 28 August 2012 21:00, Adrian Chadd adr...@freebsd.org wrote:
The default (most things as modules
I've found/fixed the BAR and filtered frame issues that crept up; as
well as some other filtered frames related hangs.
I committed the mess to -HEAD.
Please update, test and let me know if things hang in weird and strange ways.
adrian
On 12 September 2012 16:08, Adrian Chadd adr
, September 21, 2012 12:50:08 AM Adrian Chadd wrote:
Which iperf is upload and which is download?
Can you run athstats during the transfer?
Adrian
On Sep 20, 2012 8:57 PM, Derrick Edwards dantavious...@gmail.com wrote:
Hi,
I am utilizing an mini PCIE AR9287 mini PCI-E
On 23 September 2012 10:06, Sven Hazejager s...@hazejager.nl wrote:
Hi Adrian,
I am unable to build any svn sources from around March and April due
to some yacc/parse.y failure that I cannot fix within the time I have.
Can I simply restore an older version of sys/modules/ath and
sys/dev/ath
Looks like someone else is reporting a problem.
I wonder if I broke beacon handling somehow..
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
On 24 September 2012 03:00, Berislav Purgar bpur...@gmail.com wrote:
Hi
just tested it .. it's ok !
Sweet. I thought it would be, the patch was just me preparing for the
next phase of software retransmit handling. :-)
Lev, can you try -HEAD and let me know?
Thanks,
Adrian
On 28 September 2012 07:03, PseudoCylon moonlightak...@yahoo.ca wrote:
Hm, that's odd. Who wants to go digging to figure out which code paths
are causing this? :)
A suggestion
in setmlme_dropsta()
http://fxr.watson.org/fxr/source/net80211/ieee80211_ioctl.c#L1331
Just forget about node
Hi,
Nope. Its a two stream device.
Ill email the list when the ar9380 3 stream support is in
On Sep 29, 2012 11:06 AM, Sven Hazejager s...@hazejager.nl wrote:
Hi there,
I'm running FreeBSD 10-CURRENT r240893 on ALIX, just replaced my old
802.11g by a DNMA-83 3x3 802.11 card, works great,
Hi,
Your best bet is to buy one of the supported Atheros 802.11n NICs -
AR5416, AR9160, AR9220.
AR9285 didn't come in a PCI flavour.
The AR9227 is a PCI version of the AR9287, but it's 2GHz only.
You can find PCI D-Link adaptors that have either AR9220 or AR5416
NICs in them. Be sure it's dual
data.)
Thanks,
Adrian
-- Forwarded message --
From: Adrian Chadd adr...@freebsd.org
Date: 3 October 2012 16:23
Subject: svn commit: r241170 - head/sys/dev/ath
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h...@freebsd.org
Author: adrian
Date: Wed Oct 3 23:23
Hi,
Please post the output of 'ifconfig wlanX list scan' to the list. :-)
That'll make it much more obvious.
Thanks,
Adrian
On 20 October 2012 22:41, yo9...@yahoo.com wrote:
I have a Laptop Acer Extensa 5220 but I can not connect to wireless network.
Broadcom Corporation BCM4312
On 22 October 2012 06:56, Johann Hugo jh...@meraka.csir.co.za wrote:
Hi
What difference in throuput can one expect between ht/20 and a ht/40 ?
If you're hitting best possible circumstances? Almost 2x.
Now, where's my IBSS HT bug? :) I can easily debug that stuff now.
adrian
Johann
The following reply was made to PR kern/172955; it has been noted by GNATS.
From: Adrian Chadd adr...@freebsd.org
To: Johann Hugo jh...@meraka.csir.co.za
Cc: bug-follo...@freebsd.org
Subject: Re: misc/172955: [ath] 11n does not work in adhoc mode
Date: Mon, 22 Oct 2012 12:57:42 -0700
Right
I'd love if someone would do this. Anyone?
Adrian
On 7 November 2012 21:09, Christopher Patrick cpatric...@rocketmail.com wrote:
I was wondering If you would be kind enough to port urtwn from Openbsd. I
would be willing to test it if you would please port it.
Does it have a USB bluetooth adaptor on board? I know the atheros
wifi+bt combo cards use a USB bluetooth chip.
Adrian
On 16 November 2012 10:36, Гуляев Гоша gosha-n...@yandex.ru wrote:
Good day!
I'm tryin to get working wireless card RTL8723AE on my laptop with
FreeBSD
For like, the two of you out there who still have an AR5210 of some
sort, please try this out.
This seems to work correctly and correctly populate the RTS duration field.
Adrian
-- Forwarded message --
From: Adrian Chadd adr...@freebsd.org
Date: 16 November 2012 18:39
Subject
On 17 November 2012 12:37, Dmitry Kolosov o...@z-up.ru wrote:
Did not found any reasons. Moved to debian linux.
That's a shame, I'd like to try and trace this particular issue down.
I've added debugging to the ath driver in -HEAD that lets us record
the actual TX and RX descriptors from the
So for the record, I have a couple of -HEAD devices up and running with TDMA.
AP:
ath0: Atheros 5413 irq 16 at device 0.0 on cardbus0
ath0: AR5413 mac 10.4 RF5413 phy 6.1
ifconfig wlan0 create wlandev ath0 wlanmode tdma
ifconfig wlan0 ssid ADRIAN_TDMA channel 48:a
ifconfig wlan0 tdmaslotcnt 2
On 17 November 2012 21:09, Joshua Isom jri...@gmail.com wrote:
When you need a beta tester, or alpha as long as my hard drives are safe,
I'll be more than willing to try.
Thanks. I'm using the AR9380 in STA mode almost every day at the
moment, without any (obvious) issues.
Hostap requires some
That's right. The atheros devices have one MAC and one radio. There
was a module which used one MAC and two radios (one 2ghz and one 5ghz)
but only one was active at a time. since there was only one MAC, you
couldn't even do dual-band concurrent operation with that.
There's nothing _stopping_ a
I don't think the RAL driver supports that card yet?
adrian
On 21 November 2012 06:23, Volodymyr Kostyrko c.kw...@gmail.com wrote:
Hi all.
I just bought a card and trying to make it work with FreeBSD.
none1@pci0:4:1:0: class=0x028000 card=0x3c051186 chip=0x53601814
rev=0x00
On 17 November 2012 15:57, Adrian Chadd adr...@freebsd.org wrote:
Now, after the work done last year to make the 11n NICs work, I
haven't sat down and tried that.
I likely should do that soon. But at least for that very specific MAC
version above, it seems to work just fine.
.. so it's
On 23 November 2012 05:40, Johann Hugo jh...@meraka.csir.co.za wrote:
Where can I find some more info on how to configure TDMA and what things one
can tweak.
Yeah, I'll have to braindump something into the Wiki.
adrian
___
On 22 November 2012 04:22, Volodymyr Kostyrko c.kw...@gmail.com wrote:
22.11.2012 03:46, Adrian Chadd wrote:
I don't think the RAL driver supports that card yet?
It certainly looks like. I was just hoping someone's got the patches and
need to test them. :)
I'll send someone cookies
On 23 November 2012 05:39, Adrian Chadd adr...@freebsd.org wrote:
On 23 November 2012 05:28, Michael Vale mas...@internode.on.net wrote:
When I get back from my holiday I will test this on numerous multi-km ptp
and ptmp links mate.
Hold off for a bit, I'm seeing some (recovered) timing drift
On 24 November 2012 22:10, Kevin Oberman kob6...@gmail.com wrote:
Adrian,
I really don't have any data and I do't like to submit a PR that
basically says It don't work good. I only have had an 'N' AP for
about three weeks and only noticed the problem a few days ago when I
copied some
On 25 November 2012 11:20, Dmitry Kolosov o...@z-up.ru wrote:
It seems like after replacing a wireless nic on my AP only 8-based laptop
refuses to work. It even associating fine, but did not received any packet
from AP after association. Same time, AP received DHCP packets from this
8-based
Hi all,
This patch collapses all of the TXQ locking down to a single TX lock
and (mostly correctly) wraps the TX outbound path in a single, giant
lock.
The TX completion path is still a patchwork of locking, primarily
because _it_ needs to be able to free net80211 node references and
that can't
On 29 November 2012 22:58, Martin na...@web.de wrote:
this is not good, if alternate MACs are not supported, because you also
need them to configure multiple access points in hostapd. Take a look
at the end of the hostapd.conf in examples. This definitely takes away
features.
Alternate MACs
On 1 December 2012 08:05, Howard Goldstein h...@queue.to wrote:
I've been beating the patched head up on an Asus EEE 701 notebook for
the better part of a day without any issues. Looks great
The 701 identifies as an AR2425/5424 (Swan) Thanks Howard
Thanks!
Adrian
Hi,
I've committed the patch, with an extra bugfix (recursive locking, eek.)
I'm now going to go through and begin un-doing the couple of LORs I
know will occur when ieee80211_free_node() is called whilst the TX
lock is held.
Please update to -HEAD and test thoroughly with WITNESS enabled.
I'm
Hi,
I've started seeing panics in the fast frames code in FreeBSD-HEAD.
It's quite possible this has been here a while; I've heard rumours
about this dating back to last year.
The reason? Because I was doing iperf tests between
AR5212/AR5413/AR5414 NICs and the HAL/driver enables the fast frames
...
On 8 December 2012 01:24, Adrian Chadd adr...@freebsd.org wrote:
* upon a node purge, there's a panic inside m_free() from
ieee80211_ff_node_cleanup(), where it dereferences a pointer
0xdeadc0de. So there's some use-after-free nonsense going
... aaand look at that, I've just fixed
Hi all,
Here's a brief(ish) braindump of my 802.11 TX path notes:
http://wiki.freebsd.org/AdrianChadd/WifiTxNotes
I'm open to the beginnings of suggesting how we can address this all
before 10.0 ships and we end up having to introduce ABI breaking
fixes.
Thanks,
Adrian
On 18 May 2012 02:33, Johann Hugo jh...@meraka.csir.co.za wrote:
Hi
We have an outdoor wifi mesh network with various atheros adapters configured
in adhoc mode. (FreeBSD-9)
Hi,
Please try -HEAD. I _think_ I've handled the WME configuration side of
things right in IBSS mode.
The problem with
Hm, there's some odd behaviour.
If I configure the WME parameters before I bring the interface up,
bringing it up overrides the parameters.
I'll do some further digging in a few minutes. Something tells me the
aggressive mode logic is overriding the configured WME parameters.
G!
Adrian
Ok, I've just taught the aggressive mode logic about IBSS. It's pretty
dirty - I may cop some hate for enabling aggressive mode for IBSS as
each IBSS node doesn't know about the overall voice/video data rates.
That's how it works in AP mode - the AP tracks the traffic _it_ is
sending/receiving and
Ok, I've started digging into this a bit more. I need to get 11n adhoc
working so I can get 11n ahdemo working, so we can actually do 11n
TDMA at some point in the near future.
There's a whole lot of missing stuff:
* ieee80211_add_neighbor() and ieee80211_init_neighbor() don't know
about HT at
Ok, wow. I think I finally understand the level of huh? going on here.
When a new BSS is created, everything now works out great. It creates
a BSS, the channel is promoted to 11n correctly, it gets the 11n IE's
populated, etc.
When you're joining a BSS however, it doesn't do any of this.
.. so now I have 11n IBSS working, but the performance is pretty
shocking. I bet there's some timers that are just not programmed
correctly.
I see massive numbers of long retries and CRC errors.
In any case, there are a few odd things out:
* ieee80211_ies_expand() doesn't parse HTINFO, only
Hm, you may be right; but I disabled HT protection entirely and stuck
it on a very quiet channel.
It's possible both ends were colliding with each other though.
I did add some HT update code to the adhoc beacon processing, though.
It's just not entirely clear how to handle that given the nature
Here's what I have trimmed this down to so far:
http://people.freebsd.org/~adrian/ath/20121212-11n-ibss-and-other-stuff-3.diff
Please disable ampdu for now (ifconfig wlanX -ampdu) as it just plain
doesn't work.
I'll figure out why once I figure out the cleanest way to get this 11n
IBSS stuff
.. hey, scratch that. 11n aggregation works in IBSS mode with my
patch, at least on ath(4).
I bet there's all kinds of weird subtle crap going on that we need to
fix, but the basics are working.
Adrian
___
freebsd-wireless@freebsd.org mailing list
(-1) ratemask 0x0
See that? The ratemask is all wrong, even for an 11a/11bg node. Maybe
how it learnt about the second node was via a different code path..
Adrian
On 12 December 2012 04:29, Johann Hugo jh...@meraka.csir.co.za wrote:
On Wednesday, December 12, 2012 01:58:38 AM Adrian Chadd wrote
.. yup, you're doing 11n! Welcome!
Adrian
On 12 December 2012 16:54, Andrey Fesenko f0and...@gmail.com wrote:
On Thu, Dec 13, 2012 at 4:44 AM, Adrian Chadd adrian.ch...@gmail.com wrote:
Yup. It's doing 11n rates.
Compile and run athstats, it'll tell you how many aggregate frames are being
Hi,
The AR9285 is a 2GHz only NIC.
The channel list shows 11b, 11bg, HT20 and HT40 channels.
It all looks right, why don't you think it is?
Adrian
On 12 December 2012 17:32, Andrey Fesenko f0and...@gmail.com wrote:
On Thu, Dec 13, 2012 at 4:55 AM, Adrian Chadd adrian.ch...@gmail.com wrote
high throughput) rates, so expect
ifconfig to grow vht information shortly.
Adrian
On 15 December 2012 08:03, Fbsd8 fb...@a1poweruser.com wrote:
Adrian
On 12 December 2012 17:39, Andrey Fesenko f0and...@gmail.com wrote:
On Thu, Dec 13, 2012 at 5:33 AM, Adrian Chadd adrian.ch...@gmail.com
On 16 December 2012 06:38, rank1see...@gmail.com wrote:
I need a card(PCI/PCIe) with Atheros bassed chip, for hostAP with 5Ghz + n
support
Hi!
After searching '/sys/dev/ath' for 'hostap' on '9.0-RELEASE-p5', 'AR5416'
came out as a lattest chip, which supports it + N ready + supports 5ghz
On 16 December 2012 10:53, rank1see...@gmail.com wrote:
Thank you Adrian
You're welcome!
So you've said: 'AR9280'
It's only bug is:
--
baseband hangs?
--
Whatever it means. ;)
The baseband occasionally needs poking. don't worry, the workarounds
are in the driver. ;)
At which aspects
The following reply was made to PR kern/174722; it has been noted by GNATS.
From: Adrian Chadd adr...@freebsd.org
To: bug-follo...@freebsd.org
Cc: Carsten Wiedmann carsten_st...@gmx.de
Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi
interface
Date: Thu, 27 Dec 2012
So I finally figured out my problem with if_transmit()'ifying the
ath(4) code. (Yes, this means I have TX fragmentation working with
ath(4), as well as some non-trivial performance improvements in TX TCP
tests.)
In quick summary: net80211's call to the driver will decrement the
node ref if the
Hm, ok, so try:
ifconfig wlan0 down
ifconfig wlan0 ecm
ifconfig wlan0 regdomain DE
ifconfig wlan0 up
ifconfig wlan0 list channel
Adrian
On 28 December 2012 04:50, Carsten Wiedmann carsten_st...@gmx.de wrote:
The following reply was made to PR kern/174722; it has been noted by GNATS.
From:
Regards,
Carsten
Original-Nachricht
Datum: Fri, 28 Dec 2012 06:29:19 -0800
Von: Adrian Chadd adr...@freebsd.org
An: Carsten Wiedmann carsten_st...@gmx.de
CC: freebsd-wireless@freebsd.org
Betreff: Re: kern/174722: [wlan] can\'t use channel 12 and 13 (14) with my
wifi interface
What's teh PCI ID of this thing?
Adrian
On 30 December 2012 21:06, Савельев Владимир vlasave...@yandex.ru wrote:
This is Acer nplify card.
Acer Nplify 802.11a/g/n + BT 4.0
31.12.2012, 04:01, Outback Dingo outbackdi...@gmail.com:
Is this a broadcom or intel wireless chip??
Hi,
On 31 December 2012 06:34, Mario Pavlov free...@abv.bg wrote:
Hi,
several months ago I found this
http://lists.freebsd.org/pipermail/freebsd-wireless/2012-June/001835.html
as an answer to the question if AR9485 is supported.
Now that FreeBSD 9.1 is out I decided to check if this chip is
On 30 December 2012 14:06, Владимир Савельев vlasave...@gmail.com wrote:
Hi, all!
I installed FreeBSD 8.3 on my Acer Aspire V3-571G and cannot configure
wireless adapter on it. Wired network works ok.
kldload if_wi says:
module_register: module pcccard/wi already exists!
Module pccard/wi
Oh god, please create a PR for that particular scenario so we don't
have that happen.
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
, etc.) once the basic FFT
visualisation is done.
Go forth and do interesting things. Oh, and please open source some of them. :)
Adrian
On 1 January 2013 20:02, Adrian Chadd adr...@freebsd.org wrote:
Author: adrian
Date: Wed Jan 2 04:02:27 2013
New Revision: 244953
URL: http
... sounds like a definite interrupt routing issue.
Who's been knee deep in the interrupt handling code in MIPS lately? Grrr.
I know there's been some FDT work in MIPS and that's touched some
interrupt code.. maybe that's interfering?
Adrian
On 2 January 2013 12:40, Monthadar Al Jaberi
...@gmail.com wrote:
On Wed, Jan 2, 2013 at 9:43 PM, Adrian Chadd adr...@freebsd.org wrote:
... sounds like a definite interrupt routing issue.
Who's been knee deep in the interrupt handling code in MIPS lately? Grrr.
I know there's been some FDT work in MIPS and that's touched some
interrupt code
On 4 January 2013 11:24, Monthadar Al Jaberi montha...@gmail.com wrote:
On Fri, Jan 4, 2013 at 8:13 PM, Adrian Chadd adr...@freebsd.org wrote:
Ok. The magic you need to try hacking is in ar71xx_pci.c. There's the
7 PCI windows and the 3 interrupt lines that are configured.
The IRQ only gets
.. odd. Is anything else behind that PCI bridge?
I can do some digging in a couple weeks; I don't have any AR9220's on
me at the moment.
Adrian
On 10 January 2013 00:07, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote:
Does it happen
i'll write up something in the next few days.
Adrian
On 10 January 2013 07:23, Sven Hazejager s...@hazejager.nl wrote:
On Wed, Jan 9, 2013 at 1:07 AM, Adrian Chadd adr...@freebsd.org wrote:
I hereby give you, AR9280 doing spectral + channel scanning:
Much appreciated, Adrian. That is great
-read
those config registers.
Thanks,
Adrian
On 12 January 2013 07:44, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Sat, Jan 12, 2013 at 07:27:02AM -0800, Adrian Chadd wrote:
Hi,
There's no firmware for the AR9220 .. it's all in the driver/HAL.
If XP restore isn't working; maybe there's
.. right, try flipping the rf kill switch off/on after suspend, dump
the config registers.
Adrian
On 12 January 2013 08:28, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Sat, Jan 12, 2013 at 07:52:19AM -0800, Adrian Chadd wrote:
Ah, is it perhaps rfkill related?
I've seen issues
On 12 January 2013 08:37, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote:
.. right, try flipping the rf kill switch off/on after suspend, dump
the config registers.
don't react -- 255 times 'ff'
Okay. Well, I'll see if there's anything
On 12 January 2013 09:13, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Sat, Jan 12, 2013 at 09:05:37AM -0800, Adrian Chadd wrote:
We can't patch pci space if they're all 0x, that means nothing is
there.
That's the point; the card hasn't come back on from suspend. So we
need to do
The problem here is I can't easily test this. We detach and re-attach
cardbus devices during suspend/resume, so although I have AR9220
mini-PCI NICs, they don't stay connected the normal way. The slot gets
fully powered down and reset upon power up.
Adrian
Right. That should be a good indication.
It's a shame you can't just get a multimeter and measure the relevant pins. :)
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe,
.. and it may not be the slot power. It could also be the PCI bridge
(re) programming. It needs to have the right BAR and such programmed
into it, or it won't route things correctly to child slots.
I had this problem with cardbus a few months ago. After a resume, not
all of the relevant PCI
It was likely a specific client.
Traffic levels can affect things - the macosx wifi stuff will do
background scans if traffic is under a certain threshold and stop it
otherwise.
Adrian
___
freebsd-wireless@freebsd.org mailing list
Hi,
The reason I haven't (yet) written any particular directions up on
this is because I'm still trying to come up with relevant workarounds
for spectral scan on the AR9280, when it's active with traffic.
Since some of you will likely enable it with traffic and then discover
that things hang
Well. Compare the other bridges too, out of interest.
Adrian
Sent from my Palm Pre on ATamp;T
On Jan 13, 2013 4:40 PM, Slawa Olhovchenkov lt;s...@zxy.spb.rugt; wrote:
On Sun, Jan 13, 2013 at 04:32:16PM -0500, Adrian Chadd wrote:
gt; Ok. So don't use that :)
gt;
gt; I'll dig up
-HEAD or -9 ?
Adrian
On 14 January 2013 15:59, Jakub Lach jakub_l...@mailplus.pl wrote:
Have dependencies changed?
I've only have ath and ath_pci, they always gave me everything I needed
for my card.
/usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar9002/ar9285_attach.c:144:35:
error:
Duh, 9-STABLE.
Guess it wasn't build tested before commit? Odd...
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
Hi,
Please list the commands that you've used?
And is anything logged in dmesg?
A lot of mesh fixes are in -HEAD, have you tried that?
Adrian
On 23 January 2013 05:11, paranormal paranor...@isgroup.com.ua wrote:
Today I was trying what mesh is.
I have ap (stable) atheros 5008 and my
Hi,
So the AR5416 and later NICs almost all implement MIMO. The only
exception is the AR9285 which is a 1x1 with the diversity
implementation matching previous (pre-11n) NICs.
Anyway, for MIMO, all the antennas are on by default. So yes, you need
to connect all of the antennas.
If you want to
Hm, see if it's a beacon miss thing:
sysctl dev.ath.0.debug=0x80
adrian
On 27 January 2013 04:31, Vincent Hoffman vi...@unsane.co.uk wrote:
Hi all,
I'm running a recent -current (r245741) and seem to be getting
interface flaps. Since this machine is mainly used for home mail and a
On 27 January 2013 09:44, Lev Serebryakov l...@freebsd.org wrote:
AC For 2GHz in noisy environments, use it in HT20 mode.
I'm using HT20, and it seems, card in my box overheats with 802.11n
clients (it hangs very hard under load with 802.11n client), so I
don't use 802.11n on notebook (I
Hi,
On 2 February 2013 07:59, Lay, Nathan ns...@my.fsu.edu wrote:
Hi Adrian,
That's a good question. I'm going to try various things this week to pinpoint
the problem. I'll let you know what I find.
Please do. I have an earlier model Roku that doesn't show any of the
same behaviour.
Hi,
The problem is that no-one's really championing / maintaining the
FreeBSD in-tree support for the rt chips.
ray@ and bschmidt@ did a bunch of work to port over some more driver
support, but they're both busy on other things now.
A few devices in FreeBSD sorely need maintainers to actively
On 9 February 2013 06:47, Eitan Adler li...@eitanadler.com wrote:
I recently encountered a kernel panic upon removing a urtw0 device.
This removal occurred during machine shutdown.
The crashing kernel and textdump is available upon request.
Unread portion of the kernel message buffer:
Yes to both - i think some USB stack / memory buffer changes are
responsible for your issue. :-)
Adrian
On 9 February 2013 15:51, Eitan Adler li...@eitanadler.com wrote:
On 9 February 2013 14:01, Adrian Chadd adr...@freebsd.org wrote:
On 9 February 2013 06:47, Eitan Adler li
35197341
Am 11.02.13 19:59, schrieb Adrian Chadd:
Hi,
Would you please look at the output of vmstat -i, see if the ath0
device is receiving interrupts?
Thanks,
Adrian
On 10 February 2013 23:30, Kamil Szczesny k.s.m...@gmx.net wrote:
Hi,
after a downgrade to 9.0-RELEASE
On 15 February 2013 21:18, Adrian Chadd adr...@freebsd.org wrote:
Oh lordie. :-)
Please file a PR so we don't forget to fix this? :)
Ok, you filed a PR with a patch.
Who can we rope in to review whether this is being done right ?
Adrian
Hi,
As part of the AR9380 support that's hopefully appearing soon, I
finally found the motivation to tidy up how the chainmask handling is
done.
The summary:
* introduce a new HAL method that changes the currently configured
TX/RX chainmask;
* leave the TX chainmask as 1 for non-HT and the
Hm, we need to use MIN(rxmax) and MAX(density) regardless, right?
If an AP is transmitting to a STA that has a lower rxmax or higher
density, it should obey that.
The same rules apply for mesh, ibss, tdma operational modes.
So yes, what we should do is:
* initialise rxmax/density with the VAP
Ah, damn. Sorry. I was thinking about the node versus vap
configuration and got confused.
IBSS is the same as the APmode of operation - you advertise what
you're capable of and sending stations just calculate the
MIN(ampdusize) and MAX(ampdudensity) when sending to you. Exactly the
same needs to
Hm, it's possible in my sleep deprived state that I'm on the right but
wrong track here.
The OP problem is that we're not advertising the right capabilities
when we associate, right?
Why aren't we just advertising the VAP ampdumax and ampdudensity no
matter what the operating mode? Why are we
Hi,
Here's take four of the TX serialisation.
http://people.freebsd.org/~adrian/ath/20130223-net80211-tx-lock-4.diff
This patch increases the lock reach so it locks the encap path for
both data and management frames, so the path between sequence number
allocation and driver queuing is held.
On 22 February 2013 15:25, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Here's take four of the TX serialisation.
http://people.freebsd.org/~adrian/ath/20130223-net80211-tx-lock-4.diff
This patch increases the lock reach so it locks the encap path for
both data and management frames, so
.. and as a reference, Linux mac80211 seems to just do TX through a
single-threaded workqueue. Ie, all of the mac80211 TX is done deferred
and serialised that way.
Grrr.. I'm very tempted to just do this and be done with it for now.
Adrian
___
On 23 February 2013 22:30, PseudoCylon moonlightak...@yahoo.ca wrote:
So, this is all pretty terrible. The only sane solution for now is to
make my VAP TX lock an IC TX lock,and grab said IC TX lock for all
VAPs. That way the driver can grab the IC TX lock when it's doing
deferred sends and
Here we go:
http://people.freebsd.org/~adrian/ath/20130225-net80211-txlock.diff
See what you think.
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
Hi,
I have finished this round of work, intended for -HEAD.
Besides the stuff in the ath and iwn driver, here's what I'd like to commit:
http://people.freebsd.org/~adrian/ath/20130303-net80211_tx-1.diff
What it implements:
* the code that transmits a VAP frame is now in ieee80211_start_pkt().
Hi,
So this stuff breaks Monthadar's meshing code.
The mesh forwarding stuff takes mesh frames in mesh_input() that are
destined for another node and potentially stuffs them back into the
parent transmit queue, bypassing the rest of the stack.
This has a bunch of potential interesting
On 4 March 2013 09:50, Lev Serebryakov l...@freebsd.org wrote:
Hello, Freebsd-wireless.
Situation (theoretical one, I didn't try it, but I'm thinking about
WiFi coverage of my parent's cottage and lot): WiFi card with 2
antennas, in 802.11g (or single-channel 802.11n) mode. Both antennas
Yup, that's what you expect for OFDM 54MB rates.
Why do you ask?
Adrian
On 4 March 2013 12:49, Dmitry Kolosov o...@z-up.ru wrote:
Hello dear FreeBSD users!
What is maximum wireless throughput you have reached (seen) on -STABLE (mean
11g only mode)? I have 54Mbps as for `ifconfig` and
1 - 100 of 1065 matches
Mail list logo
