From: Gary Thomas <gary@mlbassoc.com>
To: Timur Tabi <timur@freescale.com>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: UCC UART
Date: Thu, 24 Jun 2010 18:49:14 -0600 [thread overview]
Message-ID: <4C23FD0A.6010805@mlbassoc.com> (raw)
In-Reply-To: <4C23CC38.9040108@freescale.com>
On 06/24/2010 03:20 PM, Timur Tabi wrote:
> Timur Tabi wrote:
>> I'd say that there are plenty of unknown issues with this driver/hardware.
>> For some reason, QE UART is just unreliable. I've had several people try to
>> use the QE for UART, and almost everyone has problems with it.
>
> I finally got in touch with one of the other development teams, and they
> said that they got QE UART working with the 8569 and the P1021. The
> reference board we make with the 8568 does not have QE pinned to the UART,
> so they didn't try to support that.
What about 8358? I'm really stuck here - Rx seems to work,
but Tx is totally dead...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-06-25 0:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 14:55 UCC UART Gary Thomas
2010-06-22 15:06 ` Tabi Timur-B04825
2010-06-22 15:10 ` Chuck Meade
2010-06-22 15:14 ` Gary Thomas
2010-06-22 15:28 ` Chuck Meade
2010-06-22 15:46 ` Gary Thomas
2010-06-22 15:53 ` Chuck Meade
2010-06-22 17:44 ` Gary Thomas
2010-06-22 18:14 ` Chuck Meade
2010-06-22 18:41 ` Gary Thomas
2010-06-22 19:01 ` Chuck Meade
2010-06-22 21:19 ` Gary Thomas
2010-06-22 21:27 ` Chuck Meade
[not found] ` <4C20D162.2020302@freescale.com>
2010-06-24 21:20 ` Timur Tabi
2010-06-25 0:49 ` Gary Thomas [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=4C23FD0A.6010805@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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.