From: Timur Tabi <timur@freescale.com>
To: Ying Lin <ylin@airvana.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Anyone using QE UART mode?
Date: Tue, 03 Jul 2007 09:59:13 -0500 [thread overview]
Message-ID: <468A6441.105@freescale.com> (raw)
In-Reply-To: <8F798BFDA851B943B3A1B2510E9287850350A90D@airmail.wirelessworld.airvananet.com>
Ying Lin wrote:
>
>> Which chip are you using? There should be separate 16550 compatible
>> UART controller on MPC8360. The driver is already there and working
>> pretty well.
>
> We are using MPC8323E. We have 2 working serial ports from the DUART
> controller, but we need more than 2.
>
> We have about 4 weeks to make them working, any suggestion where to
> start? We plan to start with CW QE Utility generated codes.
Have you tried using a PCI UART card?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-07-03 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 2:49 Anyone using QE UART mode? Ying Lin
2007-07-02 15:40 ` Timur Tabi
2007-07-02 16:01 ` Ying Lin
2007-07-03 8:32 ` Li Yang-r58472
2007-07-03 13:15 ` Ying Lin
2007-07-03 14:59 ` Timur Tabi [this message]
2007-07-03 15:11 ` Ying Lin
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=468A6441.105@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ylin@airvana.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;
as well as URLs for NNTP newsgroup(s).