From: Dan Malek <dan@embeddededge.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "Björn Östby" <Bjorn.Ostby@combitech.se>, linuxppc-embedded@ozlabs.org
Subject: Re: SCCx UART status on 8xx
Date: Mon, 20 Feb 2006 15:43:51 -0500 [thread overview]
Message-ID: <80a18d524ef11e64f291f6b0d4f877f8@embeddededge.com> (raw)
In-Reply-To: <20060220201504.C5289353C11@atlas.denx.de>
On Feb 20, 2006, at 3:15 PM, Wolfgang Denk wrote:
> All UARTS (up to 2 x SMC + 4 x SCC, depending on CPU model) can be
> used with our tree, including hardware handshake.
Except that you have to be careful about BRG allocation. At most,
the 8xx will have 4 BRGs, some only have 2. There have been various
implementations to work with this, some forced the BRGs to be
multiply mapped (where more than one UART had to run at the same rate)
while others silently returned errors and the UARTs were non-functional
although appeared for use.
Thanks.
-- Dan
next prev parent reply other threads:[~2006-02-20 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 13:37 SCCx UART status on 8xx Björn Östby
2006-02-20 14:18 ` Aristeu Sergio Rozanski Filho
2006-03-11 22:17 ` Marcelo Tosatti
2006-02-20 20:15 ` Wolfgang Denk
2006-02-20 20:43 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-21 11:01 Björn Östby
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=80a18d524ef11e64f291f6b0d4f877f8@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Bjorn.Ostby@combitech.se \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).