All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: latest u-boot branch for Marvell Armada 88F3720
Date: Wed, 25 Mar 2020 17:44:57 +0100	[thread overview]
Message-ID: <ec4399b8-2b8d-3fa8-fa19-52c2c333e66c@denx.de> (raw)
In-Reply-To: <VI1PR05MB4992F681E4D726F345294B70A6CE0@VI1PR05MB4992.eurprd05.prod.outlook.com>

Hi Moritz,

On 25.03.20 16:05, Moritz Berghof wrote:
> My Name is Moritz and we evaluate the Marvell Armada 88F3720
> on the Marvell ESPRESSObin and the TURRIS MOX.
> 
> Does someone know, where is the actual or latest u-boot branch
> for Marvell Armada 88F3720 placed? At the u-boot master or a
> marvell custodian tree or somewhere else? Does Marvell develop
> u-boot still for their Armada 88F3720 and when yes, where?

Those boards are supported in general in mainline U-Boot. Though I
have to admit, that I didn't test any of those ports recently. I
added Marek Behun to Cc, as he did submit most of the Turris Mox
stuff and has more recent experience than I do.

> Because that https://github.com/MarvellEmbeddedProcessors/u-boot-marvell,
> which is well used on the ESPRESSObin is NOT up-to-date. 4 Years ago,
> last commit.

I just took a quick glance at this repo and there are newer, more
recent branches, e.g. "u-boot-2018.03-armada-18.12". But still, this
is far away from mainline, I agree.

Perhaps someone else (Marek) can comment on the current status of
mainline U-Boot on those boards? Is something missing? If yes, it
would be great to get it ported to mainline.

Thanks,
Stefan

> I'm searching an actual u-boot platform for my Chip.
> 
> 
> I look forward to your reply, thank you very much,
> 
> --
> Moritz Berghof
> Software Engineer
> Tel. +49 30 921028-209<tel:+49%C2%A030%C2%A0921028-204>
> Fax +49 30 921028-020<tel:+49%C2%A030%C2%A0921028-020>
> mberghof at phoenixcontact.com<mailto:mberghof@phoenixcontact.com>
> www.phoenixcontact.com<http://www.phoenixcontact.com/>
> 
> PHOENIX CONTACT Cyber Security GmbH
> Richard-Willst?tter-Stra?e 6<x-apple-data-detectors://1/1>
> D-12489 Berlin<x-apple-data-detectors://1/1>
> Register Court: AG Charlottenburg, HR B 202908
> Gesch?ftsf?hrer/General Manager: Kilian Golm
> 
> 
> .......................................................................................
> PHOENIX CONTACT Cyber Security GmbH
> Richard-Willst?tter-Stra?e 6
> D-12489 Berlin
>   
> Register Court: AG Charlottenburg, HR B 202908
> Gesch?ftsf?hrer/General Manager: Kilian Golm
> 

  reply	other threads:[~2020-03-25 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 15:05 latest u-boot branch for Marvell Armada 88F3720 Moritz Berghof
2020-03-25 16:44 ` Stefan Roese [this message]
2020-03-25 17:48   ` Marek Behun
2020-03-25 17:57     ` Marek Behun
2020-04-02 11:30     ` AW: " Moritz Berghof
2020-04-02 12:18       ` Stefan Roese
2020-04-02 13:52         ` Marek Behun
     [not found] <VI1PR05MB499206310103F9B5AD6713E3A6C70@VI1PR05MB4992.eurprd05.prod.outlook.com>
2020-04-03 18:43 ` Marek Behun
2020-04-06  9:43 AW: AW: " Moritz Berghof
2020-04-14 23:52 ` Marek Behun
2020-04-21 10:25   ` AW: " Moritz Berghof
2020-04-21 11:11     ` Marek Behun
     [not found]       ` <VI1PR05MB4992654399B1405165482C47A6D20@VI1PR05MB4992.eurprd05.prod.outlook.com>
2020-04-22  9:12         ` Marek Behun

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=ec4399b8-2b8d-3fa8-fa19-52c2c333e66c@denx.de \
    --to=sr@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.