From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jean Delvare <jdelvare@suse.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Daniel Drake <dsd@reactivated.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: via irq quirk breakage
Date: Mon, 29 Jan 2007 15:51:25 +0000 [thread overview]
Message-ID: <20070129155125.74758322@localhost.localdomain> (raw)
In-Reply-To: <200701291600.32580.jdelvare@suse.de>
> 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.
My PCI tree is somewhat different to the default one and I did test it
but possibly sucked in some dependancies on the cyrix and other early PCI
handling changes in my dev tree.
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
Acked-by: Alan Cox <alan@redhat.com>
This is a lot neater than the original patch too. Only problem I see is
pci=reverse might need more care.
Alan
next prev parent reply other threads:[~2007-01-29 15:41 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 [this message]
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
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=20070129155125.74758322@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=dsd@reactivated.net \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.