mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH v2] console: flush consoles on newline when debugging
Date: Wed, 13 Mar 2024 12:46:22 +0100	[thread overview]
Message-ID: <3a09a33d-4907-42f6-acc5-f87281213eae@pengutronix.de> (raw)
In-Reply-To: <171032992292.2298318.3624692935716774908.b4-ty@pengutronix.de>

Hello Sascha,

On 13.03.24 12:38, Sascha Hauer wrote:
> 
> On Wed, 13 Mar 2024 11:00:48 +0100, Ahmad Fatoum wrote:
>> For debugging hangs, CONFIG_DEBUG_PROBES and CONFIG_DEBUG_INITCALLS are
>> useful tools to pinpoint where the issue is. FOr issues that lock up the
>> SoC, their output can be misleading if we have bigger UART FIFO and not
>> all output has managed to make it out.
>>
>> Add a new DEBUG_FLUSH_LINE_BREAK to make debugging this easier.

Thanks. I just noticed, I missed updating the message here
(CONSOLE_FLUSH_LINE_BREAK). Could you fix it?

Cheers,
Ahmad


>> The option is unnecessary outside of debugging, so for now we don't add
>> a prompt by default and select it as needed.
>>
>> [...]
> 
> Applied, thanks!
> 
> [1/1] console: flush consoles on newline when debugging
>       https://git.pengutronix.de/cgit/barebox/commit/?id=50cbfd91b573 (link may not be stable)
> 
> Best regards,

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




      reply	other threads:[~2024-03-13 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 10:00 Ahmad Fatoum
2024-03-13 11:38 ` Sascha Hauer
2024-03-13 11:46   ` Ahmad Fatoum [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=3a09a33d-4907-42f6-acc5-f87281213eae@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox