linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Eli Brin <elib@rokonet.co.il>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx SCC's as uart
Date: Thu, 17 Jul 2003 13:16:11 +0200	[thread overview]
Message-ID: <3F16857B.7010706@imc-berlin.de> (raw)
In-Reply-To: <75DF04AC5ED4D511A9810090273CB4163F5DE5@rokonet-e.rokonet.co.il>


Eli Brin wrote:
> Hello,
>
> I have noticed, in kernel 2.4.20, that SCC1 and SCC4 cannot be configured as
> uarts.
>
> Also, the configuration for RTS,CTS,DCD and DTR are missing.
>
> Comparing 8xx_io/uart.c file to the 2.4.4 version of uart.c shows that all
> the code to support the above has been removed, although both show driver
> 0.3.
>
> Our target will use all SCC's as uarts with hardware handshake. So I will
> need to put this back into uart.c and the config.in files.
>
> Is there a reason for this feature (SCC1 and SCC4 as uarts are part of the
> 8xx ability) being removed ?

They haven't been removed! This feature just never made it into the
official BitKeeper tree.

Have a look at linuxppc_2_4_devel in the DENX CVS. Especialy between
the labels LABEL_2003_03_11_2045 and LABEL_2003_03_11_2055!

BTW: Make sure you understood the "hardware handshake" done by the
MPC8xx! MPC8xx CTS/RTS have a different meaning than you might expect
when dealing with real UARTS! Basicly the only support flow control in
one direction! So a device can throttle the MPC. But the MPC can _not_
stop the device from sending more!

Hope this helps.

Steven


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-07-17 11:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 11:28 8xx SCC's as uart Eli Brin
2003-07-17 11:16 ` Steven Scholz [this message]
2003-07-18 16:27 ` Dan Malek
     [not found] <75DF04AC5ED4D511A9810090273CB4163F5DE7@rokonet-e.rokonet.co.il>
2003-07-17 12:50 ` Steven Scholz
  -- strict thread matches above, loose matches on Subject: below --
2003-07-17 14:01 Eli Brin
2003-07-17 13:24 ` Steven Scholz
2003-07-17 14:51 Eli Brin
     [not found] <75DF04AC5ED4D511A9810090273CB4163F5DEB@rokonet-e.rokonet.co.il>
2003-07-17 16:19 ` Dean Matsen
2003-07-20  8:52 Eli Brin

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=3F16857B.7010706@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=elib@rokonet.co.il \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).