From: Mike Rapoport <mike@compulab.co.il>
To: linuxppc-embedded@ozlabs.org
Subject: Using SMC on MPC8272 based board
Date: Wed, 09 Nov 2005 09:28:19 +0200 [thread overview]
Message-ID: <4371A513.6040409@compulab.co.il> (raw)
I have a custom board based on MPC8272 and I don't succeed to enable SMC
serial port. I'm running Linux 2.6.12.3 with CPM serial drivers from
2.6.13.2.
When I configure the kernel to use one or two SCCs, with or without
serial console everything works fine. But if I configure the kernel to
support SMC serial port, I see nothing at the SMC port.
I've noticed that SMC1 pins are configured at port D (as in MPC8260),
but MPC8272 has the SMC1 on the port C. I've changed the pins assignment
to use the port C pins, but it didn't help.
When I enable support for serial console on SCC/SMC port, the system
hangs when the SMC is enabled.
When I don't enable support for serial console on SCC/SMC port, the
system boots OK, but there's nothing on the SMC port.
--
Sincerely yours,
Mike Rapoport
next reply other threads:[~2005-11-09 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 7:28 Mike Rapoport [this message]
2005-11-09 13:12 ` Using SMC on MPC8272 based board Vitaly Bordug
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=4371A513.6040409@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linuxppc-embedded@ozlabs.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).