Hi David,
Can you share you current patch? I am working on the same chips,
QCA9531+9887 and hope to get some progress. I'm glad to know that scan is
working.
--Alfie
On 26 April 2016 at 06:14, David Hutchison wrote:
> Scanning appears to work ( iw dev wlan1 scan ) ,
>
> As soon as I try to use
On Tuesday, April 26, 2016 07:20:32 AM Valo, Kalle wrote:
> Christian Lamparter writes:
> > On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
> >> So with some modifications to pci.c, hw.h and core.c I was able to get
> >> the radio initialized! :)
> >
> > Hey, that's nice! Can you make
Christian Lamparter writes:
> Hello,
>
> On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
>> So with some modifications to pci.c, hw.h and core.c I was able to get
>> the radio initialized! :)
>
> Hey, that's nice! Can you make and post a patch for that?
> I'm sure if it's just a mat
Scanning appears to work ( iw dev wlan1 scan ) ,
As soon as I try to use hostapd to run as an AP I get:
[20475.14] ath10k_pci :00:00.0: firmware crashed! (uuid
b826d45e-e51f-4beb-a489-6b7a4d5c6f76)
[20475.15] ath10k_pci :00:00.0: qca988x hw2.0 (0x4100016d,
0x004000ff sub :
Hello,
On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
> So with some modifications to pci.c, hw.h and core.c I was able to get
> the radio initialized! :)
Hey, that's nice! Can you make and post a patch for that?
I'm sure if it's just a matter of adding the new pci and chip
ids to
Hello,
So with some modifications to pci.c, hw.h and core.c I was able to get
the radio initialized! :)
pci.c: added QCA9887_DEVICE_ID, modified ath10k_pci_id_table and
ath10k_pci_supp_chips
core.c: Duplicated QCA988X entry in ath10k_hw_params_list and passed
0x4100016d as the ID ( left everythin
Christian Lamparter writes:
> On Sunday, April 24, 2016 01:16:11 AM David Hutchison wrote:
>> I spoke too soon:
>> https://pci-ids.ucw.cz/read/PC/168c/0050
>>
>> It is the QCA9887, so it's definitely on the PCIe bus and is being
>> seen.
>
> Does ath10k support the QCA9887? I see no entry for th
On Sunday, April 24, 2016 01:16:11 AM David Hutchison wrote:
> I spoke too soon:
> https://pci-ids.ucw.cz/read/PC/168c/0050
>
> It is the QCA9887, so it's definitely on the PCIe bus and is being seen.
Does ath10k support the QCA9887? I see no entry for this pci-id (168c:0050)
in ath10k's pci table
I spoke too soon:
https://pci-ids.ucw.cz/read/PC/168c/0050
It is the QCA9887, so it's definitely on the PCIe bus and is being seen.
-- Davey
On Sun, Apr 24, 2016 at 1:13 AM, David Hutchison
wrote:
> Thank you for the response Christian!
>
> Here is the PCI noise is in the kernel log from ath79_
Thank you for the response Christian!
Here is the PCI noise is in the kernel log from ath79_register_pci():
[0.51] PCI host bridge to bus :00
[0.51] pci_bus :00: root bus resource [mem 0x1000-0x11ff]
[0.52] pci_bus :00: root bus resource [io 0x]
[
Hello,
On Friday, April 22, 2016 02:03:01 AM David Hutchison wrote:
> I have been working on a board port and have everything working except
> for the 2nd radio. This board has a QCA9531 CPU and 2 WiFi Radios:
> AR9531 and a QCA9887 ( http://routerboard.com/RB952Ui-5ac2nD for more
> details ).
> [
Hello,
I have been working on a board port and have everything working except
for the 2nd radio. This board has a QCA9531 CPU and 2 WiFi Radios:
AR9531 and a QCA9887 ( http://routerboard.com/RB952Ui-5ac2nD for more
details ).
The 2.4GHz radio works great, and I have acquired the correct calibrati
12 matches
Mail list logo
