From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jean Delvare <jdelvare@suse.de>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Drake <dsd@reactivated.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] VIA IRQ quirk breakage fix
Date: Wed, 31 Jan 2007 00:38:02 +1100 [thread overview]
Message-ID: <45BF4A3A.2040001@yahoo.com.au> (raw)
In-Reply-To: <200701301325.58843.jdelvare@suse.de>
Jean Delvare wrote:
> Hi Sergey,
>
> Le Mardi 30 Janvier 2007 12:47, Sergey Vlasov a écrit :
>
>>The VT82C686 is very different from other devices, because it is
>>a PCI chip, and its device number is determined by IDSEL wiring.
>>Google shows that several different assignments are in use:
>>
>>00:01.0:
>>http://ozlabs.org/pipermail/linuxppc-embedded/2005-January/016642.html
>>(but that's PPC)
>>
>>00:04.0: http://www.cs.helsinki.fi/linux/linux-kernel/2001-36/0083.html
>>00:05.0: http://lkml.org/lkml/2003/12/11/78
>>00:07.0: this example and lots of other links
>>00:14.0: http://forum.freespire.org/showthread.php?t=2998
>
>
> Ah, OK. Thanks for the exhaustive search and explanation. This explains
> why Alan and Nick disagreed on the device number.
...
> Yes, this sounds like the right thing to do. So here comes the third
> (and hopefully last) iteration of the patch:
Thanks Jean, this patch works fine for me.
Is this 2.6.20 material? Might it cause more regressions than it fixes?
Andrew, can you pick up this patch in place of the old one you got
(fix-via-irq-quirk-breakage.patch). It was sent to lkml just now.
> Fix VIA quirks that were recently broken by Alan Cox in the upstream
> kernel (commit 1597cacbe39802d86656d1f2e6329895bd2ef531).
>
> My understanding is that pci_find_present() doesn't work yet at the
> time the quirks are run. So I used a two-step quirk as is done for
> some other quirks already. First we detect the VIA south bridges
> and set the right low and high device limits, then we are ready to
> actually run the quirks on the affected devices.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Acked-by: Alan Cox <alan@redhat.com>
> ---
> drivers/pci/quirks.c | 80 +++++++++++++++++++++++++++-----------------------
> 1 files changed, 44 insertions(+), 36 deletions(-)
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2007-01-30 13:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 0:33 via irq quirk breakage Nick Piggin
2007-01-29 15:00 ` Jean Delvare
2007-01-29 15:51 ` Alan
2007-01-30 12:29 ` Jean Delvare
2007-01-30 16:05 ` Alan
2007-01-30 2:35 ` Nick Piggin
2007-01-30 7:54 ` Jean Delvare
2007-01-30 8:32 ` Nick Piggin
2007-01-30 11:47 ` Sergey Vlasov
2007-01-30 12:25 ` [PATCH] VIA IRQ quirk breakage fix Jean Delvare
2007-01-30 13:38 ` Nick Piggin [this message]
2007-01-30 13:49 ` Jean Delvare
2007-01-30 16:21 ` Alan
2007-01-30 16:17 ` Jean Delvare
2007-01-30 18:02 ` Andrew Morton
2007-01-31 2:37 ` Andrew Morton
2007-02-01 7:39 ` Jean Delvare
2007-01-30 14:56 ` via irq quirk breakage Alan
2007-01-30 14:50 ` Jeff Garzik
2007-01-30 14:25 ` Alan
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=45BF4A3A.2040001@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=dsd@reactivated.net \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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