[U-Boot] [PATCH 2/5] arm: socfpga: fix device trees to work with DM serial

Simon Goldschmidt simon.k.r.goldschmidt at gmail.com
Wed Aug 8 08:17:00 UTC 2018


On Mon, Aug 6, 2018 at 4:41 PM Simon Goldschmidt
<simon.k.r.goldschmidt at gmail.com> wrote:
>
>
>
> Emmanuel Vadot <manu at bidouilliste.com> schrieb am Mo., 6. Aug. 2018, 15:48:
>>
>> On Mon, 6 Aug 2018 15:42:01 +0200
>> Simon Goldschmidt <simon.k.r.goldschmidt at gmail.com> wrote:
>>
>> > Marek Vasut <marex at denx.de> schrieb am Mo., 6. Aug. 2018, 15:19:
>> >
>> > > On 08/05/2018 09:34 PM, Simon Goldschmidt wrote:
>> > > > Device trees need to have the serial console device available
>> > > > before relocation and require a stdout-path in chosen at least
>> > > > for SPL to have a console.
>> > > >
>> > > > Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt at gmail.com>
>> > >
>> > > This should be upstreamed to Linux too ?
>> > >
>> >
>> > Hmm, I'm not sure. Does Linux use the stdout-path too? I always use
>> > bootargs only...
>>
>>  Linux is the standard repo where other project (like FreeBSD) pull the
>> DTS and stdout-path is standard, so it should be upstreamed.
>
>
> Ok then, I can upstream them. How is the workflow, via which repository or list so socfpga device trees get pushed?

Ignore that question.

I had a look at the current socfpga device trees in Linux and only
socrates and vining seem to be missing the stdout-path. I'll send a
patch to add these.
The rest of the device trees, however, is very different to the U-Boot
ones. What's the procedure here, shall we just copy them from Linux or
do we keep ours?

In any case, we do need this patch to get U-Boot and SPL running
correctly on gen5, which is has been broken since v2018.07.

Tanks,
Simon


More information about the U-Boot mailing list