From: Mikael Pettersson <mikpe@csd.uu.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Damian Kolkowski <deimos@deimos.one.pl>,
Danny ter Haar <dth@ncc1701.cistron.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test4(-mmX) via-rhine ethernet onboard C3 mini-itx doesn't work
Date: Wed, 3 Sep 2003 17:19:30 +0200 [thread overview]
Message-ID: <16214.1666.850426.454153@gargle.gargle.HOWL> (raw)
In-Reply-To: <1062598918.19059.54.camel@dhcp23.swansea.linux.org.uk>
Alan Cox writes:
> On Mer, 2003-09-03 at 10:30, Mikael Pettersson wrote:
> > It's impossible to have an APIC bug on a C3 board, because the processor
> > simply doesn't have one!
>
> The chipset does and not writing PCI_INTERRUPT_LINE and other things
> properly can cause problems if its directing interrupts to the chipset
> I/O APIC wrongly not the PIC and thus the CPU
You mean PCI initialisation (and thus ACPI) can break the I/O-APIC
even though the kernel never actually accesses the I/O-APIC per se?
Ok, I see how that could happen.
/Mikael
next prev parent reply other threads:[~2003-09-03 15:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 7:11 Danny ter Haar
2003-09-03 7:40 ` Roger Luethi
2003-09-03 7:49 ` Danny ter Haar
2003-09-03 7:49 ` Damian Kolkowski
2003-09-03 8:02 ` Danny ter Haar
2003-09-03 8:13 ` Damian Kolkowski
2003-09-03 8:13 ` Arjan van de Ven
2003-09-03 8:22 ` Damian Kołkowski
2003-09-03 9:17 ` Roger Luethi
2003-09-03 10:03 ` Danny ter Haar
2003-09-03 9:58 ` Danny ter Haar
2003-09-03 9:30 ` Mikael Pettersson
2003-09-03 9:49 ` Roger Luethi
2003-09-03 10:05 ` Danny ter Haar
2003-09-03 14:21 ` Alan Cox
2003-09-03 15:19 ` Mikael Pettersson [this message]
2003-09-03 15:40 ` Alan Cox
2003-09-03 16:23 ` Matt Heler
2003-09-03 16:55 ` Roger Luethi
[not found] <20030903113737.A3655@pc9391.uni-regensburg.de>
2003-09-03 9:46 ` Christian Guggenberger
2003-09-03 10:50 ` Damian Kołkowski
2003-09-03 14:53 ` Danny ter Haar
2003-09-03 15:48 Christian Guggenberger
2003-09-03 16:37 ` Danny ter Haar
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=16214.1666.850426.454153@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=deimos@deimos.one.pl \
--cc=dth@ncc1701.cistron.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®