From: Justin Mattock <justinmattock@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [PATCH] add missing definitions(letters) to HD-Audio.txt
Date: Wed, 15 Apr 2009 08:35:18 -0700 [thread overview]
Message-ID: <dd18b0c30904150835l6d246bbes648ad50e20690e7e@mail.gmail.com> (raw)
In-Reply-To: <s5hiql618mt.wl%tiwai@suse.de>
On Wed, Apr 15, 2009 at 4:03 AM, Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 14 Apr 2009 14:31:21 -0700,
> Justin Mattock wrote:
>>
>> impact: Add missing definitions(letters).
>>
>> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
>
> Thanks, applied now.
>
> (BTW, your patch couldn't be applied cleanly, partly because of
> a wrong format and partly because of your MUA breaking the lines...)
>
>
> Takashi
>
>>
>> ---
>> Documentation/sound/alsa/HD-Audio.txt | 3 +++
>> 1 files changed,3 insertions(+),0 deletions(-)
>>
>> ===========================================================================================
>> ---- Documentation/sound/alsa/HD-Audio.txt 2009-04-14
>> 17:03:14.000000000 -0700
>> ++++ Documentation/sound/alsa/HD-Audio.txt 2009-04-14
>> 21:15:22.000000000 -0700
>> @@ -162,7 +162,7 @@
>> What `model` option values are available depends on the codec chip.
>> Check your codec chip from the codec proc file (see "Codec Proc-File"
>> section below). It will show the vendor/product name of your codec
>> -chip. Then, see Documentation/sound/alsa/HD-Audio-Modelstxt file,
>> +chip. Then, see Documentation/sound/alsa/HD-Audio-Models.txt file,
>> the section of HD-audio driver. You can find a list of codecs
>> and `model` options belonging to each codec. For example, for Realtek
>> ALC262 codec chip, pass `model=ultra` for devices that are compatible
>> @@ -170,7 +170,7 @@
>>
>> Thus, the first thing you can do for any brand-new, unsupported and
>> non-working HD-audio hardware is to check HD-audio codec and several
>> -different `model` option values. If you have a luck, some of them
>> +different `model` option values. If you have any luck, some of them
>> might suit with your device well.
>>
>> Some codecs such as ALC880 have a special model option `model=test`.
>>
>>
>>
>> --
>> Justin P. Mattock
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
>
I went diff -u file.old file.new
(I'm not sure how to generate the
1 files changed,2 etc... stuff)
And yes I will be honest I didn't test the patch.
(figured it wasn't that complicated, and I was tired).
If I find more I'll let you know.
(back to trying to get sound working on my imac).
--
Justin P. Mattock
next prev parent reply other threads:[~2009-04-15 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:31 Justin Mattock
2009-04-15 11:03 ` [alsa-devel] " Takashi Iwai
2009-04-15 15:35 ` Justin Mattock [this message]
2009-04-15 15:56 ` Randy Dunlap
2009-04-15 17:43 ` Justin Mattock
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=dd18b0c30904150835l6d246bbes648ad50e20690e7e@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®