From: Chris Wedgwood <cw@f00f.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Drake <dsd@gentoo.org>, Adrian Bunk <bunk@stusta.de>,
Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>,
Daniel Ritz <daniel.ritz@gmx.ch>,
Jean Delvare <khali@linux-fr.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Brice Goglin <brice@myri.com>,
"John W. Linville" <linville@tuxdriver.com>,
Bauke Jan Douma <bjdouma@xs4all.nl>,
Tomasz Koprowski <tomek@koprowski.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Sun, 10 Dec 2006 14:49:03 -0800 [thread overview]
Message-ID: <20061210224903.GA23643@tuatara.stupidest.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612101438080.12500@woody.osdl.org>
On Sun, Dec 10, 2006 at 02:39:37PM -0800, Linus Torvalds wrote:
> They should be safe, and OBVIOUS.
Well, it's not clear to me that reverting to a quirk the pokes *all*
VIA pci devices on all machines is safe, it's not even clear if it was
a good idea to merge this.
All the same, I can retest the latest 2.6.16.x with that change
reverted but since it originally caused pain there has been a BIOS
upgrade (or two, I forget) that might affect things (for many poeple
the quirk isn't needed and CPI does the right thing).
> If there is a box that breaks with a 2.6.x.y release, then that .y
> release was clearly a mistake, and fundamentally broke the whole
> point of the 3Astable tree.
Well, I think the current 2.6.16.x release series is already broken on
some other subset of hardware.
There might be more of those than there are with the quirk-me-hard
approach --- in which case do we try to accommodate the (potential)
majority with something that is clearly wrong or so we leave them
broken for a bit longer until we can get some more coverage on Alan's
much cleaner and specific fix which I think is slated for 2.6.20 and
then backport that?
next prev parent reply other threads:[~2006-12-10 22:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 13:24 Adrian Bunk
2006-12-07 13:53 ` Sergey Vlasov
2006-12-07 17:27 ` Bauke Jan Douma
2006-12-07 18:32 ` Sergey Vlasov
2006-12-08 15:34 ` Adrian Bunk
2006-12-07 14:38 ` Daniel Drake
2006-12-07 14:57 ` Adrian Bunk
2006-12-07 16:37 ` Alan Cox
2006-12-10 4:09 ` Sergio Monteiro Basto
2006-12-10 16:00 ` Adrian Bunk
2006-12-10 16:22 ` Daniel Drake
2006-12-10 22:33 ` Chris Wedgwood
2006-12-10 22:39 ` Linus Torvalds
2006-12-10 22:49 ` Chris Wedgwood [this message]
2006-12-11 1:17 ` Linus Torvalds
2006-12-10 23:47 ` Adrian Bunk
2006-12-11 1:23 ` Linus Torvalds
2006-12-11 12:52 ` Adrian Bunk
2006-12-19 6:08 ` Sergio Monteiro Basto
2006-12-11 1:42 ` Sergio Monteiro Basto
2006-12-11 12:41 ` Adrian Bunk
2006-12-11 12:48 ` Sergio Monteiro Basto
2006-12-11 13:01 ` Adrian Bunk
2006-12-07 19:54 ` Jean Delvare
2006-12-07 20:45 ` Tomek Koprowski
2006-12-08 15:42 ` Adrian Bunk
2006-12-08 16:11 ` RFC: PCI quirks update for 2.6.16 (v2) Adrian Bunk
2006-12-08 21:02 ` RFC: PCI quirks update for 2.6.16 Brice Goglin
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=20061210224903.GA23643@tuatara.stupidest.org \
--to=cw@f00f.org \
--cc=bjdouma@xs4all.nl \
--cc=bjorn.helgaas@hp.com \
--cc=brice@myri.com \
--cc=bunk@stusta.de \
--cc=daniel.ritz@gmx.ch \
--cc=dsd@gentoo.org \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linville@tuxdriver.com \
--cc=sergio@sergiomb.no-ip.org \
--cc=tomek@koprowski.org \
--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
all inboxes | Powered by JetHome®