From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] Add board_pre_console_putc to deal with early console output
Date: Fri, 02 Dec 2011 18:09:19 +0100 [thread overview]
Message-ID: <4ED9063F.2010301@denx.de> (raw)
In-Reply-To: <1318981400-23947-1-git-send-email-sjg@chromium.org>
On 19/10/2011 01:43, Simon Glass wrote:
> This patch adds support for console output before the console is inited.
> The main purpose of this is to deal with a very early panic() which would
> otherwise cause a silent hang.
>
> A new board_pre_console_putc() function is added to the board API. If
> provided by the board it will be called in the event of console output
> before the console is ready. This function should turn on all UARTs and
> spray the character out if it possibly can.
>
> The feature is controlled by a new CONFIG_PRE_CONSOLE_PUTC option.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
Hi Simon,
> Changes in v2:
> - Made this feature conditional on CONFIG_PRE_CONSOLE_PANIC
>
> Changes in v3:
> - Rewrite this to be independent of panic()
> - Rename feature to CONFIG_PRE_CONSOLE_PUTC
>
> Changes in v4:
> - Remove weak function, so we get a link error if it is undefined by the board
maybe I have not understood the real goal of this patch. We have already
a CONFIG_PRE_CONSOLE_BUFFER, that tries to store the output when the
console is not avalable - and can be retrieved with a JTAG debugger.
Your patch adds a way to call some serial setup in board code, but it is
not said that works or can work for all / most boards. Compared to the
usage of the circular buffer, it is not so general - am I missing
something ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-12-02 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 22:57 [U-Boot] [PATCH v3] Add board_pre_console_putc to deal with early console output Simon Glass
2011-10-18 23:31 ` Graeme Russ
2011-10-18 23:37 ` Simon Glass
2011-10-18 23:43 ` [U-Boot] [PATCH v4] " Simon Glass
2011-10-18 23:50 ` Graeme Russ
2011-11-25 7:35 ` Simon Glass
2011-11-25 11:53 ` Stefano Babic
2011-11-28 18:56 ` Simon Glass
2011-12-02 17:09 ` Stefano Babic [this message]
2011-12-02 18:16 ` Simon Glass
2011-12-04 18:56 ` Stefano Babic
2011-12-05 3:34 ` Simon Glass
2011-12-05 3:40 ` Graeme Russ
2011-12-05 4:31 ` Simon Glass
2011-12-05 4:35 ` Graeme Russ
2011-12-07 18:20 ` Simon Glass
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=4ED9063F.2010301@denx.de \
--to=sbabic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox