From: Sergey Vlasov <vsu@altlinux.ru>
To: Adrian Bunk <bunk@stusta.de>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz,
Daniel Ritz <daniel.ritz@gmx.ch>, Daniel Drake <dsd@gentoo.org>,
Jean Delvare <khali@linux-fr.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Linus Torvalds <torvalds@osdl.org>, Brice Goglin <brice@myri.com>,
"John W. Linville" <linville@tuxdriver.com>,
Bauke Jan Douma <bjdouma@xs4all.nl>,
Tomasz Koprowski <tomek@koprowski.org>
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Thu, 7 Dec 2006 16:53:52 +0300 [thread overview]
Message-ID: <20061207165352.9cb61023.vsu@altlinux.ru> (raw)
In-Reply-To: <20061207132430.GF8963@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Thu, 7 Dec 2006 14:24:30 +0100 Adrian Bunk wrote:
> While checking how to fix the VIA quirk regressions for several users
> introduced into -stable in 2.6.16.17, I started looking through all
> drivers/pci/quirks.c updates up to both -stable and 2.6.19.
>
> Below is the selection the seemed good and safe.
>
> Any comments on whether it's really good or whether I should change
> anything?
>
> TIA
> Adrian
>
>
> Bauke Jan Douma (1):
> PCI: quirk for asus a8v and a8v delux motherboards
This quirk will cause breakage for people who used an external PCI
soundcard with these boards - the builtin sound chip which was
invisible before may become the first audio device.
It also enables the MC97 device, which does not really work (there is
no MC97 codec attached to the controller at least on A8V Deluxe; I'm
not sure if there is some other variant of this board which has MC97,
but it seems unlikely).
[...]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-07 13:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 13:24 RFC: PCI quirks update for 2.6.16 Adrian Bunk
2006-12-07 13:53 ` Sergey Vlasov [this message]
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
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=20061207165352.9cb61023.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--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=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