From: "Carl Ljungmark" <carl.ljungmark@sysgo.com>
To: linuxppc-embedded@ozlabs.org
Subject: serial line on mpc5200
Date: Mon, 29 Aug 2005 12:52:55 +0200 [thread overview]
Message-ID: <op.sv9m6hio0c7u6q@clj.sysgo.com> (raw)
Hi all!
I have 2.6.12 up and running on my mpc5200, but are experiencing a proble=
m =20
with the
serial line.
PSC1+3 are both registered as uarts during boot
Serial: MPC52xx PSC driver
ttyS0 at MMIO 0xf0002000 (irq =3D 39) is a MPC52xx PSC
ttyS2 at MMIO 0xf0002400 (irq =3D 41) is a MPC52xx PSC
, but I don't get the 2nd line to work.
# cat /proc/tty/driver/mpc52xx_psc_uart
shows
serinfo:1.0 driver revision:
0: uart:MPC52xx PSC mmio:0xF0002000 irq:39 tx:3546 rx:112 =20
RTS|CTS|DTR|DSR|CD
2: uart:MPC52xx PSC mmio:0xF0002400 irq:41 tx:0 rx:0 CTS|DSR|CD
#
(IRQ 41 isn't shown under /proc/interrupts - and no entry under =20
/proc/irq/41, but
the irq 41 count IS increased when writing to the port - as shown under =20
/proc/stat)
under 2.4.31 both serial lines work, so it's not hardware. In 2.4 the =20
serial lines show up as /dev/tts/{0,1}, whereas in 2.6 they show up as =20
/dev/tts/{0,2}.
Does anyone know what the problem might be?
thanks in advance..
/carl
reply other threads:[~2005-08-29 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=op.sv9m6hio0c7u6q@clj.sysgo.com \
--to=carl.ljungmark@sysgo.com \
--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