ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	Tim Harvey <tharvey@gateworks.com>,
	Chris Blake <chrisrblake93@gmail.com>,
	Ben Greear <greearb@candelatech.com>,
	"Valo, Kalle" <kvalo@qca.qualcomm.com>
Subject: Re: Please add new board files for WLE1216V5-20 and another Compex NIC.
Date: Thu, 12 Apr 2018 09:27:55 +0200	[thread overview]
Message-ID: <2080980.pDnGlZTBzu@bentobox> (raw)
In-Reply-To: <CAJ+vNU1MSa3iR7dAW6M+TiKutzyYSeT3p4H0J8L_W3mTTEtyzQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2623 bytes --]

On Mittwoch, 11. April 2018 08:18:15 CEST Tim Harvey wrote:
> It's not clear what the process is for getting new board id's
> supported in the board.bin files.

The reaction of QCA when asking for new IDs was mostly "please go away, we 
will not talk to you about it". But with the help of Kalle Valo, a new 
mechanism called "qcom,ath10k-calibration-variant" was added (for embedded 
boards which include QCA 11ac wave2 radios). There are a couple of mails 
about it on this list - a general overview about BDFs, variant strings and 
why we need them can be found at 
http://lists.infradead.org/pipermail/ath10k/2018-March/011066.html.

But it looks like you really got the IDs 30+31 (maybe because you are selling 
the, as separate PCIe modules?). Then I would guess that you can still use the 
same process as we use for the accesspoint specific BDFs (just without the 
variant= part).

The description of the general upstreaming process can be found at 
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles - but it 
seems like Kalle Valo doesn't have much time for it at the moment for it (or
there might be other problems which we don't see from our perspective - for 
example legal departments).

Maybe you or Ben Greear can enhance the submission for the BDFs to better 
answer the questions from the "Submitting board files" guide. 


Examples for such submission
============================

* OpenMesh A42

  - applied
  - http://lists.infradead.org/pipermail/ath10k/2017-November/010470.html
  - http://lists.infradead.org/pipermail/ath10k/2017-December/010543.html

* Asus RT-AC58U

  - not yet accepted
  - submitted before the guide was published
  - http://lists.infradead.org/pipermail/ath10k/2017-March/009454.html

* Netgear EX6100v2/EX6150v2

  - not yet accepted
  - http://lists.infradead.org/pipermail/ath10k/2018-February/010845.html

* 8devices Jalapeno

  - not yet accepted
  - http://lists.infradead.org/pipermail/ath10k/2018-March/010916.html

* GL.iNet GL-B1300

  - not yet accepted
  - http://lists.infradead.org/pipermail/ath10k/2018-March/011058.html

* OpenMesh A62

  - not yet accepted
  - http://lists.infradead.org/pipermail/ath10k/2018-March/011081.html



Still waiting for send BDFs to upstream
=======================================

* Meraki MR33

  - Chris Blake?
  - https://github.com/openwrt/openwrt/blob/master/package/firmware/ipq-wifi/board-meraki_mr33.bin

* Fritzbox 4040

  - Christian Lamparter?
  - https://github.com/openwrt/openwrt/blob/master/package/firmware/ipq-wifi/board-avm_fritzbox-4040.bin

* maybe more which I missed


Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

  reply	other threads:[~2018-04-12  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 21:59 Please add new board files for WLE1216V5-20 and another Compex NIC Ben Greear
2018-04-11 15:18 ` Tim Harvey
2018-04-12  7:27   ` Sven Eckelmann [this message]
2018-04-12 16:31     ` Ben Greear
2018-04-13 10:53   ` Kalle Valo
2018-04-18 16:42 ` Kalle Valo
2018-04-18 16:52   ` Ben Greear
2018-04-19 10:01 ` Kalle Valo
2018-04-19 10:10   ` Kalle Valo
2018-04-19 17:33     ` Ben Greear

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=2080980.pDnGlZTBzu@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=chrisrblake93@gmail.com \
    --cc=chunkeey@googlemail.com \
    --cc=greearb@candelatech.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=tharvey@gateworks.com \
    /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;
as well as URLs for NNTP newsgroup(s).