From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 0/3] Start of MStar/SigmaStar Arm v7 SoC support
Date: Mon, 14 Sep 2020 14:56:48 -0400 [thread overview]
Message-ID: <20200914185648.GT5110@bill-the-cat> (raw)
In-Reply-To: <20200914120441.3274829-1-daniel@0x0f.com>
On Mon, Sep 14, 2020 at 09:04:38PM +0900, Daniel Palmer wrote:
> The initial very basic support for MStar/SigmaStar's Arm v7 SoCs
> should land in Linux 5.9 so I want to start the ball rolling on
> the u-boot side of things.
>
> This series does almost nothing aside from define the header needed
> for the binaries to boot.
>
> In my tree everything is working to the point that booting from
> SPI NOR, ethernet, SD etc work and for one chip it's even possible
> to have a completely u-boot boot flow.
>
> I'm working on cleaning those patches up but I'm not sure how much
> I need for this very first series. So I've put the bare minimum here
> and will pull more parts in based on feedback.
>
> Daniel Palmer (3):
> arm: mstar: Initial MStar/SigmaStar Armv7 SoC support
> arm: mstar: Add option for loading the SPL from the IPL
> arm: mstar: Add boot0 header
>
> MAINTAINERS | 6 +++++
> arch/arm/Kconfig | 9 +++++++
> arch/arm/Makefile | 1 +
> arch/arm/include/asm/arch-mstarv7/boot0.h | 29 ++++++++++++++++++++
> arch/arm/mach-mstar/Kconfig | 32 +++++++++++++++++++++++
> 5 files changed, 77 insertions(+)
> create mode 100644 arch/arm/include/asm/arch-mstarv7/boot0.h
> create mode 100644 arch/arm/mach-mstar/Kconfig
What I see in the code so far is fine. This is a bit too little of a
first series as there's nothing building. I would suggest aiming for a
"boots to hush prompt on serial" for the first series as the goal and
adding follow up series to add in IO. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200914/25946bc0/attachment.sig>
next prev parent reply other threads:[~2020-09-14 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 12:04 [RFC PATCH 0/3] Start of MStar/SigmaStar Arm v7 SoC support Daniel Palmer
2020-09-14 12:04 ` [RFC PATCH 1/3] arm: mstar: Initial MStar/SigmaStar Armv7 " Daniel Palmer
2020-09-14 12:04 ` [RFC PATCH 2/3] arm: mstar: Add option for loading the SPL from the IPL Daniel Palmer
2020-09-14 12:04 ` [RFC PATCH 3/3] arm: mstar: Add boot0 header Daniel Palmer
2020-09-14 18:56 ` Tom Rini [this message]
2020-09-15 10:14 ` [RFC PATCH 0/3] Start of MStar/SigmaStar Arm v7 SoC support Daniel Palmer
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=20200914185648.GT5110@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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