linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dean Matsen <deanmatsen@earthlink.net>
To: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx SCC's as uart
Date: Thu, 17 Jul 2003 09:19:50 -0700	[thread overview]
Message-ID: <3F16CCA6.30905@earthlink.net> (raw)
In-Reply-To: <75DF04AC5ED4D511A9810090273CB4163F5DEB@rokonet-e.rokonet.co.il>


If anyone has interest, I have a patch against the 2.4.22-pre4/5
kernels that allows SCC1 to be a console (but still without
handshaking, in accord with this discussion thread) on 8xx builds.

We have a device where SCC1 is the only port connected to a DB-9, so
I had to do it.  The patch is modeled after the 8260 SCC console
stuff.

Problem is, the boot/8xx_io/boot/simple/m8xx_tty.c is kind of
messy because of an intertwined if/else and #ifdef/#else (we call
it a "conditional curly brace" at our office), so I do not know that
my patch is appropriate for all platforms.  It works on the one
device of ours that needs it...

Dean

Eli Brin wrote:

>Dear Wolfgang,
>
>Thanks, but I prefer to try it on the FADS.  I don't want anything "bad" to
>happen to the TQM860L.  The FADS is expendable...
>
>Thank you,
>Eli Brin
>
>
>-----Original Message-----
>From: Wolfgang Denk [mailto:wd@denx.de]
>Sent: Thursday, July 17, 2003 4:08 PM
>To: Eli Brin
>Cc: 'Steven Scholz'; 'linuxppc-embedded@lists.linuxppc.org'
>Subject: Re: 8xx SCC's as uart
>
>
>Dear Eli,
>
>in message <75DF04AC5ED4D511A9810090273CB4163F5DE9@rokonet-e.rokonet.co.il>
>you wrote:
>
>
>>When I will get our target, I will be able to test the HW flow control
>>of the 8xx and find a working mode with mgetty.  Our development
>>targets (TQM860L and FADS) don't have an SCC uart port...Perhaps I
>>will try to rewire the FADS that has SCC2 connected to an IRDA port...
>>
>>
>
>You can easily connect a UART port on a free SCC on the TQM860L - all 4 SCCs
>are available on  the  headers,  and  all  required  pins  are available  on
>the  STK8xxL  starter  kit board, too. You just need a RS232 line driver.
>
>
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
>Thought for the day: What if there were no hypothetical situations?
>
>
>
>
>


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

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

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

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=3F16CCA6.30905@earthlink.net \
    --to=deanmatsen@earthlink.net \
    --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).