All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Paweł Dembicki" <paweldembicki@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add ZTE MF286D specific BDFs
Date: Fri, 21 Jan 2022 15:58:02 +0200	[thread overview]
Message-ID: <87lez9b385.fsf@kernel.org> (raw)
In-Reply-To: <CAJN1KkxHQwLWQ=0m6DfGG_c5Ls3QMp7VBkJ4BMbqeQY4V-Lx1Q@mail.gmail.com> ("Paweł Dembicki"'s message of "Tue, 18 Jan 2022 21:16:07 +0100")

Paweł Dembicki <paweldembicki@gmail.com> writes:

> I am preparing OpenWrt support for the ZTE MF286D router. It's based
> on the IPQ4019 processor.
>
> * description of hardware
>   - QCA4019-based board
>   - QCA4019 is used as 2.4 GHz radio
>   - QCA4019 is used as 5 GHz radio
>
> * origin of the board file
>   - Pulled from the stock firmware dump.
>
> * IDs to be used with the board file
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=zte,mf286d
>     md5sum: 489f0157df7d92857a8d915098c2de56
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=zte,mf286d
>     md5sum: e0fd5376d24f0c2c3c49ba2a7fc37376
>
> Board file is attached.

Thanks, added to QCA4019/hw1.0/board-2.bin:

New:
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=zte,mf286d
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=zte,mf286d

Changed:


Deleted:

2 board image(s) added, 0 changed, 0 deleted, 89 in total

https://github.com/kvalo/ath10k-firmware/commit/93591ce918f3d7b1070efcc90e08308b85f22b3e


-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

      reply	other threads:[~2022-01-21 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 20:16 ath10k-firmware: QCA4019 hw1.0: Add ZTE MF286D specific BDFs Paweł Dembicki
2022-01-21 13:58 ` Kalle Valo [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=87lez9b385.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=paweldembicki@gmail.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 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.