All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mohammed, Afzal" <afzal@ti.com>
To: "linux-arm-kernel-bounces@lists.infradead.org"
	<linux-arm-kernel-bounces@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: "Nori, Sekhar" <nsekhar@ti.com>
Subject: Early prints on different UART's for same machine type
Date: Tue, 9 Aug 2011 11:26:17 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024DF9E2C1@dbde02.ent.ti.com> (raw)
In-Reply-To: <mailman.7147.1312868034.20023.linux-arm-kernel@lists.infradead.org>

Hi,

This is regarding board with multiple variations using an upcoming SoC from TI.
Variation of the board is detected by reading EEPROM using I2C after
init_machine gets invoked. In one of the variation UART# used is different.
Because of this decompressor logs (and early prints) can't be captured for the
board variant using this different UART#. Our solution for this problem is to
use different mach-id for the board using different UART#. But this solution
seems to be overkill as only to capture decompressor logs, we have to use
a new machine id.

As I2C will not work at the decompressor stage, I2C can't be used to detect
the board type.

As far as I know, ATAG is not parsed in decompressor stage and so ATAG cannot
be used to determine board variant or UART#. Otherwise we will have to add
capability in decompressor to parse ATAG, detect console to be used, and
modify uncompress.h to select proper console for capturing decompressor logs.
This seems a bad solution.

Our bootloader has the capability to detect the board variant.

So the best solution for us so far seems to add a new machine id, if any
better solutions are possible, please let us know.

Regards
Afzal

       reply	other threads:[~2011-08-09  5:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7147.1312868034.20023.linux-arm-kernel@lists.infradead.org>
2011-08-09  5:56 ` Mohammed, Afzal [this message]
2011-08-10  6:37   ` Early prints on different UART's for same machine type Paul Walmsley

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=B85A65D85D7EB246BE421B3FB0FBB593024DF9E2C1@dbde02.ent.ti.com \
    --to=afzal@ti.com \
    --cc=linux-arm-kernel-bounces@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.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 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.