All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Stafford <jstafford@ampltd.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Envy24HT
Date: Wed, 04 Dec 2002 14:38:32 +0000	[thread overview]
Message-ID: <m18JajL-003yUYC@mail.corpex.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212041402420.521-100000@pnote.perex-int.cz>

At 14:05 04/12/02 +0100, Jaroslav Kysela wrote:
 
>> I have added a build_controls function in the amp.c file which sets the
>> relavent ac97 register. Is this the correct way to do this?
>
>The controls should be built in the ac97_codec.c, but the initial settings 
>of AC97 registers might be done in the amp.c file.

All the controls are built in ac97_codec.c. I only write to one of the ac97
registers in the build_controls function from the snd_ice1712_card_info
structure because it was the only card specific function call after the
call to snd_ice1712_ac97_mixer. Would it be better to add a new function
pointer to the snd_ice1712_card_info structure for setting the initial
values of the chip specific ac97 registers (such as the rerouting of some
of the outputs) ?
I thought it was best not to write the ac97 register in ice1712.c since not
all Envy24HT cards use the VT1616.

>If you follow the ICH.conf file (and/or ICE1712.conf) file, then you can 
>use 'surround51' device as ac3dec uses: 'aplay -D plug:surround51' .
>The new name will be ICE1724.conf (I changed the driver ID for the new 
>chip). Unfortunately, at the time, we cannot distinguish more 
>hardware variations for given driver, but hopefully, it will change in the 
>future.

Ok, I understand you now. 

--
James Stafford


mailto:jstafford@ampltd.com

Advanced Micro Peripherals Ltd 
Unit 17
Sedgeway Business Park
Witchford
Cambridge
CB6 2HY

Tel: +44 1353 659 500 
Fax:+44 1353 659 600 



-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET 
comprehensive development tool, built to increase your 
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en

  reply	other threads:[~2002-12-04 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m18JZ72-003yUIC@mail.corpex.com>
2002-12-04 13:05 ` [PATCH] Envy24HT Jaroslav Kysela
2002-12-04 14:38   ` James Stafford [this message]
2002-12-04 17:29     ` James Stafford
2003-01-27 13:31 James Stafford
2003-01-27 14:02 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2002-11-25 12:06 Envy24HT Jaroslav Kysela
2002-11-24 20:32 ` Envy24HT James Stafford
2002-11-27 21:47   ` Envy24HT James Stafford
2002-12-03 17:07     ` [PATCH] Envy24HT James Stafford
2002-12-03 18:06       ` Jaroslav Kysela
2002-12-04 12:54         ` James Stafford

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=m18JajL-003yUYC@mail.corpex.com \
    --to=jstafford@ampltd.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /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.