From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Andy Shevchenko <andy@smile.org.ua>, alsa-devel@alsa-project.org
Subject: Re: Same pci id for different ASUS machine
Date: Wed, 19 Mar 2008 15:45:58 +0100 [thread overview]
Message-ID: <s5hwsnykc0p.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080318185740.GA30373@sirena.org.uk>
At Tue, 18 Mar 2008 18:57:41 +0000,
Mark Brown wrote:
>
> On Tue, Mar 18, 2008 at 06:12:14PM +0100, Takashi Iwai wrote:
> > Andy Shevchenko wrote:
>
> > > example? Could we make more flex configuration in the ALSA instead of
> > > hardcoded model= in the modprobe.conf?
>
> > Windows have *.INI files so that they can ignore broken BIOS. Or in
> > other way round - due to this, the hardware vendors never ship the
> > correct BIOS!
>
> Worse, fixing the BIOS would probably break driver level workarounds :/
No, in the case HD-audio, it won't normally. The driver level
workarounds are simply to override (thus ignore) the BIOS
definitions and use the static configuration.
> > I have patches to make some stuff dynamically re-configurable,
> > e.g. overriding the default pin-config or additional verbs together
> > with some hints to the parser, which can be set up via udev etc.
>
> I guess the kernel could do the quirking for most cases by using DMI
> information to identify the broken BIOSes, though there are obvious
> advantages to user space workarounds so it may not be worth it for
> something like sound which is unlikely to be needed to boot.
The quirks have been already there in HD-audio driver. But the
problem is that there are far too many. That's why we need a better,
more flexible approach now, adjustable from the user-space after
loading the driver.
Takashi
prev parent reply other threads:[~2008-03-19 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 2:48 Same pci id for different ASUS machine Jiang zhe
2008-03-13 7:37 ` Takashi Iwai
2008-03-17 20:19 ` Andy Shevchenko
2008-03-18 17:12 ` Takashi Iwai
2008-03-18 18:57 ` Mark Brown
2008-03-19 14:45 ` Takashi Iwai [this message]
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=s5hwsnykc0p.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andy@smile.org.ua \
--cc=broonie@opensource.wolfsonmicro.com \
/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