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

2013-03-17 Thread Adrian Chadd
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

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

2013-03-17 Thread Joshua Isom
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 ___

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

2013-03-17 Thread Adrian Chadd
Fixed! Adrian On 17 March 2013 15:27, Joshua Isom jri...@gmail.com 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

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

2013-03-14 Thread Joshua Isom
On 3/13/2013 7:31 PM, Adrian Chadd 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 to this list: * AR9390 (HB116) * AR9462

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

2013-03-14 Thread Adrian Chadd
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 On 14 March 2013 19:18, Joshua Isom jri...@gmail.com wrote: Not a laptop, but here's the vendor's website.

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

2013-03-14 Thread Adrian Chadd
.. and here I am, hoping you're user #1 (with me being user #0) of this HAL. :) Adrian On 14 March 2013 19:20, Adrian Chadd adrian.ch...@gmail.com 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

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

2013-03-14 Thread Joshua Isom
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

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

2013-03-13 Thread Adrian Chadd
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 to this list: * AR9390 (HB116) * AR9462 (WB225) Thanks, Adrian

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

2013-03-13 Thread Joshua Isom
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

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

2013-03-13 Thread Adrian Chadd
Can you please post the patch and the specific compile issue? adrian On 13 March 2013 18:41, Joshua Isom jri...@gmail.com 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

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

2013-03-13 Thread Adrian Chadd
... 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

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

2013-03-12 Thread Joshua Isom
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

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

2013-03-11 Thread Adrian Chadd
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

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

2013-03-11 Thread Joshua Isom
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

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

2013-03-11 Thread Adrian Chadd
Is this with clang? adrian On 11 March 2013 17:39, Joshua Isom jri...@gmail.com 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

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

2013-03-11 Thread Adrian Chadd
.. 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 the

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

2013-03-11 Thread Adrian Chadd
On 11 March 2013 17:43, Adrian Chadd adr...@freebsd.org 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)

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

2013-03-11 Thread Joshua Isom
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

2013-03-11 Thread Adrian Chadd
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

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

2013-03-10 Thread Joshua Isom
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.

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

2013-03-10 Thread Adrian Chadd
You didn't check out the local/freebsd branch. On 10 March 2013 09:29, Joshua Isom jri...@gmail.com 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

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

2013-03-10 Thread Joshua Isom
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,

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

2013-03-10 Thread Rui Paulo
On 2013/03/10, at 16:35, Joshua Isom jri...@gmail.com 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,

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

2013-03-10 Thread Adrian Chadd
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 ATamp;T On Mar 10, 2013 5:07 PM, Rui Paulo lt;rpa...@felyko.comgt; wrote: On

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

2013-03-09 Thread Adrian Chadd
I finally got the legal all-clear to push this open source version of the QCA mainline HAL into open source. So, without further ado: https://github.com/qca/ The open HAL is there. I then forked it: https://github.com/erikarn/qcamain_open_hal_public .. and then I created a branch, called