From: "Landau, Bracha" <BLandau@nds.com>
To: "Vitaly Bordug" <vbordug@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: using SCC4 on MPC8272ADS
Date: Wed, 21 Sep 2005 14:33:39 +0300 [thread overview]
Message-ID: <02AA386EB831044F8537A696BA785C78076299@ILEX5.IL.NDS.COM> (raw)
I reconfigured the kernel so that only SCC1 and SCC4 are supported. The s=
ame thing happens as before.
Another bit of info is that if I run with console=3DttyCPM1 as a kernel c=
ommand line parameter, so that u-boot outputs to one port and the kernel =
outputs to the other, if I type "ls > /dev/ttyCPM0" the system hangs.
-----Original Message-----
From: Vitaly Bordug [mailto:vbordug@ru.mvista.com]
Sent: Wednesday, September 21, 2005 1:56 PM
To: Landau, Bracha
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: using SCC4 on MPC8272ADS
Landau, Bracha wrote:
> I am using the MPC8272ADS with kernel 2.6.10. The kernel is configured =
to support 4 CPM SCCs, of which 1 and 4 are connected on the board.
> I created device files as follows:
>=20
> mknod /dev/ttyCPM0 c 204 46
> mknod /dev/ttyCPM1 c 204 47
> mknod /dev/ttyCPM2 c 204 48
> mknod /dev/ttyCPM3 c 204 49
>=20
> If I boot the kernel using console=3DttyCPM3 I see that it uses SCC4. B=
ut when I boot with console=3DttyCPM0 and write to the second port using =
a command like "echo hello > /dev/ttyCPM3" I don't see that anything is b=
eing outputted to the second console.
>=20
> What am I doing wrong?
> =20
Funny - you said that SCC 1 and 4 are connected to the board; than why=20=
you are enabling SCC2 and SCC3?
This board does have 2 SCCs assigned for UARTs. No need to configure=20
SCC2 and SCC3 - this is useless and may lead to kernel crash. This board=20=
will use in the correct configuration /dev/ttyCPM0 <SCC1> and=20
/dev/ttyCPM1 <SCC4>.
--=20
Sincerely,
Vitaly
*************************************************************************=
**********
Information contained in this email message is intended only for use of t=
he individual or entity named above. If the reader of this message is not=
the intended recipient, or the employee or agent responsible to deliver =
it to the intended recipient, you are hereby notified that any disseminat=
ion, distribution or copying of this communication is strictly prohibited=
=2E If you have received this communication in error, please immediately =
notify the postmaster@nds.com and destroy the original message.
*************************************************************************=
**********
next reply other threads:[~2005-09-21 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 11:33 Landau, Bracha [this message]
2005-09-21 11:40 ` using SCC4 on MPC8272ADS Vitaly Bordug
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 15:20 Landau, Bracha
2005-09-21 10:21 Landau, Bracha
2005-09-21 10:55 ` 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=02AA386EB831044F8537A696BA785C78076299@ILEX5.IL.NDS.COM \
--to=blandau@nds.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.com \
/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