From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: spider-cpu: Switch from SCIF3 to HSCIF0
Date: Wed, 9 Nov 2022 21:44:52 +0100 [thread overview]
Message-ID: <CAMuHMdU7foCN873wrwUVgCyuoN6Y52Ds-ENXUSoEH0wKpD_qBQ@mail.gmail.com> (raw)
In-Reply-To: <YqmoWYARVsXos3me@shikoro>
Hi Wolfram,
On Wed, Jun 15, 2022 at 11:37 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> > I.e. the U-Boot on the Spider in Magnus' lab has "baudrate=115200"
> > in its environment, while I can read the output from ICUMXA Loader
> > to U-Boot, and Linux just fine.
>
> Earlier U-Boot may have no HSCIF support. Recent ones have and the
> installer suggests to set baudrate to highspeed. ICUMXA loaders never
> worked for me in 115200.
>
> I can keep my patch local if you prefer 115200.
As all active white-hawk users are now suffering from this,
I will queue your patch in renesas-devel for v6.2.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-11-09 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 13:10 [PATCH 1/2] arm64: dts: renesas: r8a779f0: Add HSCIF 0+1 nodes Wolfram Sang
2022-06-13 13:10 ` [PATCH 2/2] arm64: dts: renesas: spider-cpu: Switch from SCIF3 to HSCIF0 Wolfram Sang
2022-06-15 9:06 ` Geert Uytterhoeven
2022-06-15 9:37 ` Wolfram Sang
2022-11-09 20:44 ` Geert Uytterhoeven [this message]
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=CAMuHMdU7foCN873wrwUVgCyuoN6Y52Ds-ENXUSoEH0wKpD_qBQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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;
as well as URLs for NNTP newsgroup(s).