From: "Gadiyar, Anand" <gadiyar@ti.com>
To: Nishanth Menon <menon.nishanth@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: [PATCH 2/3] omap3: 3430sdp: add choice of UARTs for console
Date: Mon, 5 Apr 2010 17:16:22 +0530 [thread overview]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB0322418528@dbde02.ent.ti.com> (raw)
In-Reply-To: <4BB9BFB2.9010807@gmail.com>
Nishanth Menon wrote:
> On 04/05/2010 04:07 AM, Anand Gadiyar wrote:
> > The OMAP3 SDPs have both UART1 and UART3 available.
> > Historically, UART1 has been used for the console.
> >
> > Add a config option to select between these UARTs
> > (along the lines of what has been done for OMAP3 EVM)
> >
> I dont see a major reason for supporting UART1 other than historical
> reasons, as UART3 seems capable of doing more than just debug terminal
> alone (includes download aswell).. overall I dont see an issue, but
> might be better to choose the terminal in a generic manner accross
> platforms - as in, CONFIG_OMAP_SERIAL_UART1,2,3... for all platforms -
> just my 2 cents.
Yup, sounds good. Let me see if I can make this generic.
- Anand
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-04-05 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 9:07 Anand Gadiyar
2010-04-05 9:07 ` [PATCH 1/3] omap3: rename defconfigs to align with kernel Anand Gadiyar
2010-04-05 9:07 ` [PATCH 3/3] omap3: 3430sdp: Update defconfig Anand Gadiyar
2010-04-05 10:48 ` Nishanth Menon
2010-04-05 10:41 ` [PATCH 1/3] omap3: rename defconfigs to align with kernel Nishanth Menon
2010-04-05 11:45 ` Gadiyar, Anand
2010-04-05 10:47 ` [PATCH 2/3] omap3: 3430sdp: add choice of UARTs for console Nishanth Menon
2010-04-05 11:46 ` Gadiyar, Anand [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=5A47E75E594F054BAF48C5E4FC4B92AB0322418528@dbde02.ent.ti.com \
--to=gadiyar@ti.com \
--cc=barebox@lists.infradead.org \
--cc=menon.nishanth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox