From: "Chuck Partridge" <Chuck_Partridge@amx.com>
To: <gallen@arlut.utexas.edu>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC8245 Internal Duart and Linux
Date: Wed, 10 Apr 2002 17:14:08 -0500 [thread overview]
Message-ID: <scb472f8.096@mx.amx.com> (raw)
I'm using the South Bridge's 8259 controllers and putting the 8245 EPIC in pass through mode, so all internal 8245 interrupts are routed out the L_INT pin to one of the ALI's PCI_IRQ pins.
Does this seem like something very wrong?
I originally thought this would be the easiest way to handle this from an IRQ standpoint, but now know that I have never seen anyone else do this.
>>> Greg Allen <gallen@arlut.utexas.edu> 04/10/02 05:05PM >>>
>{ 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 reply other threads:[~2002-04-10 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 22:14 Chuck Partridge [this message]
[not found] <scb46c71.008@mx.amx.com>
2002-04-10 23:24 ` MPC8245 Internal Duart and Linux Jim Thompson
[not found] <scb46c71.006@mx.amx.com>
2002-04-10 22:05 ` Greg Allen
-- 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=scb472f8.096@mx.amx.com \
--to=chuck_partridge@amx.com \
--cc=gallen@arlut.utexas.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.