From: Christian Lamparter <chunkeey@googlemail.com>
To: David Hutchison <dhutchison@bluemesh.net>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [OpenWrt-Devel] How to initialize multiple phy radios
Date: Mon, 25 Apr 2016 21:01:04 +0200 [thread overview]
Message-ID: <112436203.W4fT509tru@debian64> (raw)
In-Reply-To: <CA+i30h9cNRQkMWfCXXgTgv8GVVPny8NkbUUAK6e-roPfRHaNGg@mail.gmail.com>
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 the tables. You could just go ahead and post it, so it
will be picked up.
> 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 everything else the same )
> hw.h: added definitions for QCA9887
>
> I found "https://github.com/kvalo/ath10k-firmware/blob/master/QCA9887/firmware-5.bin_10.2.3.31.7-1"
> on your github and replaced
> /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin on my board.
> hotplug.d then loaded QCA9887 firmware on next boot.
>
> Of course my approach was very much a hack. If there is anything I can
> contribute to creating a patch for ath10k, please let me know. I would
> love to help!
>
> dmesg
> [ 18.920000] ath10k_pci 0000:00:00.0: pci irq legacy interrupts 0
> irq_mode 0 reset_mode 0
> [ 19.030000] rev_id 00000000 QCA9887
> [ 19.030000] dev_id 00000050 QCA9887
> [ 20.460000] ath10k_pci 0000:00:00.0: qca988x hw2.0 (0x4100016d,
> 0x004000ff sub 0000:0000) fw 10.2.3.31.7-1 fwapi 5 bdapi 1 htt-ver 2.1
> wmi-op 5 htt-op 2 cal file max-sta 1p
> [ 20.480000] ath10k_pci 0000:00:00.0: debug 1 debugfs 1 tracing 0
> dfs 0 testmode 1
>
...
Does the device work? Can you scan for networks, connect to networks
and create networks? That would be good to know.
Regards,
Christian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-25 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+i30h-5GCJ0h9REAJE8TCdxNQDe8Sa=Fs=gbxpHEW3fOY-hMw@mail.gmail.com>
[not found] ` <CA+i30h--nmpjeNK4S02a9o9qrQ-b3QR77WcRorxC5-Dame5hBw@mail.gmail.com>
[not found] ` <CA+i30h-Y_rB0kZfgWifk14Zw1CCkGZH5x5zf8+OH-GTwswXh3w@mail.gmail.com>
2016-04-24 10:48 ` [OpenWrt-Devel] How to initialize multiple phy radios Christian Lamparter
2016-04-25 15:21 ` Valo, Kalle
2016-04-25 16:53 ` David Hutchison
2016-04-25 19:01 ` Christian Lamparter [this message]
2016-04-25 22:14 ` David Hutchison
2016-04-26 7:20 ` Valo, Kalle
2016-04-26 12:21 ` Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=112436203.W4fT509tru@debian64 \
--to=chunkeey@googlemail.com \
--cc=ath10k@lists.infradead.org \
--cc=dhutchison@bluemesh.net \
--cc=kvalo@qca.qualcomm.com \
--cc=openwrt-devel@lists.openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.