From: Tom Rini <trini@kernel.crashing.org>
To: Leigh Brown <leigh@solinno.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [RFC][PATCH 7/9] Support for old IBM PReP boxes
Date: Thu, 17 Jun 2004 11:55:06 -0700 [thread overview]
Message-ID: <20040617185506.GA811@smtp.west.cox.net> (raw)
In-Reply-To: <1859.80.7.99.14.1086887283.squirrel@www.solinno.co.uk>
On Thu, Jun 10, 2004 at 06:08:03PM +0100, Leigh Brown wrote:
>
> This is to support the old OpenPICs in old E20/E30 machines. They
> seem to be mapped as I/O instead of memory mapped. These also seem
> to have a bug that the spurious interrupt always seems to be reported
> as 255. Changing the OPENPIC_VEC_SPURIOUS to 239 (which maps to
> 255 after adding the offset of 16) seems to make it work. As the
> change seems to make no difference on other machines, it seems better
> to do that than have special code for it. However, I don't really
> understand how this spurious vector stuff works, so....
If we don't change OPENPIC_VEC_SPURIOUS, how do the E20/E30 behave? Do
they blow up badly, or just have some spurious bad interrupts? I've
played with that hunk a bit on a sandpoint and lopec, and didn't see
anything go wrong (lopec didn't get any bad w/ or w/o, sandpoint, always
gets a few bad ones). If it's a non-fatal problem, I'd rather err on
the side of caution, and leave it be, or export openpic_set_spurious, so
you can give it the right setting on E20/E30.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-17 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 17:08 [RFC][PATCH 7/9] Support for old IBM PReP boxes Leigh Brown
2004-06-17 18:55 ` Tom Rini [this message]
2004-06-17 19:14 ` Leigh Brown
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=20040617185506.GA811@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=leigh@solinno.co.uk \
--cc=linuxppc-dev@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).