From: Christian Lamparter <chunkeey@googlemail.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: David Hutchison <dhutchison@bluemesh.net>,
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: Tue, 26 Apr 2016 05:21:01 -0700 (PDT) [thread overview]
Message-ID: <2910322.5mKxx5TJEB@debian64> (raw)
In-Reply-To: <8760v425vl.fsf@kamboji.qca.qualcomm.com>
On Tuesday, April 26, 2016 07:20:32 AM Valo, Kalle wrote:
> Christian Lamparter <chunkeey@googlemail.com> 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 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.
> > [...] Editing...
> > Does the device work? Can you scan for networks, connect to networks
> > and create networks? That would be good to know.
^^^^
> But remember that the basic functionality should somewhat work before we
> add the ids to ath10k. The hardware support doesn't need to be perfect
> but we should not enable something which is brokend and would just waste
> users time.
Don't worry about that, I did include the highlighted sentence in the previous
mail as well (seems like it was lost during editing - readded it).
Anyway, I think David will figure out what's working and what isn't and will
let ath10k-devel know about it.
it.
Regards,
Christian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-04-26 12:21 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
2016-04-25 22:14 ` David Hutchison
2016-04-26 7:20 ` Valo, Kalle
2016-04-26 12:21 ` Christian Lamparter [this message]
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=2910322.5mKxx5TJEB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox