[Bug 230654] [ath] AR9485 will not connect when wlan MAC address is changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230654 Ian changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New

[Bug 230654] [ath] AR9485 will not connect when wlan MAC address is changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230654 --- Comment #1 from Ian --- Oops, this appears to be a duplicate of bug #213207. Sorry for the noise. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wirel

[Bug 230654] [ath] AR9485 will not connect when wlan MAC address is changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230654 Bug ID: 230654 Summary: [ath] AR9485 will not connect when wlan MAC address is changed Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS

[Bug 179547] [ath] Add AR9485 custom board fixes (CUS198)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179547 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #2 from Eitan Adler

Re: Atheros AR9485 slow connection

FreeBSD 10-RELEASE. I have a AR9485 wireless card and > getting =~ 150kB/s, but in Linux I get the real paid speed =~ 2MB/s. > > Any idea? > > Thanks. > ___ > freebsd-wireless@freebsd.org mailing list > https://lists.freeb

Atheros AR9485 slow connection

Hi all, I'm using FreeBSD 12-CURRENT and I get a very slow speed connection since when I was in FreeBSD 10-RELEASE. I have a AR9485 wireless card and getting =~ 150kB/s, but in Linux I get the real paid speed =~ 2MB/s. Any idea? Thanks. ___ fr

[Bug 200598] Atheros AR9485 and AR8161 Network Adapter both does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200598 siliang@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|Ne

[Bug 200598] Atheros AR9485 and AR8161 Network Adapter both does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200598 --- Comment #2 from siliang@gmail.com --- (In reply to Adrian Chadd from comment #1) Thanks! It got to work when use CU -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 200598] Atheros AR9485 and AR8161 Network Adapter both does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200598 Adrian Chadd changed: What|Removed |Added CC||adr...@freebsd.org --- Comment #1 f

[Bug 200598] Atheros AR9485 and AR8161 Network Adapter both does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200598 Bug ID: 200598 Summary: Atheros AR9485 and AR8161 Network Adapter both does not work Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS

AR9485

:2:0:0: class=0x03 card=0xc609144d chip=0x67601002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'Caicos [Radeon HD 6400M/7400M Series]' class = display subclass = VGA re0@pci0:3:0:0: class=0x02 card=0xc608144d chi

Re: atheros ar9485

it's in -head. ;) -adrian On 2 August 2013 19:17, H.W. Neff wrote: > hi. > > what is the status of the/any driver for the atheros ar9485 wifi adapter? > > cheers! > hwn > ___ > freebsd-wireless@freebsd.org mailing li

atheros ar9485

hi. what is the status of the/any driver for the atheros ar9485 wifi adapter? cheers! hwn ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wir

Re: kern/179547: [ath] Add AR9485 custom board fixes (CUS198)

Synopsis: [ath] Add AR9485 custom board fixes (CUS198) Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 16 23:44:47 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/17/2013 9:43 AM, Li-Wen Hsu wrote: Oops, accidentally clicked on "send." Before the changes you made yesterday, I can only see it got found by kernel, but was unable to get IP through DHCP, and the status of wlan0 was flipping between associated and no carrier, while ath0 is always associa

Re: Fine, OK, here's my initial AR9380/AR9485 support

Fixed! Adrian On 17 March 2013 15:27, Joshua Isom wrote: > There's no issues for the fork, only the master. > > > On 3/17/2013 4:40 PM, Adrian Chadd wrote: >> >> Just go to my github - github.com/erikarn/ - then click on >> repositories, then the HAL fork, then just file an issue there. >> >>

Re: Fine, OK, here's my initial AR9380/AR9485 support

There's no issues for the fork, only the master. On 3/17/2013 4:40 PM, Adrian Chadd wrote: Just go to my github - github.com/erikarn/ - then click on repositories, then the HAL fork, then just file an issue there. Adrian ___ freebsd-wireless@fre

Re: Fine, OK, here's my initial AR9380/AR9485 support

Just go to my github - github.com/erikarn/ - then click on repositories, then the HAL fork, then just file an issue there. Adrian On 17 March 2013 14:22, Joshua Isom wrote: > How do you file a bug report against the fork? > > > On 3/16/2013 7:25 PM, Adrian Chadd wrote: >> >> On 15 March 2013

Re: Fine, OK, here's my initial AR9380/AR9485 support

How do you file a bug report against the fork? On 3/16/2013 7:25 PM, Adrian Chadd wrote: On 15 March 2013 15:33, Joshua Isom wrote: ar9300_set_stub_functions: setting stub functions ar9300_set_stub_functions: setting stub functions ar9300_attach: calling ar9300_hw_attach ar9300_hw_attach: cal

Re: Fine, OK, here's my initial AR9380/AR9485 support

On Sun, Mar 17, 2013 at 10:07 PM, Li-Wen Hsu wrote: > On Sun, Mar 17, 2013 at 2:23 PM, Adrian Chadd wrote: >> I've just fixed a couple things with the AR9300 HAL: >> >> * I've implemented a "get slot time" method, so one stub function call >> message should disappear; >> * I've fixed a quirk with

Re: Fine, OK, here's my initial AR9380/AR9485 support

On Sun, Mar 17, 2013 at 2:23 PM, Adrian Chadd wrote: > I've just fixed a couple things with the AR9300 HAL: > > * I've implemented a "get slot time" method, so one stub function call > message should disappear; > * I've fixed a quirk with slot/ack/rtscts timeout calculations in HT40 > - the AR9300

Re: Fine, OK, here's my initial AR9380/AR9485 support

I've just fixed a couple things with the AR9300 HAL: * I've implemented a "get slot time" method, so one stub function call message should disappear; * I've fixed a quirk with slot/ack/rtscts timeout calculations in HT40 - the AR9300 HAL was compensating for the 40Mhz width of the channel, but Fre

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 15 March 2013 15:33, Joshua Isom wrote: >> ar9300_set_stub_functions: setting stub functions >> ar9300_set_stub_functions: setting stub functions >> ar9300_attach: calling ar9300_hw_attach >> ar9300_hw_attach: calling ar9300_eeprom_attach >> ar9300_flash_map: unimplemented for now >> Restoring

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/15/2013 11:00 AM, Adrian Chadd wrote: Yes, you can't have both ethernet and wireless up on the same L2 network like that; things will get confused. Does it all work fine if you don't have ethernet configured? adrian Removing the DHCP variable for the ethernet wasn't enough, I also had

Re: Fine, OK, here's my initial AR9380/AR9485 support

... and can you please post a dmesg output, so I can see it actually attaching right? :) Adrian On 15 March 2013 09:00, Adrian Chadd wrote: > Yes, you can't have both ethernet and wireless up on the same L2 > network like that; things will get confused. > > Does it all work fine if you don't

Re: Fine, OK, here's my initial AR9380/AR9485 support

Yes, you can't have both ethernet and wireless up on the same L2 network like that; things will get confused. Does it all work fine if you don't have ethernet configured? adrian On 15 March 2013 06:52, Joshua Isom wrote: > I got it all working after removing the driver from the kernelconfig an

Re: Fine, OK, here's my initial AR9380/AR9485 support

I got it all working after removing the driver from the kernelconfig and a few other tweaks. I'll post an ugly diff later when I can. I was able to get the network working only after I forced the wired down and commented out the rc.conf references. DHCP worked but no routing, not even the rou

Re: Fine, OK, here's my initial AR9380/AR9485 support

.. as a side note, if someone has a laptop with an AR9565 (WB335) in it, please test my HAL out and let me know how it goes. I don't yet have one to test with but the HAL should "just work". Thanks, Adrian ___ freebsd-wireless@freebsd.org mailing lis

Re: Fine, OK, here's my initial AR9380/AR9485 support

Did you remove ath/ath_hal/ath_rate_sample from your kernel config file when you rebuilt? The default system ships with ath/ath_hal/ath_rate_sample compiled into the kernel rather than as modules. Thanks, Adrian On 14 March 2013 19:57, Joshua Isom wrote: > On 3/14/2013 9:20 PM, Adrian Chadd

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/14/2013 9:20 PM, Adrian Chadd wrote: Oh! http://wikidevi.com/wiki/TP-LINK_TL-WDN4800 Silly me, I was reading the wrong number on my phone. Yes, 0x0030 is Osprey (AR9380.) kldload if_ath_pci too. :-) Adrian Something weird happened. My config has ath_pci listed, but then I get thi

Re: Fine, OK, here's my initial AR9380/AR9485 support

>>> >>> >>> Sent from my Palm Pre on AT&T >>> >>> >>> >>> On Mar 14, 2013 6:31 PM, Joshua Isom wrote: >>> >>> On 3/13/2013 7:31 PM, Adrian Chadd w

Re: Fine, OK, here's my initial AR9380/AR9485 support

d wrote: >>> >>> On 9 March 2013 10:54, Adrian Chadd wrote: >>> >>>> What's tested: >>>> >>>> * legacy, 1x1 and 2x2 HT20/HT40, STA mode >>>> * AR9380 (1x1, 2x2 - 2/5ghz) >>>> * AR9485 (1x1, 2ghz only) >

Re: Fine, OK, here's my initial AR9380/AR9485 support

1 and 2x2 HT20/HT40, STA mode * AR9380 (1x1, 2x2 - 2/5ghz) * AR9485 (1x1, 2ghz only) I can now add two more NICs to this list: * AR9390 (HB116) * AR9462 (WB225) Thanks, Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/

Re: Fine, OK, here's my initial AR9380/AR9485 support

wrote: > On 9 March 2013 10:54, Adrian Chadd <adr...@freebsd.org> wrote: > >> What's tested: >> >> * legacy, 1x1 and 2x2 HT20/HT40, STA mode >> * AR9380 (1x1, 2x2 - 2/5ghz) >> * AR9485 (1x1, 2ghz only) > > I can now add two more NICs t

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/13/2013 7:31 PM, Adrian Chadd wrote: On 9 March 2013 10:54, Adrian Chadd wrote: What's tested: * legacy, 1x1 and 2x2 HT20/HT40, STA mode * AR9380 (1x1, 2x2 - 2/5ghz) * AR9485 (1x1, 2ghz only) I can now add two more NICs to this list: * AR9390 (HB116) * AR9462 (WB225) T

Re: Fine, OK, here's my initial AR9380/AR9485 support

... oh, that's with the smartantenna support. Which I guess they've never actually _put_ on a 64 bit platform. so it's doing direct SOC GPIO port accesses from the HAL. That's .. ew. Anyway. I've just fixed it; so please update your git repo and the bad code will magically not compile in any lon

Re: Fine, OK, here's my initial AR9380/AR9485 support

Can you please post the patch and the specific compile issue? adrian On 13 March 2013 18:41, Joshua Isom wrote: > I added a cast to u_int64_t first on line 63 of ar9300_gpio.c to get it to > compile. I imagine (void *) would be prefered, but I don't know what's > actually correct. Unfortuna

Re: Fine, OK, here's my initial AR9380/AR9485 support

I added a cast to u_int64_t first on line 63 of ar9300_gpio.c to get it to compile. I imagine (void *) would be prefered, but I don't know what's actually correct. Unfortunately, I get a kernel panic on boot with scsi_cd, so I'll have to wait until that's dealt with before trying the ath driv

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 9 March 2013 10:54, Adrian Chadd wrote: > What's tested: > > * legacy, 1x1 and 2x2 HT20/HT40, STA mode > * AR9380 (1x1, 2x2 - 2/5ghz) > * AR9485 (1x1, 2ghz only) I can now add two more NICs to this list: * AR9390 (HB116) * AR9462 (WB22

Re: Fine, OK, here's my initial AR9380/AR9485 support

Hi, I've fixed some warnings - please update the git repo youre using. I've also added some clang workarounds in the MAkefile (see the bottom of the file for the two lines to update) - so please svn update in sys/modules/ath/ Hopefully that works enough for you! Please let me know what other bui

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/12/2013 4:14 PM, Adrian Chadd wrote: On 12 March 2013 14:12, Joshua Isom wrote: I had to remove the /sys/ from the PATH and CFLAGS to point to the right directory, it's still failing with warnings. I tried gcc and clang. I'll try to see how much I can patch myself without knowing the code

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/12/2013 4:14 PM, Adrian Chadd wrote: On 12 March 2013 14:12, Joshua Isom wrote: I had to remove the /sys/ from the PATH and CFLAGS to point to the right directory, it's still failing with warnings. I tried gcc and clang. I'll try to see how much I can patch myself without knowing the code

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 12 March 2013 14:12, Joshua Isom wrote: > I had to remove the /sys/ from the PATH and CFLAGS to point to the right > directory, it's still failing with warnings. I tried gcc and clang. I'll > try to see how much I can patch myself without knowing the code at all. Hi, Where's it failing with

Re: Fine, OK, here's my initial AR9380/AR9485 support

I had to remove the /sys/ from the PATH and CFLAGS to point to the right directory, it's still failing with warnings. I tried gcc and clang. I'll try to see how much I can patch myself without knowing the code at all. On 3/11/2013 10:25 PM, Adrian Chadd wrote: Ok, I see that clang is doing so

Re: Fine, OK, here's my initial AR9380/AR9485 support

Ok, I see that clang is doing some odd expansion there. I've poked the clang nerds about it, I'll see what they say. Anyway - I've shifted its location - now please create a new directory - sys/contrib/dev/ath/ath_hal/ar9300/, and put your symlinks in there. Then uncomment in ath/Makefile like th

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 11 March 2013 17:43, Adrian Chadd wrote: > .. and yeah, that code is wrong. GCC doesn't complain; just change it to: > > if ((ahp->ah_enterprise_mode && AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && > > to: > > if ((ahp->ah_enterprise_mode & AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && > > Thanks,

Re: Fine, OK, here's my initial AR9380/AR9485 support

I had tried the buildworld with -DWITHOUT_CLANG at one point, partially to speed up buildworld since building clang is slow without large amounts of memory. Most of the errors were the same, so my last buildworld was just stock. On 3/11/2013 7:41 PM, Adrian Chadd wrote: Is this with clang?

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 11 March 2013 17:43, Adrian Chadd wrote: > .. and yeah, that code is wrong. GCC doesn't complain; just change it to: > > if ((ahp->ah_enterprise_mode && AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && > > to: > > if ((ahp->ah_enterprise_mode & AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && > > Thanks,

Re: Fine, OK, here's my initial AR9380/AR9485 support

.. and yeah, that code is wrong. GCC doesn't complain; just change it to: if ((ahp->ah_enterprise_mode && AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && to: if ((ahp->ah_enterprise_mode & AR_ENT_OTP_MIN_PKT_SIZE_DISABLE) && Thanks, this is the first bug that I can file as having come from

Re: Fine, OK, here's my initial AR9380/AR9485 support

Is this with clang? adrian On 11 March 2013 17:39, Joshua Isom wrote: > Still no luck, and some errors look like I'm missing more. > > > /root/ATH/head/sys/modules/ath/../../dev/ath/ath_hal/ar9003/ar9300_misc.c:853:38: > error: use of logical '&&' with constant operand > [-Werror,-Wconstant-

Re: Fine, OK, here's my initial AR9380/AR9485 support

Still no luck, and some errors look like I'm missing more. /root/ATH/head/sys/modules/ath/../../dev/ath/ath_hal/ar9003/ar9300_misc.c:853:38: error: use of logical '&&' with constant operand [-Werror,-Wconstant-logical-operand] if ((ahp->ah_enterprise_mode && AR_ENT_OTP_MIN_PKT_SIZE_DIS

Re: Fine, OK, here's my initial AR9380/AR9485 support

Ooh.. add the debug options to your kernel, sorry! options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI I'm sorry, I've never tested it outside of a debug build before. Adrian On 11 March 2013 16:38, Joshua Isom wrote: > Here's me retrying everything. I also tried running make with -DAH

Re: Fine, OK, here's my initial AR9380/AR9485 support

Here's me retrying everything. I also tried running make with -DAH_DEBUG and -DAH_DEBUG_ALQ, but I also got errors messages that made me think the variables didn't propagate to the source files. [jri:~/ATH/head] root# uname -a FreeBSD jri.homeunix.com 9.1-STABLE FreeBSD 9.1-STABLE #1: Thu Jan

Re: Fine, OK, here's my initial AR9380/AR9485 support

Try this: adrian@cynthia:~/git/github/erikarn$ g...@github.com:erikarn/qcamain_open_hal_public.git -bash: g...@github.com:erikarn/qcamain_open_hal_public.git: No such file or directory adrian@cynthia:~/git/github/erikarn$ git clone https://github.com/erikarn/qcamain_open_hal_public.git Cloning int

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 3/10/2013 9:00 PM, Adrian Chadd wrote: Yes, you need to do this: Git clone ... Cd openhal... Git checkout local/freebsd It'll create the branch based off of my branch in git. Then do the ln -s ing.. Then build. Adrian Here's the commands I tried: cd /root/ATH git clone https://github

Re: Fine, OK, here's my initial AR9380/AR9485 support

Yes, you need to do this: Git clone ... Cd openhal... Git checkout local/freebsd It'll create the branch based off of my branch in git. Then do the ln -s ing.. Then build. Adrian Sent from my Palm Pre on AT&T On Mar 10, 2013 5:07 PM, Rui Paulo wrote: On 2013/03/10, at

Re: Fine, OK, here's my initial AR9380/AR9485 support

On 2013/03/10, at 16:35, Joshua Isom wrote: > It's my first time using git, so there's a learning curve. I'm building on > 9-STABLE, but because of yacc I am doing a buildworld first. First it fails > with ichan not being used in ar9300_radio.c. I commented it out, rebuilt, > and then it fa

Re: Fine, OK, here's my initial AR9380/AR9485 support

It's my first time using git, so there's a learning curve. I'm building on 9-STABLE, but because of yacc I am doing a buildworld first. First it fails with ichan not being used in ar9300_radio.c. I commented it out, rebuilt, and then it fails with the errors listed below. I was using -j, bu

Re: Fine, OK, here's my initial AR9380/AR9485 support

You didn't check out the local/freebsd branch. On 10 March 2013 09:29, Joshua Isom wrote: > I patched according to the instructions, but it fails with these four > missing files: > > ash_amem.h > ar9300_freebsd.c > ar9300_stub_funcs.c > ar9300_stub.c > > I tried commenting them out, the .c files

Re: Fine, OK, here's my initial AR9380/AR9485 support

I patched according to the instructions, but it fails with these four missing files: ash_amem.h ar9300_freebsd.c ar9300_stub_funcs.c ar9300_stub.c I tried commenting them out, the .c files in the makefile, ash_amem.h in the .c file, but the build fails. ___

Fine, OK, here's my initial AR9380/AR9485 support

or your equipment or whether this breaks the RF around you. Don't be a dick. It's your responsibility." What's tested: * legacy, 1x1 and 2x2 HT20/HT40, STA mode * AR9380 (1x1, 2x2 - 2/5ghz) * AR9485 (1x1, 2ghz only) What's not tested: * Any hostap, mesh, tdma, adhoc

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

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

AR9485 support

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 supported but unfortunately it is still not. So when would be