U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 5/5] board: Add new Samsung "stemmy" board based on ST-Ericsson U8500
Date: Thu, 23 Jan 2020 16:58:44 -0500	[thread overview]
Message-ID: <20200123215844.GN26536@bill-the-cat> (raw)
In-Reply-To: <20200104174519.19238-6-stephan@gerhold.net>

On Sat, Jan 04, 2020 at 06:45:19PM +0100, Stephan Gerhold wrote:

> The ST-Ericsson U8500 SoC has been used in mass-production for
> some Android smartphones released around 2012.
> In particular, Samsung has released more than 5 different
> smartphones based on U8500, e.g.
> 
>   - Samsung Galaxy S III mini (GT-I8190) "golden"
>   - Samsung Galaxy S Advance (GT-I9070)  "janice"
>   - Samsung Galaxy Xcover 2 (GT-S7710)   "skomer"
> 
> and a few others.
> 
> Mainline Linux has great support for the Ux500 SoC, so these
> smartphones can also run Linux mainline quite well.
> 
> Unfortunately, the original Samsung bootloader used on these devices
> has limitations that prevent booting Linux mainline directly.
> It keeps the L2 cache enabled, which causes Linux to crash very early,
> shortly after decompressing the kernel.
> 
> Using U-Boot allows to circumvent these limitations. We can let the
> Samsung bootloader chain-load U-Boot and U-Boot locks the L2 cache
> before booting into Linux. U-Boot has several other advantages
> - it supports device-trees directly and we are no longer limited to
> flashing Android boot images through Samsung's proprietary download
> mode.
> 
> The Samsung "stemmy" board covers all Samsung devices based on U8500.
> Add minimal support for "stemmy". For now only UART is supported but
> this will be extended later.
> 
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200123/d9a03e7a/attachment.sig>

  parent reply	other threads:[~2020-01-23 21:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 17:45 [RFC PATCH 0/5] arm: Restore minimal support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-04 17:45 ` [RFC PATCH 1/5] timer: Add driver for Nomadik Multi Timer Unit (MTU) Stephan Gerhold
2020-01-06  1:48   ` Linus Walleij
2020-01-23 21:58   ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 2/5] arm: dts: Import device tree for ST-Ericsson Ux500 Stephan Gerhold
2020-01-06  1:48   ` Linus Walleij
2020-01-23 21:58   ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 3/5] arm: Add support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-06  1:49   ` Linus Walleij
2020-01-23 21:58   ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 4/5] MAINTAINERS: Add ARM U8500 Stephan Gerhold
2020-01-06  1:50   ` Linus Walleij
2020-01-23 21:58   ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 5/5] board: Add new Samsung "stemmy" board based on ST-Ericsson U8500 Stephan Gerhold
2020-01-06  1:50   ` Linus Walleij
2020-01-23 21:58   ` Tom Rini [this message]
2020-01-22 16:47 ` [RFC PATCH 0/5] arm: Restore minimal support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-22 18:03   ` Tom Rini
2020-01-23 17:56     ` Stephan Gerhold

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=20200123215844.GN26536@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