Re: AR6003 concurrent AP+STA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Nick,

Sounds awesome, looking forward to testing it :-) We have the fw-4 I
believe, so that's probably not a problem.

Best,
Attila

On Mon, Jan 19, 2015 at 3:22 PM, Stevens, Nick
<Nick.Stevens@xxxxxxxxxxxx> wrote:
> Hi Attila,
>
> Thanks for poking me - I meant to message the mailing list earlier.
>
> It turns out that in order to get concurrent mode, the fw-4 firmware is needed. The latest firmware available in the linux-firmware repo is fw-3. Some additional patches to the driver were also needed to get everything working.
>
> My plan is to get the patches we created submitted to upstream. I am also checking within our company to see if I can make the patches available now through our GitHub account. I'll message the mailing list when that's available.
>
> Thanks!
> Nick
>
>> -----Original Message-----
>> From: Attila Sukosd [mailto:attila@xxxxxxxxxxx]
>> Sent: Friday, January 16, 2015 2:29 AM
>> To: Stevens, Nick
>> Cc: ath6kl@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: AR6003 concurrent AP+STA
>>
>> Hi Nick,
>>
>> Did you have some success with this?
>> Looking to do the same here too.
>>
>> Cheers,
>> Attila
>>
>> On Wed, Dec 17, 2014 at 8:52 PM, Stevens, Nick <Nick.Stevens@xxxxxxxxxxxx>
>> wrote:
>> > Hi all,
>> >
>> > I am attempting to use an AR6003 in a concurrent AP/station mode. Using
>> the iw tool to try and add a second virtual interface gives me the
>> following error:
>> >   > iw phy phy0 interface add wlan0_ap type __ap
>> >     ath6kl: Not a supported interface type
>> >
>> > I get the same thing for "managed" and "station" types.
>> >
>> > I've traced the error back into the kernel to a check against available
>> VIFs. It seems that the driver is being loaded with "1" for the max_vif's,
>> which is strange since I know this device supports AP+STA.
>> >
>> > In short - can anyone provide any information about putting the AR6003
>> into concurrent AP+STA mode? Is this even possible with the in-kernel
>> firmware and driver?
>> >
>> > Nick Stevens
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > ath6kl mailing list
>> > ath6kl@xxxxxxxxxxxxxxxxxxx
>> > http://lists.infradead.org/mailman/listinfo/ath6kl
>>
>>
>>
>> --
>> Attila Sukosd
>> CTO & Co-founder
>> +45 27 14 88 03
>> attila@xxxxxxxxxxx
>> LinkedIn
>> GitHub
>> ________________________________
>>
>> AIRTAME ApS
>> Vestergade 20C, 2nd Floor
>> 1456 Copenhagen
>> Denmark
>> airtame.com
>> Facebook
>> LinkedIn
>> Twitter



-- 
Attila Sukosd
CTO & Co-founder
+45 27 14 88 03
attila@xxxxxxxxxxx
LinkedIn
GitHub
________________________________

AIRTAME ApS
Vestergade 20C, 2nd Floor
1456 Copenhagen
Denmark
airtame.com
Facebook
LinkedIn
Twitter

_______________________________________________
ath6kl mailing list
ath6kl@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/ath6kl



[Index of Archives]     [Linux Kernel]     [Linux Wireless]     [Linux Bluetooth]     [Linux WPAN]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]

  Powered by Linux