From: Ryan Brue <ryanbrue.dev@gmail.com>
To: YoungJoon Lee <getfeus@gmail.com>
Cc: devnull+getfeus.gmail.com@kernel.org, Xiandong.Wang@mediatek.com,
andrew-ct.chen@mediatek.com, houlong.wei@mediatek.com,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
mchehab@kernel.org, minghsiu.tsai@mediatek.com
Subject: Re: [PATCH RFC v3] media: mediatek: mdp: Keep component suppliers powered while streaming
Date: Fri, 13 Nov 2026 08:28:34 -0600 [thread overview]
Message-ID: <b7d42a96-6827-4251-ace4-1b3a86bb7593@gmail.com> (raw)
In-Reply-To: <CA+m4KrDA9rx9YB4pPMdZ+Qg-GbGyYb2Mnfbb7NdgrwGWduEuYw@mail.gmail.com>
Hi Youngjoon,
On 11/13/26 5:40 AM, YoungJoon Lee wrote:
> Out of curiosity, are you working on mainline Linux support for the
> Fire HD 10? Your mention of the board DTS being under review caught my
> eye. I’d be interested to hear how you’re booting and running Linux on
> it.
I am [1]!
The original boot sequence is something like BROM -> Preloader -> TF-A
-> LK -> Kernel (simplified)
Back in the day there was an old boot exploit you could use to unlock
the bootloader and allow booting other kernels [2]. This let me replace
the vendor Fire OS kernel with an upstream Linux kernel (with
modifications of course).
Almost everything from that is upstreamable from that, EXCEPT the lack
of proper PSCI 1.0. Amazon's TF-A is PSCI 0.2, and a broken version of
it, so it's more like PSCI 0.1 in practice. The upstream kernel expects
PSCI 1.0 or a spin table, and with a spin table my understanding is
you're giving up proper deep sleep.
There's a newer unlock [3] that works at the preloader-level, allowing
us to replace TF-A with upstream TF-A (supporting PSCI 1.1!). I'm also
replacing LK with U-Boot, because LK has some arbitrary restrictions on
kernel size that I had to figure out by trial-and-error annoyingly.
I'm not the only one working on Fire devices for upstream. I'm aware of
Ben Grisdale working on the SoC and DT for an Echo device [4]. More will
likely come in the future. I personally am working on the Amazon Fire TV
Stick (3rd Generation) and I'll be cleaning up more patches for it as I
wrap up the tablet support.
[1]
https://lore.kernel.org/all/20261111-rbrue-suez-upstreaming-amazon-suez-dts-v1-0-77b47cdea702@gmail.com/
[2]
https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/
[3] https://github.com/R0rt1z2/amonet-koboreru
[4]
https://lore.kernel.org/all/20261105-arm64-initial-support-for-mediatek-mt8163-soc-v2-0-e68d7d428f99@protonmail.ch/
Best Regards,
Ryan Brue
next prev parent reply other threads:[~2026-11-13 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:39 [RFC PATCH] media: mediatek: mdp: Keep component suppliers powered while streaming getfeus
2026-11-11 6:41 ` [PATCH RFC v2] " Youngjoon Lee via B4 Relay
2026-11-11 9:43 ` [PATCH RFC v3] " Youngjoon Lee via B4 Relay
2026-11-13 6:46 ` Ryan Brue
2026-11-13 11:40 ` YoungJoon Lee
2026-11-13 14:28 ` Ryan Brue [this message]
2026-11-11 7:57 ` 回复: [RFC PATCH] " Xiandong Wang (王先冬)
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=b7d42a96-6827-4251-ace4-1b3a86bb7593@gmail.com \
--to=ryanbrue.dev@gmail.com \
--cc=Xiandong.Wang@mediatek.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=devnull+getfeus.gmail.com@kernel.org \
--cc=getfeus@gmail.com \
--cc=houlong.wei@mediatek.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=minghsiu.tsai@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