From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] tegra: Implement board_pre_console_panic() for Seaboard
Date: Mon, 19 Mar 2012 15:18:30 -0600 [thread overview]
Message-ID: <4F67A2A6.8030708@wwwdotorg.org> (raw)
In-Reply-To: <1332188824-5447-5-git-send-email-sjg@chromium.org>
On 03/19/2012 02:27 PM, Simon Glass wrote:
> We enable this feature on all UARTs for Seaboard. This ensures that a
> message is printed if CONFIG_OF_CONTROL is in use and a value device tree
> is not available.
Why not just enabled this on UARTD, since that's what Seaboard uses?
I guess some derivatives do use UARTB too, which makes things quite
painful. Perhaps at least limit this to UARTB + UARTD, and not all the
others?
next prev parent reply other threads:[~2012-03-19 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 20:27 [U-Boot] [PATCH 1/5] Revert "Add board_pre_console_putc to deal with early console output" Simon Glass
2012-03-19 20:27 ` [U-Boot] [PATCH 2/5] Add board_panic_no_console() to deal with early critical errors Simon Glass
2012-03-20 22:26 ` Graeme Russ
2012-03-20 23:22 ` Simon Glass
2012-03-20 23:43 ` Graeme Russ
2012-03-21 0:06 ` Simon Glass
2012-03-21 0:34 ` Stephen Warren
2012-03-21 0:36 ` Simon Glass
2012-03-21 9:02 ` Wolfgang Denk
2012-03-21 16:17 ` Simon Glass
2012-03-21 22:48 ` Wolfgang Denk
2012-03-21 23:04 ` Wolfgang Denk
2012-03-19 20:27 ` [U-Boot] [PATCH 3/5] tegra: Export the UART setup function for use by boards Simon Glass
2012-03-21 9:04 ` Wolfgang Denk
2012-03-19 20:27 ` [U-Boot] [PATCH 4/5] tegra: Provide tegra_pre_console_panic() for early panics Simon Glass
2012-03-19 21:16 ` Stephen Warren
2012-03-19 22:55 ` Simon Glass
2012-03-19 20:27 ` [U-Boot] [PATCH 5/5] tegra: Implement board_pre_console_panic() for Seaboard Simon Glass
2012-03-19 21:18 ` Stephen Warren [this message]
2012-03-19 22:59 ` Simon Glass
2012-03-20 1:22 ` Stephen Warren
2012-03-20 1:31 ` Simon Glass
2012-03-20 1:46 ` Stephen Warren
2012-03-20 1:58 ` Simon Glass
2012-03-21 9:08 ` Wolfgang Denk
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=4F67A2A6.8030708@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.