public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: atags: add support for Marvell's u-boot
Date: Tue, 4 Jun 2013 06:50:13 -0400	[thread overview]
Message-ID: <20130604105013.GY3803@titan.lakedaemon.net> (raw)
In-Reply-To: <51ADA9F3.9000703@gmail.com>

On Tue, Jun 04, 2013 at 10:48:51AM +0200, Sebastian Hesselbarth wrote:
> On 06/04/13 10:13, Thomas Petazzoni wrote:
> >On Mon, 3 Jun 2013 15:17:31 -0400, Jason Cooper wrote:
> >>>Isn't upstream U-Boot supporting Marvell devices properly these days?
> >>>If so maybe considering a U-Boot upgrade would be the best way forward?
> >>
> >>Yes, both u-boot and barebox are supporting Marvell devices,
> >
> >Sorry Jason, but you're overstating the status of this support:

True.

> >
> >  * Barebox has only *minimal* support for Marvell SoCs, i.e only the
> >    serial console and timers are supported. There is no support for
> >    network, NAND, SPI or anything that even allows to load a kernel and
> >    boot it.
> 
> That remembers me that I wanted to make it boot from DT so we don't
> start adding drivers and add DT later on.
> 
> >  * U-Boot has zero support for Armada 370 and Armada XP, and Sebastian
> >    has tried for several months to push support for Marvell Dove,
> >    without success (lack of review/interest from the U-Boot
> >    maintainers, if I remember correctly).
> 
> True. It took about 2 month for a useful review and then the discussion
> was only about naming it orion-something or mv-something. Recently,
> someone picked up that patches and reposted them.. but don't expect them
> to get in quickly.

Sascha Silbe seems to have picked up the ball, and I could've sworn I
saw Tom Rini picked them up.  It shocked me because I thought he was
bypassing Prafulla, but I can't find the email, now.  My mind must be
playing tricks on me.

> >So as of today, the Marvell-specific U-Boot is the /only/ working
> >solution for Armada 370 and Armada XP based platforms, and it will
> >remain this way at least for several months, until we've pushed enough
> >work into Barebox. And even at that time, as you say, users may not
> >necessarily be willing to upgrade their bootloader.
> 
> Well, there is still the possibility to have board-specific dts files.
> If you are stuck for whatever reason with an old boot loader, append a
> dtb with MAC addresses set for your board. IMHO, adding workarounds for
> every single boot loader just because we don't want anybody to either
> update or manually patch the dts is ridiculous.

Agreed.

thx,

Jason.

  reply	other threads:[~2013-06-04 10:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 16:45 [PATCH] ARM: atags: add support for Marvell's u-boot Thomas Petazzoni
2013-06-03 16:57 ` Jason Cooper
2013-06-03 17:09   ` Thomas Petazzoni
2013-06-03 17:42     ` Jason Cooper
2013-06-03 17:10 ` Russell King - ARM Linux
2013-06-03 17:56   ` Willy Tarreau
2013-06-03 18:14     ` Jason Cooper
2013-06-03 18:26       ` Jason Cooper
2013-06-03 18:30       ` Willy Tarreau
2013-06-03 18:41         ` Jason Cooper
2013-06-03 19:07           ` Nicolas Pitre
2013-06-03 19:17             ` Jason Cooper
2013-06-03 19:46               ` Nicolas Pitre
2013-06-03 21:07               ` Willy Tarreau
2013-06-04  8:13               ` Thomas Petazzoni
2013-06-04  8:48                 ` Sebastian Hesselbarth
2013-06-04 10:50                   ` Jason Cooper [this message]
2013-06-04  8:10             ` Thomas Petazzoni
2013-06-04  8:43               ` Sebastian Hesselbarth
2013-06-03 19:01         ` Nicolas Pitre
2013-06-03 21:04           ` Willy Tarreau
2013-06-04  8:05         ` Thomas Petazzoni

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=20130604105013.GY3803@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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