From: "J. Neuschäfer" <j.ne@posteo.net>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: j.ne@posteo.net, u-boot@lists.denx.de,
Tom Rini <trini@konsulko.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Peter Geis <pgwipeout@gmail.com>, Lukasz Majewski <lukma@denx.de>,
Junhui Liu <junhui.liu@pigmoral.tech>
Subject: Re: [PATCH next] board: amediatech: Add X96Q support
Date: Sat, 03 Jan 2026 18:40:47 +0000 [thread overview]
Message-ID: <aVlirgD9gWR9srwp@probook> (raw)
In-Reply-To: <aVlTJPeB5HmvmerJ@google.com>
On Sun, Jan 04, 2026 at 01:34:28AM +0800, Kuan-Wei Chiu wrote:
> Hi J.,
>
> On Wed, Dec 31, 2025 at 08:45:03PM +0100, J. Neuschäfer via B4 Relay wrote:
> > From: "J. Neuschäfer" <j.ne@posteo.net>
> >
> > The X96Q is a set-top box with an H313 SoC, AXP305 PMIC, 1 or 2 GiB RAM,
> > 8 or 16 GiB eMMC flash, 2x USB A, Micro-SD, HDMI, Ethernet, audio/video
> > output, and infrared input.
> >
> > https://x96mini.com/products/x96q-tv-box-android-10-set-top-box
> >
> > This commit adds a defconfig and some documentation. The devicetree is
> > already in dts/upstream.
> >
> > The CONFIG_DRAM_SUNXI_* settings are chosen such that the register
> > values in the DRAM PHY's MMIO space are as close as possible to those
> > observed when booting with the preinstalled vendor U-Boot.
> >
> > ---
>
> Please remove the --- separator above the Signed-off-by tag. git am
> treats everything after the first --- as comments, which will cause
> your sign-off to be stripped from the final commit message.
Yes - I forgot to add the S-o-b manually, and b4 added it under the line
automatically. I will stick to the proper format in v2.
Thanks
next prev parent reply other threads:[~2026-01-03 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 19:45 [PATCH next] board: amediatech: Add X96Q support J. Neuschäfer via B4 Relay
2026-01-02 15:08 ` Tom Rini
2026-01-03 17:17 ` J. Neuschäfer
2026-01-03 17:34 ` Kuan-Wei Chiu
2026-01-03 18:40 ` J. Neuschäfer [this message]
2026-01-03 17:39 ` Kuan-Wei Chiu
2026-01-03 18:46 ` J. Neuschäfer
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=aVlirgD9gWR9srwp@probook \
--to=j.ne@posteo.net \
--cc=clamor95@gmail.com \
--cc=junhui.liu@pigmoral.tech \
--cc=lukma@denx.de \
--cc=pgwipeout@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=visitorckw@gmail.com \
--cc=ycliang@andestech.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