From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] sunxi: Pine64 fixes
Date: Wed, 7 Sep 2016 12:12:58 -0400 [thread overview]
Message-ID: <20160907161258.GI4990@bill-the-cat> (raw)
In-Reply-To: <0aaf5740-800d-10a4-5e0a-554e84ed41ba@arm.com>
On Wed, Sep 07, 2016 at 04:55:53PM +0100, Andre Przywara wrote:
> Hi,
>
> On 07/09/16 16:48, Hans de Goede wrote:
> > Hi,
> >
> > On 07-09-16 17:18, Andre Przywara wrote:
> >> Hi,
> >>
> >> On 07/09/16 16:13, Hans de Goede wrote:
> >>> Hi,
> >>>
> >>> On 05-09-16 02:32, Andre Przywara wrote:
> >>>> Some patches to fix the Pine64 support:
> >>>> The first two patches revert two patches that actually broke booting
> >>>> Pine64 via the boot0 blob, already in 2016.07.
> >>>> This has been discussed on IRC before, the commit messages contain
> >>>> some details on the reasons for the revert. As the intent of those
> >>>> original fixes was to help the (not yet upstream) SPL support, we don't
> >>>> loose anything as the Pine64 uses the U-Boot proper only at the moment.
> >>>>
> >>>> Patch 3/4 removes the usage of a non-existing config symbol.
> >>>> Patch 4/4 fixes a compiler warning when compiling sunxi's board.c
> >>>> with a 64-bit compiler.
> >>>>
> >>>> Please apply for the 2016.09 release to allow booting Pine64s with
> >>>> a recent U-Boot.
> >>>
> >>> I've send out a pull-req with patches 1, 3 and 4 yesterday and
> >>> this has been merged.
> >>
> >> Thanks a lot! That's very helpful.
> >>
> >> Cheers,
> >> Andre.
> >>
> >> P.S. I have the SPL support with proper sunxi DRAM init mostly working,
> >> I am fighting with some bugs still (FIT loading related), but I am
> >> confident that this will be ready for the upcoming merge window.
> >
> > Cool, so do we then still need some closed firmware bits, or is everything
> > open then ?
>
> Everything is proper FOSS, thanks to Jens, who took the existing U-Boot
> H3 DRAM init bits and ported them to support the A64 as well.
>
> Also we don't need any boot0img anymore, mksunxiboot works as expected.
> Appending the U-Boot proper directly to the SPL image works already, but
> leaves out the ATF and thus SMP :-(
> So I have improved SPL FIT support to load multiple images: load both
> U-Boot and ATF, but jump to ATF, which in turn drops to U-Boot.
> I chose the have the SPL in AArch64 (with a handful of AArch32
> instructions in the beginning), which greatly simplifies the build
> process. The drawback is increased code size, but I think we can cope
> with that.
Nice! Will it all also work with FEL mode? That's how I'm integrating
sunxi boards into my test farm. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160907/0c6d7ff3/attachment.sig>
next prev parent reply other threads:[~2016-09-07 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 0:32 [U-Boot] [PATCH 0/4] sunxi: Pine64 fixes Andre Przywara
2016-09-05 0:32 ` [U-Boot] [PATCH 1/4] Revert "sunxi: Move the SPL stack top to 0x1A000 on Allwinner A64/A80" Andre Przywara
2016-09-05 4:12 ` Siarhei Siamashka
2016-09-05 8:23 ` Andre Przywara
2016-09-08 10:51 ` Siarhei Siamashka
2016-09-08 13:23 ` Andre Przywara
2016-09-05 0:32 ` [U-Boot] [PATCH 2/4] Revert "sunxi: Downclock AHB1 to 100MHz on Allwinner A64" Andre Przywara
2016-09-05 4:48 ` Siarhei Siamashka
2016-09-05 8:32 ` Andre Przywara
2016-09-05 0:32 ` [U-Boot] [PATCH 3/4] sunxi: Kconfig: rename non-existent SUN50I_A64 config symbol Andre Przywara
2016-09-05 0:32 ` [U-Boot] [PATCH 4/4] sunxi: fix 64-bit compiler warning for SPL header parsing Andre Przywara
2016-09-05 5:00 ` Siarhei Siamashka
2016-09-07 15:13 ` [U-Boot] [PATCH 0/4] sunxi: Pine64 fixes Hans de Goede
2016-09-07 15:18 ` Andre Przywara
2016-09-07 15:48 ` Hans de Goede
2016-09-07 15:55 ` Andre Przywara
2016-09-07 16:12 ` Tom Rini [this message]
2016-09-07 16:20 ` Andre Przywara
2016-09-08 8:26 ` Hans de Goede
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=20160907161258.GI4990@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