public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bauke Jan Douma <bjdouma@xs4all.nl>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Adrian Bunk <bunk@stusta.de>,
	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>,
	Tomasz Koprowski <tomek@koprowski.org>
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Thu, 07 Dec 2006 18:27:40 +0100	[thread overview]
Message-ID: <45784F0C.7040005@xs4all.nl> (raw)
In-Reply-To: <20061207165352.9cb61023.vsu@altlinux.ru>

Sergey Vlasov wrote on 07-12-06 14:53:
> 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.
>>
[snip]
>>
>>
>> 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.

I'm afraid I don't understand the problem described here, when
ALSA can assign any arbitrary index number of a user's choice
to cards that are detected.

Indeed, on my system (an A8V Deluxe motherboard, with this
quirk active), my first soundcard (given index=0) is an offboard
Creative SB Live, and the onboard card I have assigned index=1.

I for one need this quirk to get both soundcards at all (which
I need) -- no matter what indexing order.

> 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).

This one can be disabled separate of the AC97 -- let me get back
on that.  I, for one (however much that is), don't need it either.


bjd

  reply	other threads:[~2006-12-07 17:28 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
2006-12-07 17:27   ` Bauke Jan Douma [this message]
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=45784F0C.7040005@xs4all.nl \
    --to=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 \
    --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