Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Brue <ryanbrue.dev@gmail.com>
To: sean.wang@mediatek.com, chris.lu@mediatek.com
Cc: mark-yw.chen@mediatek.com, ryder.lee@mediatek.com,
	shayne.chen@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Request for MT6630 firmware for linux-firmware (btmtksdio, mt76)
Date: Tue, 10 Nov 2026 20:36:39 -0600	[thread overview]
Message-ID: <ec8e2f41-ffea-4153-a5a0-ea2199bebd74@gmail.com> (raw)

Hi Sean and Chris,

I have mainline drivers for the MT6630 Wi-Fi/Bluetooth combo chip on 
SDIO, written for a 2017 Amazon Fire HD 10 (MT7173). I have MT6630 
support in btmtksdio, and a new mt76 driver, mt6630s. On the tablet, I 
have Wi-Fi working on 5 GHz with VHT80, and Bluetooth plays A2DP audio 
to headphones. I plan on posting them to linux-bluetooth and linux-wireless.

The drivers need three files, none of which are in linux-firmware:

   mediatek/mt6630/mt6630_patch_e3_0_hdr.bin, 47068 bytes
   sha256 c9790255a4e0dacdd6ef9191647fe96c96c30e10f158e9bf15e9ec08a6bab022

   mediatek/mt6630/mt6630_patch_e3_1_hdr.bin, 65524 bytes
   sha256 8a4ed4d384bd14bf255cde87adefe5136742575752e571c39cf49ceef221e6ea

   mediatek/mt6630/WIFI_RAM_CODE_MT6630, 237008 bytes
   sha256 c9715c3f09fbd92afa74bf530c8dea34a0558b463799e4feb3795053402c5558


They are from the Fire OS vendor files for the tablet. Both patches 
carry the build time 20180626b001007, and the chip reports hw version 
0x8a12, ROM version 0x8a11. Fire OS also has an older pair, built 
20170622224023a.

I have three questions:

1. Would MediaTek submit these files to linux-firmware under 
LICENCE.mediatek, or sign off on a submission I prepare? linux-firmware 
only takes firmware from the vendor or with its acknowledgement, so I 
wouldn't send them on my own.

2. Are these the right builds for the MT6630 E3, or is there a newer one 
you'd rather ship?

3. Are the names above acceptable? I'd like the drivers and 
linux-firmware to match before I post the drivers, and I can change them 
to whatever you prefer.

Thank you, and best regards,
Ryan Brue


                 reply	other threads:[~2026-11-11  2:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ec8e2f41-ffea-4153-a5a0-ea2199bebd74@gmail.com \
    --to=ryanbrue.dev@gmail.com \
    --cc=chris.lu@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark-yw.chen@mediatek.com \
    --cc=ryder.lee@mediatek.com \
    --cc=sean.wang@mediatek.com \
    --cc=shayne.chen@mediatek.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