linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Dominik Baranski <jdb2@ece.msstate.edu>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 2nd serial port on an Embedded Planet EP862-1.1 board
Date: Mon, 22 Sep 2003 17:30:55 -0500	[thread overview]
Message-ID: <3F6F781F.6060706@ece.msstate.edu> (raw)
In-Reply-To: <1062713293.31909.14.camel@trouble>


Hi all,
I'm attempting to get the second serial port working on an EP862-1.1
board. I see that I need to be concerned with BCSR4 and that the port
can be controlled via SCC1, 2, or 3.
I assume that 'struct serial_state rs_table[]' in arch/ppc/8xx_io/uart.c
needs to be set up correctly, although I'm not quite sure how to go
about doing this.
I know that this board has more BCSR registers than the CLLF, but
everything seems to be correct in arch/ppc/platforms/rpxclassic.h. I
don't have to mess with any memory mappings in arch/ppc/mm/init.c, do I?

Any pointers in the right direction?

Thanks!

-Jan Baranski


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

           reply	other threads:[~2003-09-22 22:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1062713293.31909.14.camel@trouble>]

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=3F6F781F.6060706@ece.msstate.edu \
    --to=jdb2@ece.msstate.edu \
    --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).