From: Reid Sutherland <reid-lkml@thirddimension.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Philipp Matthias Hahn <pmhahn@titan.lahn.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Interrupt issue with 2.4.19 vs 2.4.18.
Date: Mon, 19 Aug 2002 13:00:42 -0400 [thread overview]
Message-ID: <3D61243A.8040304@thirddimension.net> (raw)
In-Reply-To: 1029774904.19375.40.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>>My board has a Intel 440GX chipset. From my understanding these are a
>>bitch to deal with and are littered with bugs. I've also read that by
>
>
> Not bugs. Intel refusal to provide documentation on the IRQ routing for
> them
Ahh just lovely. Any known hack/workaround?
(pci=noacpi doesn't work)
-reid
next prev parent reply other threads:[~2002-08-19 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 19:29 Interrupt issue with 2.4.19 vs 2.4.18 Reid Sutherland
2002-08-19 13:16 ` Reid Sutherland
2002-08-19 15:54 ` Philipp Matthias Hahn
2002-08-19 16:35 ` Alan Cox
2002-08-19 17:00 ` Reid Sutherland [this message]
2002-08-20 19:15 ` Reid Sutherland
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=3D61243A.8040304@thirddimension.net \
--to=reid-lkml@thirddimension.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pmhahn@titan.lahn.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