From: okorpil@fh-landshut.de
To: linuxppc-embedded@lists.linuxppc.org
Subject: MVME2100 patch
Date: Wed, 7 Apr 2004 16:51:19 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0404071641050.16422@ppcproject1> (raw)
Hello.
Before I'm going into a prolonged Easter weekend, I've updated my patch
for the MVME2100.
Straightened out the interrupt configuration of the EPIC according to tips
from Tom Rini, commented a bit of stuff, cleaned up the patch itself, and
tested it. Boots up, works fine.
Tests for sanity of PCI/PMC cards and the VME-Bus stuff are planned for
the next weeks.
Get the patches at:
http://www.fh-landshut.de/~okorpil/mvme2100-linux-2.4.25.patch.bz2
http://www.fh-landshut.de/~okorpil/mvme2100-linux-2.4.25.patch.gz
My interrupt config without addon cards looks like this:
# cat /proc/interrupts
CPU0
2: 0 i8259 Edge 82c59 secondary cascade
8: 0 i8259 Edge rtc
16: 1828 OpenPIC Level eth0
25: 311 OpenPIC Level serial
BAD: 1
I still wonder why it maps RTC to IRQ8, because it should be at 27 in my
current config - 2nd line after serial.
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 hope I got it right now.
Have a happy Easter, y'all.
Oliver Korpilla
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-04-07 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 14:51 okorpil [this message]
2004-04-08 12:50 ` MVME2100 patch Adrian Cox
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=Pine.LNX.4.58.0404071641050.16422@ppcproject1 \
--to=okorpil@fh-landshut.de \
--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