public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>
Cc: Linus Torvalds <torvalds@osdl.org>, Dave Jones <davej@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@osdl.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cardbus: revert IO window limit
Date: Wed, 12 Jul 2006 08:54:35 +0200	[thread overview]
Message-ID: <44B49CAB.60206@manoweb.com> (raw)
In-Reply-To: <200607010003.31324.daniel.ritz-ml@swissonline.ch>

Daniel Ritz wrote:

> register is hidden at the very same place (32bit at 0x90 in function 3 of the
> "south" brigde)...so the attached little patch might be enough to fix things...
> 
> Alessio, could you try that one on top of a kernel that shows the problem?

well sorry for being so late but I had some lectures to do and... by the
way, everybody on this msiling list is officially invited at the
Planetarium of Lecco - if you happen to pass by northern Italy just drop
me an email... :)

You know... this patch works :)
I'm now running the latest kernel in the git repository with APM enabled
and everything is working fine! I will qute the patch below.

Thank you
Alessio Sangalli

diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 4364d79..1d26a64 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -401,6 +401,8 @@ static void __devinit quirk_piix4_acpi(s
 	piix4_io_quirk(dev, "PIIX4 devres J", 0x7c, 1 << 20);
 }
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,
PCI_DEVICE_ID_INTEL_82371AB_3,	quirk_piix4_acpi );
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,
PCI_DEVICE_ID_INTEL_82443MX_3,	quirk_piix4_acpi );
+

 /*
  * ICH4, ICH4-M, ICH5, ICH5-M ACPI: Three IO regions pointed to by
longwords at

  parent reply	other threads:[~2006-07-12  6:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30 22:03 [PATCH] cardbus: revert IO window limit Daniel Ritz
2006-06-30 22:18 ` Linus Torvalds
2006-06-30 23:09   ` Daniel Ritz
2006-06-30 23:21     ` Linus Torvalds
2006-07-05  6:56       ` Pekka J Enberg
2006-07-12  7:55       ` Alessio Sangalli
2006-07-12 15:18         ` Linus Torvalds
2006-07-13  6:29           ` Alessio Sangalli
2006-07-12  7:29   ` Alessio Sangalli
2006-07-12  6:54 ` Alessio Sangalli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 18:29 Mallick, Asit K
2006-06-22  6:48 Pekka J Enberg
2006-06-22  7:11 ` Andrew Morton
2006-06-22  7:53   ` Alessio Sangalli
2006-06-22 11:35   ` Alan Cox
2006-06-22 16:18     ` Linus Torvalds
2006-06-22 16:36       ` Andrew Morton
2006-06-22 17:07         ` Linus Torvalds
2006-06-22 20:01           ` Alessio Sangalli
2006-06-22 21:27           ` Alessio Sangalli
2006-06-30  4:34             ` Pekka Enberg
2006-06-30 19:10             ` Linus Torvalds
2006-06-30 19:19               ` Dave Jones
2006-06-30 19:26                 ` Dave Jones
2006-06-30 22:15                   ` Linus Torvalds
2006-06-22 16:16   ` Linus Torvalds

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=44B49CAB.60206@manoweb.com \
    --to=alesan@manoweb.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@osdl.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