linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: August Hoerandl <ahoerandl@gmx.at>
To: linuxppc-embedded@lists.linuxppc.org
Subject: new uart on MPC8xx
Date: Mon, 25 Jun 2001 10:36:49 +0200	[thread overview]
Message-ID: <01062510364900.00667@linuxhoe> (raw)


I was checking the new uart (got the kernel from
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.4-2001-05-12.tar.bz2 )

I tried to use some pins on port b for handshake and it refuses to compile:
The problem is in uart.c around line 80:

#if (CONFIG_UART_DTR_CONTROL_SCC1 == PORT_B)
#define PORT_DTR1_PAR immap->im_ioport.iop_pbpar

but 8xx_immap.h reads:

typedef struct comm_proc {
        ...
        uint   cp_pbdir;

so port b is a little different from all the other ports ;-)

Has anyone got a patch to correct this ?

Thanks
Gustl

ps: is this list the right place to report such troubles ?

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

             reply	other threads:[~2001-06-25  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25  8:36 August Hoerandl [this message]
2001-06-25  8:54 ` new uart on MPC8xx Wolfgang Denk

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=01062510364900.00667@linuxhoe \
    --to=ahoerandl@gmx.at \
    --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).