linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: "Linux-Kernel," <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [2.6.18-rc2-mm1] pata_via fails
Date: Wed, 02 Aug 2006 00:18:27 +0100	[thread overview]
Message-ID: <1154474307.3819.5.camel@localhost.portugal> (raw)
In-Reply-To: <20060802010415.2bebc5fc@werewolf.auna.net>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On Wed, 2006-08-02 at 01:04 +0200, J.A. Magallón wrote:
> Jul 10 15:09:46 nada kernel: PCI: VIA IRQ fixup for 0000:00:11.1, from
> 255 to 0
> Any ideas ?
yes, try this patch
http://lkml.org/lkml/2006/7/28/99
As you are using -mm tree use just hunk #1 above

--- linux-2.6.17.i686/drivers/pci/quirks.c.orig	2006-07-28 12:59:04.000000000 +0100
+++ linux-2.6.17.i686/drivers/pci/quirks.c	2006-07-28 13:26:49.000000000 +0100
@@ -648,11 +648,17 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_V
  *
  * Some of the on-chip devices are actually '586 devices' so they are
  * listed here.
+ * 
+ * if flags say that we have working apic(s), we don't need to quirk these
+ * devices
  */
 static void quirk_via_irq(struct pci_dev *dev)
 {
 	u8 irq, new_irq;
 
+	if ((smp_found_config && !skip_ioapic_setup && nr_ioapics) || cpu_has_apic)
+		return;
+
 	new_irq = dev->irq & 0xf;
 	pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
 	if (new_irq != irq) {


-- 
Sérgio M. B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]

  reply	other threads:[~2006-08-01 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 23:04 [2.6.18-rc2-mm1] pata_via fails J.A. Magallón
2006-08-01 23:18 ` Sergio Monteiro Basto [this message]
2006-08-02 21:43   ` J.A. Magallón
2006-08-01 23:45 ` Alan Cox

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=1154474307.3819.5.camel@localhost.portugal \
    --to=sergio@sergiomb.no-ip.org \
    --cc=jamagallon@ono.com \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).