All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Marcelo Tosatti <marcelo-KCZ47A4bww4P48s/oLjRZg@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	hps-NuKNLqtyCiEuZeo0DBJMuQ@public.gmane.org
Subject: Re: [BK PATCH] ACPI Updates for 2.4
Date: Wed, 13 Aug 2003 18:20:02 -0400	[thread overview]
Message-ID: <3F3AB992.4000506@pobox.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470255EECD-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>

This ACPI update also fixes the irq routing issues I was seeing in 
2.4.22-rc2.  Previously, on Intel ICH5, I had to either disable 
CONFIG_ACPI (which makes my 2nd HT CPU disappear) and boot with 
'noapic', or disable CONFIG_SMP and boot with pci=noacpi.  If I did not 
do this, interrupts to the PCI slots would never be delivered.

With this update, 2.4 now matches 2.6 behavior:
full hyperthread, and interrupts routed correctly.

	Jeff

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	hps@intermeta.de
Subject: Re: [BK PATCH] ACPI Updates for 2.4
Date: Wed, 13 Aug 2003 18:20:02 -0400	[thread overview]
Message-ID: <3F3AB992.4000506@pobox.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470255EECD@orsmsx401.jf.intel.com>

This ACPI update also fixes the irq routing issues I was seeing in 
2.4.22-rc2.  Previously, on Intel ICH5, I had to either disable 
CONFIG_ACPI (which makes my 2nd HT CPU disappear) and boot with 
'noapic', or disable CONFIG_SMP and boot with pci=noacpi.  If I did not 
do this, interrupts to the PCI slots would never be delivered.

With this update, 2.4 now matches 2.6 behavior:
full hyperthread, and interrupts routed correctly.

	Jeff




  parent reply	other threads:[~2003-08-13 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 22:36 [BK PATCH] ACPI Updates for 2.4 Grover, Andrew
2003-08-12 22:36 ` Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A8470255EECD-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-08-13 13:54   ` [ACPI] " Alan Cox
2003-08-13 13:54     ` Alan Cox
     [not found]     ` <1060782897.8513.50.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-08-13 14:55       ` Willy Tarreau
2003-08-13 14:55         ` Willy Tarreau
2003-08-13 22:20   ` Jeff Garzik [this message]
2003-08-13 22:20     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13  8:55 Yu, Luming
2003-08-13  8:55 ` Yu, Luming

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=3F3AB992.4000506@pobox.com \
    --to=jgarzik-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=hps-NuKNLqtyCiEuZeo0DBJMuQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marcelo-KCZ47A4bww4P48s/oLjRZg@public.gmane.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.