All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Bauke Jan Douma <bjdouma@xs4all.nl>,
	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: Fri, 8 Dec 2006 16:34:05 +0100	[thread overview]
Message-ID: <20061208153405.GA3356@stusta.de> (raw)
In-Reply-To: <20061207183217.GA7865@procyon.home>

On Thu, Dec 07, 2006 at 09:32:17PM +0300, Sergey Vlasov wrote:
> On Thu, Dec 07, 2006 at 06:27:40PM +0100, Bauke Jan Douma wrote:
>...
> > I for one need this quirk to get both soundcards at all (which
> > I need) -- no matter what indexing order.
> 
> I don't question the need for this patch in mainline; however, it does
> not seem to be suitable for -stable.
>...

Thanks to both of you.
First of all, I agree that this is not 2.6.16 material.

And looking at this issue at my A7V600-X, it's also a "feature" of this 
quirk that it enables the onboard audio even if you explicitely disabled 
it in the BIOS. I'm not sure about the correct solution in this case.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-12-08 15:33 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
2006-12-07 18:32     ` Sergey Vlasov
2006-12-08 15:34       ` Adrian Bunk [this message]
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=20061208153405.GA3356@stusta.de \
    --to=bunk@stusta.de \
    --cc=bjdouma@xs4all.nl \
    --cc=bjorn.helgaas@hp.com \
    --cc=brice@myri.com \
    --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 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.