From: Adrian Cox <adrian@humboldt.co.uk>
To: okorpil@fh-landshut.de
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MVME2100 patch
Date: Thu, 08 Apr 2004 13:50:30 +0100 [thread overview]
Message-ID: <1081428630.19021.55.camel@newt> (raw)
In-Reply-To: <Pine.LNX.4.58.0404071641050.16422@ppcproject1>
On Wed, 2004-04-07 at 15:51, okorpil@fh-landshut.de wrote:
> Was wrong about IRQ stuff last time - I'm off course operation in serial
> IRQ mode here, because there is a serial IRQ source (8259(attached to the
> IRQO of the OpenPIC, giving me the 12 (16 in total, 4 unused) IRQs I care
> about. But no cascade within that 16 lines, so no cascade hook.
I'm not sure what you mean here. The presence of an i8259 cascade is
independent of the EPIC serial mode. EPIC serial mode is a hardware
design decision, which is required if you need to feed more than 5
sources into the EPIC. An i8259 is just another source, and as far as I
can tell, there is no i8259 on the MVME2100.
The RTC is probably connected to IRQ 8 because you set CONFIG_RTC=y. Use
CONFIG_GEN_RTC instead.
- Adrian Cox
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-08 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 14:51 MVME2100 patch okorpil
2004-04-08 12:50 ` Adrian Cox [this message]
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=1081428630.19021.55.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=okorpil@fh-landshut.de \
/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).