All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] hda: ALC260 test model implementation
Date: Mon, 06 Feb 2006 18:02:22 -0500	[thread overview]
Message-ID: <1139266943.2041.4.camel@mindpipe> (raw)
In-Reply-To: <200602062250.k16Mo0XK012879@auster.physics.adelaide.edu.au>

On Tue, 2006-02-07 at 09:20 +1030, Jonathan Woithe wrote:
> The following patch adds a "test" ALC260 model specification to the
> patch_realtek.c driver if CONFIG_SND_DEBUG is set.  This is similar to
> the "test" ALC880 model in that it sets up mixer controls for almost
> everything to make it easier for people to test their laptop/soundcard
> when working out what pin widgets are connected to which real-world
> devices.
> 

Man, these Intel HDA codecs are becoming a huge PITA... is there any end
in sight, or will users have to resort to trial and error every time any
vendor releases a new laptop?  This is starting to feel like the ACPI
situation... hmm, Intel designed that too, coincidence?

;-)

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-06 23:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 22:50 [PATCH] hda: ALC260 test model implementation Jonathan Woithe
2006-02-06 23:02 ` Lee Revell [this message]
2006-02-06 23:22   ` Jonathan Woithe
2006-02-06 23:26     ` Lee Revell
2006-02-06 23:40       ` Jonathan Woithe
2006-02-07 21:19         ` Takashi Iwai
2006-02-07 23:48           ` Jonathan Woithe
2006-02-09  5:59 ` Rimas Kudelis
2006-02-09  6:20   ` Lee Revell

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=1139266943.2041.4.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    /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.