linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, mzielinski@wp-sa.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: unexpected IO-APIC on IBM xSeries 440
Date: Thu, 12 Sep 2002 09:45:55 -0700	[thread overview]
Message-ID: <572796648.1031823954@[10.10.2.3]> (raw)
In-Reply-To: <1031846309.2838.96.camel@irongate.swansea.linux.org.uk>

> I don't know what state 2.5 is on Summit numa but 2.4.19-ac and
> 2.4.20pre6 plus one patch (I can bounce you the diff if you want) should
> work nicely on summit chipsets with any distro

2.5 has some problems with interrupts and ACPI that were being
worked around ... the right people here will send you some stuff.

M.


  reply	other threads:[~2002-09-12 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 15:33 unexpected IO-APIC on IBM xSeries 440 Mariusz Zielinski
2002-09-12 15:58 ` Alan Cox
2002-09-12 16:45   ` Martin J. Bligh [this message]
2002-09-12 21:07     ` [PATCH] IBM x440 patches for 2.4 and 2.5 James Cleverdon

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='572796648.1031823954@[10.10.2.3]' \
    --to=mbligh@aracnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzielinski@wp-sa.pl \
    /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).