From: "Juha Saarinen" <juha@saarinen.org>
To: <mingo@elte.hu>, <linux-kernel@vger.kernel.org>
Cc: <linux-smp@vger.kernel.org>, "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: RE: [patch] ioapic-2.4.5-A1
Date: Wed, 30 May 2001 22:26:16 +1200 [thread overview]
Message-ID: <045001c0e8f2$f5774d20$0a01a8c0@den2> (raw)
In-Reply-To: <Pine.LNX.4.33.0105291306470.3146-200000@localhost.localdomain>
The attachment didn't survive... please try again.
-- Juha
:: -----Original Message-----
:: From: linux-smp-owner@vger.kernel.org
:: [mailto:linux-smp-owner@vger.kernel.org] On Behalf Of Ingo Molnar
:: Sent: Tuesday, 29 May 2001 23:11
:: To: linux-kernel@vger.kernel.org
:: Cc: linux-smp@vger.kernel.org; Alan Cox
:: Subject: [patch] ioapic-2.4.5-A1
::
::
::
:: the attached ioapic-2.4.5-A1 patch includes a number of
:: important IO-APIC
:: related fixes (against 2.4.5-ac3):
::
:: - correctly handle bridged devices that are not listed in
:: the mptable
:: directly. This fixes eg. dual-port eepro100 devices on
:: Compaq boxes
:: with such PCI layout:
::
:: -+-[0d]---0b.0
:: +-[05]-+-02.0
:: | \-0b.0
:: \-[00]-+-02.0
:: +-03.0-[01]--+-04.0 <=== eth0
:: | \-05.0 <=== eth1
:: +-0b.0
:: +-0c.0
:: +-0d.0
:: +-0e.0
:: +-0f.0
:: +-14.0
:: +-14.1
:: +-19.0
:: +-1a.0
:: \-1b.0
::
:: without the patch the eepro100 devices get misdetected as
:: XT-PIC IRQs
:: and their interrupts are stuck.
::
:: - the srcbus entry in the mptable does not have to be
:: translated into
:: a PCI-bus value.
::
:: - add more APIC versions to the whitelist
::
:: - initialize mp_bus_id_to_pci_bus[] correctly, so that we can detect
:: nonlisted/bridged PCI busses more accurately.
::
:: the patch should only affect systems that were not working properly
:: before, but it might break broken-mptable systems - we'll see.
::
:: Ingo
::
next prev parent reply other threads:[~2001-05-30 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 11:11 [patch] ioapic-2.4.5-A1 Ingo Molnar
2001-05-30 10:26 ` Juha Saarinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 15:24 Ben Twijnstra
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='045001c0e8f2$f5774d20$0a01a8c0@den2' \
--to=juha@saarinen.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=mingo@elte.hu \
/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