mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Tomaž Šolc" <tomaz.solc@klevio.com>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: rpi: refactor debug UART Kconfig settings.
Date: Tue, 5 Mar 2019 10:13:04 +0100	[thread overview]
Message-ID: <890b8bc1-68d2-1b7d-e4b8-071f63d53fd9@klevio.com> (raw)
In-Reply-To: <20190304080442.hjyncl4whxmrz2eu@pengutronix.de>

On 4. 03. 19 09:04, Sascha Hauer wrote:
> So that said, even with a debug UART enabled for Rpi1 we should still
> allow to build for Rpi2/3 although we know it won't work there.
> 
> The reason is you might get failures only when multiple SoCs are
> selected. In that case you only want to enable early debugging support
> (for the SoC you are currently testing on) without changing other things
> in the config which might make your errors disappear.

Thanks for the clarification. I've sent another patch series that 
removes the restriction for board builds and adds the help text.

On the topic of the debug UART, I've also noticed that it's a bit tricky 
to get it running on Raspberry Pi 3. The problem is that the debug UART 
is using PL011 hardware, but the console is now using miniuart.

In addition to enabling it in menuconfig, I have to reverse the commit 
ab76f9d0 (switch to miniuart for stdout in the device tree) and keep 
"dtoverlay=pi3-miniuart-bt" in "config.txt" (instruction for this was 
removed in f1330536).

Best regards
Tomaž

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-03-05  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 11:39 Tomaz Solc
2019-03-01  6:42 ` Rouven Czerwinski
2019-03-01 10:58 ` Roland Hieber
2019-03-04  8:04 ` Sascha Hauer
2019-03-05  9:13   ` Tomaž Šolc [this message]
2019-03-06  9:45     ` Sascha Hauer

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=890b8bc1-68d2-1b7d-e4b8-071f63d53fd9@klevio.com \
    --to=tomaz.solc@klevio.com \
    --cc=barebox@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