From: Greg Allen <gallen@arlut.utexas.edu>
To: "Chuck Partridge" <Chuck_Partridge@amx.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC8245 Internal Duart and Linux
Date: Wed, 10 Apr 2002 17:05:30 -0500 [thread overview]
Message-ID: <p05101505b8da65e8b244@[10.8.16.89]> (raw)
In-Reply-To: <scb46c71.006@mx.amx.com>
>{ 0, BASE_BAUD_8245_DUART, AMX2275_SERIAL_2, 9, STD_COM_FLAGS, /* ttyS2 */ \
> iomem_base: (u8 *)AMX2275_SERIAL_2, \
> io_type: SERIAL_IO_MEM }, \
>{ 0, BASE_BAUD_8245_DUART, AMX2275_SERIAL_3, 9, STD_COM_FLAGS, /* ttyS3 */ \
> iomem_base: (u8 *)AMX2275_SERIAL_3, \
> io_type: SERIAL_IO_MEM },
This may or may not be the problem, but your IRQs are faulty.
The internal 8245 IRQs are 137 and 138.
You need to call openpic_set_sources() before openpic_init() to get
these initialized.
My utx8245_init_IRQ() contains:
openpic_set_sources(0, 32, NULL); /* up to serial interrupt 15 */
openpic_set_sources(129, 3, NULL); /* MPC8245 I2C, DMA0, DMA1 */
openpic_set_sources(134, 1, NULL); /* MPC8245 Message Unit */
openpic_set_sources(137, 2, NULL); /* MPC8245 DUART */
openpic_init(1, 0, 0, -1);
L8r,
-Greg
--
Gregory E. Allen, MSEE Engineering Scientist
Applied Research Laboratories:
The University of Texas at Austin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-04-10 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <scb46c71.006@mx.amx.com>
2002-04-10 22:05 ` Greg Allen [this message]
[not found] <scb46c71.008@mx.amx.com>
2002-04-10 23:24 ` MPC8245 Internal Duart and Linux Jim Thompson
2002-04-10 22:14 Chuck Partridge
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 21:46 Chuck Partridge
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='p05101505b8da65e8b244@[10.8.16.89]' \
--to=gallen@arlut.utexas.edu \
--cc=Chuck_Partridge@amx.com \
--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).