From: Dan Malek <dan@netx4.com>
To: Grant Carter <gcarter@eng.uct.ac.za>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: SMC2
Date: Wed, 07 Jun 2000 13:05:27 -0400 [thread overview]
Message-ID: <393E80D7.9918BBE1@embeddededge.com> (raw)
In-Reply-To: 393E4156.E7E8153A@eng.uct.ac.za
Grant Carter wrote:
> When I look at my manuals, I see no reference made to the bits 20 and 21
> in pbpar, pbdir or pbodr. How does setting those bits enable the SMC2
> pins? Those are located in Port A (PA8 and PA9)
>
> I guess my point is why are the Port B registers being modified for SMC2
> pins which are found in Port A?
Oh oh......are you using an 823 or 850? Sorry about this, you will
have to change the code. Someday, I have to finish up a better UART
driver. You are the first person I know that is trying to use this
as a UART. SMC2 is the first thing to disappear when using the parts
for other data communication protocols or interfaces, so custom
software tends to assign these for other purposes. I seldom see anything
but SMC1 used for a UART, so making the driver better hasn't been
high on the list......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-07 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-07 12:34 SMC2 Grant Carter
2000-06-07 17:05 ` Dan Malek [this message]
2000-06-07 20:26 ` SMC2 Wolfgang Denk
2000-06-07 20:40 ` SMC2 Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-06-07 14:19 SMC2 Wohlgemuth, Jason
2000-06-07 14:55 ` SMC2 Grant Carter
2000-06-07 17:09 ` SMC2 Dan Malek
2000-06-07 17:40 SMC2 Brown, David (dbrown03)
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=393E80D7.9918BBE1@embeddededge.com \
--to=dan@netx4.com \
--cc=gcarter@eng.uct.ac.za \
--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).