Re: Network Event Kit serving 750+ devices at ApacheCon2012

Hi, That's fantastic news! For those who aren't quite tuned in - they're pushing out FreeBSD-8 on Alix's with Atheros 11abg NICs. No 11n NIC yet unfortunately. Adrian On 13 November 2012 12:01, Ed Kikkert wrote: > During ApacheCon2012 The Network Event Kit has served 750+ devices, > assisted

Today's wireless update - TL;DR - please test -HEAD

Hi all, Here's another hacking update. The TL;DR version - please update to -HEAD if you're testing 802.11n on ath(4). * I've finished re-engineering the TX aggregation path in preparation for the AR9380 support. Rui reported a rather subtle bug and after a few days of narrowing it down, we naile

Re: Today's wireless update - TL;DR - please test -HEAD

On 14 November 2012 22:52, Joshua Isom wrote: > I recently purchased a wireless card with an AR9380 chipset. I'm wanting to > try the driver, but would I need to update my whole kernel to -HEAD or just > the directory to -HEAD and keep the rest as -STABLE? I test things out on a combination of H

Re: Today's wireless update - TL;DR - please test -HEAD

On 15 November 2012 09:24, Joshua Isom wrote: > So I'm taking it that currently it will not work without the glue that's not > yet available? > > I'm trying to get ndis working, but it's failing to find the device. I can > run pciconf -lv and it shows that it's connected. The glue is available

Re: Strange output from ndisgen'ed driver in 10-Current

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, Гуляев Гоша wrote: >Good day! > >I'm tryin to get working wireless card RTL8723AE on my laptop with >FreeBSD 10-Current amd64 > >Fr

Fwd: svn commit: r243174 - head/sys/dev/ath/ath_hal/ar5210

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 Date: 16 November 2012 18:39 Subject: svn commit

Re: Replacing wireless nic on my router

On 17 November 2012 12:37, Dmitry Kolosov 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 driver, so we c

(Re) Verifying TDMA behaviour on -HEAD

So for the record, I have a couple of -HEAD devices up and running with TDMA. AP: ath0: 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 tdmaslot 0 td

Re: Today's wireless update - TL;DR - please test -HEAD

Yup, there's no AR9300 HAL support yet in the tree, sorry. If I could commit it right now I would. :) Adrian On 17 November 2012 20:57, Joshua Isom wrote: > On 11/15/2012 11:41 AM, Adrian Chadd wrote: >> >> On 15 November 2012 09:24, Joshua Isom wrote: >> &g

Re: (Re) Verifying TDMA behaviour on -HEAD

Oh, and if you would ever like to see 11n + TDMA work, someone first needs to make adhoc+11n work. I'm happy to help out that. I almost got it working here too adrian On 17 November 2012 15:57, Adrian Chadd wrote: > So for the record, I have a couple of -HEAD devices up and

Fixing the encryption keycache handling for the AR5210, or "things I do to avoid going out.."

Hi, I noticed that the AR5210 NIC I have here wasn't associating to WPA networks. Now, the AR5210 only implements WEP (and clear!) so it should be punting the non-WEP frames to the net80211 stack for software encryption/decryption handling. However, it was erroring out. The net80211 stack was get

Re: Today's wireless update - TL;DR - please test -HEAD

On 17 November 2012 21:09, Joshua Isom 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 further hacking

Re: Replacing wireless nic on my router

On 17 November 2012 22:25, Dmitry Kolosov wrote: > Actually it is my wife's laptop and she need to work. Anyway, i have -9 based > client and -9 based AP of my own, and of course, i am _interested_ in helping > and debuging. I am very interested in wireless on FreeBSD, and waiting for > full 1

Re: kern/173636: [ath] ath1: bad series0 hwrate 0x0, tries 1 ts_status 0x0

Right, try updating to the latest -HEAD. It should be fine. The problem was the uninitialised final descriptor in an aggregate chain, which is why you are seeing it when you flip on 11n. Adrian On 18 November 2012 23:31, Johann Hugo wrote: > On Sunday 18 November 2012 23:05:44 adr...@freebsd.

Re: Today's wireless update - TL;DR - please test -HEAD

Nope, because there's no ETA at the present moment on when I've cleared all the hurdles for an open source AR9380 HAL. On the flip side, the driver side is almost done. All that I have to do now is PAPRD training calibration support and MSI handling; then it's _just_ the HAL. So if someone wanted

Re: Today's wireless update - TL;DR - please test -HEAD

No, you need two cards. Sorry, but anything else in hostap mode is just plain madness. It's possible to do other dirty hacks (eg make p2p work, multiple station VAPs, each on different channels) but that's not currently how net80211 works. Adrian On 19 November 2012 12:09, Lev Serebryakov wro

Re: Today's wireless update - TL;DR - please test -HEAD

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 ma

Re: Today's wireless update - TL;DR - please test -HEAD

On 19 November 2012 14:24, Aleksandr Rybalko wrote: > > Hi guys! > > Lev, it seems it's time for you to get some dual-11n-nic router (like > f.e. DIR-825) and join to mips community :) Please! That works really well! Adrian ___ freebsd-wireless@freeb

Re: Today's wireless update - TL;DR - please test -HEAD

On 20 November 2012 02:16, Lev Serebryakov wrote: > Hmm... I need to give it a try. Because now 500Mhz x86 CPU can not route > my traffic with extensive firewall, NAT and other stuf, and DLink > has only 650(?) Mhz CPU. But I understand, that Mhz is not only > metric, and network chips a

Re: wifi + wpa_supplicant in 9.1-RC3

On 20 November 2012 05:52, CeDeROM wrote: > Hello :-) > > I have some problems with WiFi connectivity on my Dell Latitude E4310 > laptop with Intel card. Very often connection is broken, although > windows clients of the same network is working fine. I need to turn > radio off and on, sometimes th

Re: D-Link DWA-525 is not detected

I don't think the RAL driver supports that card yet? adrian On 21 November 2012 06:23, Volodymyr Kostyrko 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 hdr=0x00 > vend

Re: (Re) Verifying TDMA behaviour on -HEAD

On 17 November 2012 15:57, Adrian Chadd 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&#

Re: (Re) Verifying TDMA behaviour on -HEAD

On 23 November 2012 05:28, Michael Vale 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 when I'm doing iperf tests. It takes a while for it to trigger, but at least now it does r

Re: (Re) Verifying TDMA behaviour on -HEAD

On 23 November 2012 05:40, Johann Hugo 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 ___ freebsd-wireless@freebsd.org mailing list http:/

Re: D-Link DWA-525 is not detected

On 22 November 2012 04:22, Volodymyr Kostyrko 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. :)

Re: (Re) Verifying TDMA behaviour on -HEAD

On 23 November 2012 05:39, Adrian Chadd wrote: > On 23 November 2012 05:28, Michael Vale 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 when I

Re: wifi + wpa_supplicant in 9.1-RC3

On 24 November 2012 22:10, Kevin Oberman 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 multi-megabyte fi

Re: Replacing wireless nic on my router

On 25 November 2012 11:20, Dmitry Kolosov 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 laptop, an

Re: Replacing wireless nic on my router

Oh, can you -please- smack me around with the PR you filed (you filed a PR, right?) so I can backport this change to -8? Thanks, Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscr

Re: (Re) Verifying TDMA behaviour on -HEAD

and now TDMA works right with the 11n chips. They're only doing 11a rates for now, but the timer programming works. There's a bunch more work to do with the 11n chips and timer programming, mostly to figure out why the clock sync drift is slightly worse/different than the 11a cards. But I don

Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated

Hi, On 29 November 2012 11:40, Martin wrote: > The following reply was made to PR kern/149516; it has been noted by GNATS. > > From: Martin > To: bug-follo...@freebsd.org > Cc: > Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in > station dropping packets when associa

Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated

You ca'nt set the high bit in the first (left hand) octet, that means something special. Set it to 0x0d and re-test. Adrian On 29 November 2012 12:45, Martin wrote: > Am Thu, 29 Nov 2012 12:23:44 -0800 > schrieb Adrian Chadd : > >> > Confirmed on 9.0-RELEA

Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated

There was someone who posted on -wireless a while ago about how to "correctly" program different mac addresses for different VAPs. The whole setup path is a little un-intuitive and needs some love. So take a look over the -wireless archives for multi-VAP and separate mac addresses. :-) Aha. It's

Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated

Hi, Yes. As I said, the whole "configure an alternate MAC" thing isn't very consistent and I'm sure that the whole migration to VAP interfaces made some of the MAC BSSID and local ethernet card address programming "inconsistent." If you want to take a look at whta's in the card: * add ATH_DIAGAP

Please test - collapsing the TX locking down to ATH_TX_LOCK()

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 b

TDMA update: 802.11n NIC -> 802.11n NIC is now working stable (alas at 802.11a rates..)

Hi, I meant to post this last night but fell asleep. :-) I've verified that the 11n NIC <-> 11n NIC TDMA setup is working and working stable. I haven't yet run it over the course of "time needed to wrap a 32 bit TSF", so that's next. In this instance: * TDMA master: AR9280 * TDMA slave: AR5416

Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip.

It's not that simple. Speak to bernhard. There are other issues that he knows about. I don't know if he's replied to the email or not; poke him on irc. adrian On 30 November 2012 15:25, wrote: > Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip. > > Responsible-Changed-From-To: freebsd-

Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated

On 29 November 2012 22:58, Martin 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 are suppo

Re: Please test - collapsing the TX locking down to ATH_TX_LOCK()

On 1 December 2012 08:05, Howard Goldstein 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 __

Re: Please test - collapsing the TX locking down to ATH_TX_LOCK()

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

Re: Problem with Atheros card, regression? Layer 8 problem?

Hi, If it's not recognising the card then it's either a whacky PCI bus code problem, or the device is just plainly not being seen by the motherboard or BIOS. Can you try booting Linux and see if it sees the PCI device? Adrian On 2 December 2012 23:42, Derek Kulinski wrote: > Hello Adrian, >

Re: Problem with Atheros card, regression? Layer 8 problem?

That's really good to know! Thanks! Adrian On 3 December 2012 22:20, Derek Kulinski wrote: > Hello Adrian, > > So I figured the problem out. > > This is how it went. I booted OpenSuSE and couldn't find the device as > well... > > At that point I was sure that the problem is with my PC. I deci

Hm, somehow the fast frames code is broken (surprise)

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

Re: Hm, somehow the fast frames code is broken (surprise)

... On 8 December 2012 01:24, Adrian Chadd 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 jus

Re: rum0 based USB wireless adapter dumps core

Oo, someone else has seen this bug! I'm honestly not sure what's going on here. I think we can just disable that panic and ensure that we don't somehow end up with a stalled powersave queue. Adrian On 8 December 2012 23:37, Volodymyr Kostyrko wrote: > Hi all. > > I recently acquired another de

TX path serialisation notes

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 __

Re: [ath] Degraded throughput - adhoc mode

On 18 May 2012 02:33, Johann Hugo 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 IBSS is that nodes

Re: [ath] Degraded throughput - adhoc mode

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 ___

Re: [ath] Degraded throughput - adhoc mode

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

Re: 11n in adhoc mode

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 al

Re: 11n in adhoc mode

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. adhoc_

Re: 11n in adhoc mode

.. 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 HTCAP

Re: 11n in adhoc mode

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 o

Re: 11n in adhoc mode

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 work

Re: 11n in adhoc mode

.. 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 ht

Re: 11n in adhoc mode

(-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 wrote: > On Wednesday, December 12, 2012 01:58:38 AM Adrian Chadd wrote: > >> H

Re: AR9285 not see n-channels

What's 'ifconfig wlan0' and 'ifconfig wlan0 list sta' look like? adrian On 12 December 2012 15:51, Andrey Fesenko wrote: > I have > # uname -a > FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 > r243259: Mon Nov 19 09:28:08 MSK 2012 > root@beastie.mydomain.local:/usr/obj/u

Re: AR9285 not see n-channels

Yup. It's doing 11n rates. Compile and run athstats, it'll tell you how many aggregate frames are being sent and received. Adrian Sent from my Palm Pre on AT&T On Dec 12, 2012 4:39 PM, Andrey Fesenko <f0and...@gmail.com> wrote: On Thu, Dec 13, 2012 at 4:32 A

Re: AR9285 not see n-channels

.. yup, you're doing 11n! Welcome! Adrian On 12 December 2012 16:54, Andrey Fesenko wrote: > On Thu, Dec 13, 2012 at 4:44 AM, Adrian Chadd wrote: >> Yup. It's doing 11n rates. >> >> Compile and run athstats, it'll tell you how many aggregate f

Re: AR9285 not see n-channels

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 wrote: > On Thu, Dec 13, 2012 at 4:55 AM, Adrian Chadd wrote: >> .. yup, you're

Re: AR9285 not see n-channels

Right, that's what "HT" is for. Adrian On 12 December 2012 17:39, Andrey Fesenko wrote: > On Thu, Dec 13, 2012 at 5:33 AM, Adrian Chadd wrote: >> Hi, >> >> The AR9285 is a 2GHz only NIC. >> >> The channel list shows 11b, 11bg, HT20 and HT40 c

Re: AR9285 not see n-channels

ghput) is. 802.11ac is adding "VHT" (very high throughput) rates, so expect ifconfig to grow vht information shortly. Adrian On 15 December 2012 08:03, Fbsd8 wrote: > >> Adrian >> >> On 12 December 2012 17:39, Andrey Fesenko wrote: >>> >>> O

Re: Atheros chip for FreeBSD Access Point

On 16 December 2012 06:38, 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 + > supports hard

Re: Atheros chip for FreeBSD Access Point

On 16 December 2012 10:53, 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 is 'AR9280' in

Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface

The following reply was made to PR kern/174722; it has been noted by GNATS. From: Adrian Chadd To: bug-follo...@freebsd.org Cc: Carsten Wiedmann Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface Date: Thu, 27 Dec 2012 19:57:55 -0800 Hi, This m

.. if_transmit() and the quirky issues with node referencing

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 dri

Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface

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 wrote: > The following reply was made to PR kern/174722; it has been noted by GNATS. > > From: "Carsten Wiedmann

Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface

rogram to construct regula- > | tory state for download to the system. > > > And in "/etc/regdomain.xml" I have: > | > | ETSI > | 0x30 > | > | > | > | 30 > | IEEE80211_CHAN_B > | > | > | > | > |

Re: Cannot bring up wireless adapter on Acer notebook

What's teh PCI ID of this thing? Adrian On 30 December 2012 21:06, Савельев Владимир wrote: >This is Acer nplify card. > >Acer Nplify 802.11a/g/n + BT 4.0 > >31.12.2012, 04:01, "Outback Dingo" : > >Is this a broadcom or intel wireless chip?? or an Acer Nplify card > >On Su

Re: AR9485 support

Hi, On 31 December 2012 06:34, Mario Pavlov 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 already

Re: Cannot bring up wireless adapter on Acer notebook

On 30 December 2012 14:06, Владимир Савельев 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 failed to re

Re: if_transmit() and the quirky issues with node referencing

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 "freebsd-wireless-uns

Skeleton spectral scan driver support is in -HEAD (was Re: svn commit: r244953 - in head/tools/tools/ath: . athspectral)

uous" reporting, 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 wrote: > Author: adrian > Date: Wed Jan 2 04:02:27 2013 > New Revision: 244953 >

Re: ath0: could not map interrupt

... 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 wrote:

Re: ath0: could not map interrupt

you in advance >> >> On Wed, Jan 2, 2013 at 10:29 PM, Monthadar Al Jaberi >> wrote: >>> On Wed, Jan 2, 2013 at 9:43 PM, Adrian Chadd wrote: >>>> ... sounds like a definite interrupt routing issue. >>>> >>>> Who's been knee

Re: ath0: could not map interrupt

On 4 January 2013 11:24, Monthadar Al Jaberi wrote: > On Fri, Jan 4, 2013 at 8:13 PM, Adrian Chadd 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

[CFT] ath(4) migration to if_transmit() and a transmit tasklet, rather than direct dispatch

Hi, I've written up a replacement ath(4) TX path that does a bunch of things. The patch I'd like everyone to try: http://people.freebsd.org/~adrian/ath/20130105-if_transmit_txfrag_2.diff What it does: * It implements a driver staging queue for frames from if_start and if_transmit(); * It popul

freebsd-head and spectral scan

I hereby give you, AR9280 doing spectral + channel scanning: http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe,

Re: freebsd-head and spectral scan

Primarily- to look at inteference sources. Adrian Sent from my Palm Pre on AT&T On Jan 9, 2013 10:59 AM, Vincent Hoffman <vi...@unsane.co.uk> wrote: On 09/01/2013 00:07, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: > > http:/

Re: Atheros 9220 don't return from S3 state

Does it happen every time? Which version of freebsd is it? Adrian Sent from my Palm Pre on AT&T On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov wrote: I am try play with suspend resume and see Atheros 9220 don't return from s3 state: [833] ath0: unable to reset hardware;

Re: Atheros 9220 don't return from S3 state

.. 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 wrote: > On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote: > > >

Re: freebsd-head and spectral scan

i'll write up something in the next few days. Adrian On 10 January 2013 07:23, Sven Hazejager wrote: > On Wed, Jan 9, 2013 at 1:07 AM, Adrian Chadd wrote: >> I hereby give you, AR9280 doing spectral + channel scanning: > > Much appreciated, Adrian. That is great functi

Re: Atheros 9220 don't return from S3 state

.. so there's no _specific_ code being run when it goes to sleep or comes back from sleep for the 11n PCI NICs (AR5416, AR9160, AR9220, AR9227..) .. there's some code to tinker with the internal reset line(s) that force the hardware to re-initialise, but that's not appropriate for you. The problem

Re: Debugging Stalls with ath(4)

... oh this is kind of strange. Hm, it's interesting that it's delaying that much; I wonder if the air is really busy and the transmitter just can't squeeze a frame out into the air. How close is it? What's the RSSI? adrian On 8 January 2013 15:50, Andrew wrote: > Hi, > > I just installed a T

Re: Debugging Stalls with ath(4)

.. ok, so reading about this a bit more. Going in and out of power save state could be it. Having it wait for a second is possible when you're in power save, because it's quite possible that the device is _in_ power save state for that long. Enable power state debugging in net80211 and see what's

Re: Atheros 9220 don't return from S3 state

Hi, There's no firmware for the AR9220 .. it's all in the driver/HAL. If XP restore isn't working; maybe there's something in the ACPI/BIOS that's screwing things up? Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailm

Re: Atheros 9220 don't return from S3 state

ur keyboard, then re-read those config registers. Thanks, Adrian On 12 January 2013 07:44, Slawa Olhovchenkov 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

Re: Atheros 9220 don't return from S3 state

.. right, try flipping the rf kill switch off/on after suspend, dump the config registers. Adrian On 12 January 2013 08:28, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 07:52:19AM -0800, Adrian Chadd wrote: > >> Ah, is it perhaps rfkill related? >> >> I&#x

Re: Atheros 9220 don't return from S3 state

On 12 January 2013 08:37, Slawa Olhovchenkov 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. We

Re: Atheros 9220 don't return from S3 state

I don't know the first thing about ACPI, I'm sorry. Perhaps ask on the freebsd acpi list? Adrian On 12 January 2013 08:52, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: > >> On 12 January 2013 08:37, Slawa Olhovchenkov wrot

Re: Atheros 9220 don't return from S3 state

PCI bus. Adrian On 12 January 2013 09:07, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote: > >> I don't know the first thing about ACPI, I'm sorry. > > OK, what about "patching" pci config space? Remove indication of

Re: Atheros 9220 don't return from S3 state

On 12 January 2013 09:13, Slawa Olhovchenkov 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

Re: Atheros 9220 don't return from S3 state

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 __

Re: Atheros 9220 don't return from S3 state

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, se

Re: Atheros 9220 don't return from S3 state

.. 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 conf

Re: Atheros 9220 don't return from S3 state

On 13 January 2013 12:07, Slawa Olhovchenkov wrote: > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > >> Right. That should be a good indication. > > After 10 min card still hot. Ok, so that means the basic power lines are up and working. Ah, I did add in the

Re: Debugging Stalls with ath(4)

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 http://lists.freebsd

Re: freebsd-head and spectral scan

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 (and

Re: Atheros 9220 don't return from S3 state

t;s...@zxy.spb.ru> wrote: On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: > On 13 January 2013 12:07, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > > > >> Right. That should be a

Re: Atheros 9220 don't return from S3 state

Well. Compare the other bridges too, out of interest. Adrian Sent from my Palm Pre on AT&T On Jan 13, 2013 4:40 PM, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: On Sun, Jan 13, 2013 at 04:32:16PM -0500, Adrian Chadd wrote: > Ok. So don't use that :) > > I&

<    1   2   3   4   5   6   7   8   9   10   >