From: Christer Weinigel <wingel@acolyte.hack.org>
To: Alan Cox <alan@www.linux.org.uk>
Cc: proski@gnu.org (Pavel Roskin),
linux-kernel@vger.kernel.org, dhinds@sonic.net (David Hinds),
mj@ucw.cz (Martin Mares)
Subject: Re: Cyrix IRQ routing is wrong?
Date: 05 Jul 2002 16:49:13 +0200 [thread overview]
Message-ID: <m3wusa44d2.fsf@acolyte.hack.org> (raw)
In-Reply-To: Alan Cox's message of "Fri, 5 Jul 2002 15:12:32 +0100 (BST)"
Alan Cox <alan@www.linux.org.uk> writes:
> > 1) 2.4.17 was using the code I want to restore. Where was your hanging
> > box then?
>
> Hanging. Thats why I fixed it when Nat Semi documentation for the old cyrix
> appeared
So your BIOS probably has a buggy PIRQ table.
>From page 155 of the CS5530 manual found at:
http://www.national.com/ds/CS/CS5530.pdf
Index 5Ch PCI Interrupt Steering Register 1 (R/W) Reset Value = 00h
7:4 INTB# Target Interrupt: Selects target interrupt for INTB#
3:0 INTA# Target Interrupt: Selects target interrupt for INTA#
Index 5Dh PCI Interrupt Steering Register 2 (R/W) Reset Value = 00h
7:4 INTD# Target Interrupt: Selects target interrupt for INTD#
3:0 INTC# Target Interrupt: Selects target interrupt for INTC#
So I have to switch that code around on most GX1 boards that I use or
I'll get a lot of messages about IRQ routing conflicts.
/Christer
--
"Just how much can I get away with and still go to heaven?"
next prev parent reply other threads:[~2002-07-05 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 23:50 Cyrix IRQ routing is wrong? Pavel Roskin
2002-07-03 23:31 ` Alan Cox
2002-07-04 0:02 ` Pavel Roskin
2002-07-05 14:12 ` Alan Cox
2002-07-05 14:49 ` Christer Weinigel [this message]
2002-07-05 20:43 ` Alan Cox
2002-07-05 21:13 ` Pavel Roskin
2002-07-04 0:36 ` Linus Torvalds
2002-07-04 8:48 ` Rob van Nieuwkerk
2002-07-05 15:02 ` Christer Weinigel
2002-07-05 21:29 ` Alan 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=m3wusa44d2.fsf@acolyte.hack.org \
--to=wingel@acolyte.hack.org \
--cc=alan@www.linux.org.uk \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=proski@gnu.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.