From: Takashi Iwai <tiwai@suse.de>
To: "Tien, C.L." <cltien@cmedia.com.tw>
Cc: alsa-devel@alsa-project.org
Subject: Re: [patch] patch_cm9880.c to support multi-channel
Date: Tue, 29 Mar 2005 14:18:36 +0200 [thread overview]
Message-ID: <s5hu0muir1f.wl@alsa2.suse.de> (raw)
In-Reply-To: <92C0412E07F63549B2A2F2345D3DB515F7D6D2@cm-msg-02.cmedia.com.tw>
At Sun, 27 Mar 2005 23:19:02 +0800,
Tien, C.L. wrote:
>
> I got configuration info from Windows driver's .INI file, there are
> totally 28 configuration so I think it is impractical to use parameter
> to fits user's needs.
>
> I want to add configuration for 6-stack first since most of the M/Bs
> have them.
OK, that's fine. A patch would be appreciated as always ;)
> Then I plan to add code to probe the jacks for multi-channel
> playback, so driver can find which pin for front/rear/side/LFE by
> itself without parameter help. The line-out/line-in/mic etc. should
> also can be detected without a fixed table.
That's exactly what I wanted to implement after 1.0.9, too.
The basic infrastructure for unsolicited events is already implemented
as a callback to driver, but it's never tested yet.
My another plan for HD-audio is to add the hwdep interface to allow
users reconfigure the mixer interface (like .INI file of windows).
This will require a relatively big rewrite...
Takashi
>
> Sincerely,
> ChenLi Tien
>
>
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Sent: 2005/3/24 [星期四] 下午 03:40
> To: Tien, C.L. - 田承禮
> Cc: alsa-devel@alsa-project.org
> Subject: Re: [Alsa-devel] [patch] patch_cm9880.c to support multi-channel
> At Fri, 25 Mar 2005 01:53:06 +0800,
> Tien, C.L. wrote:
> >
> > I also added controls in the allout_init array. I wonder what this
> > model for because it is the same as basic_init except the line-in is
> > used as output in allout_init.
>
> It was coded so, just based on the example configuration described in
> the datasheet of CMI9880, in case any hardware is implemented in that
> way. Surely we can clean up these models.
>
> > I plan to add controls for 5/6 stacks , which lacks front panel but
> > has rear 5/6 jacks. Any idea?
>
> Go ahead, let's discuss together with the code :)
>
>
> Takashi
>
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
next prev parent reply other threads:[~2005-03-29 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 15:19 [patch] patch_cm9880.c to support multi-channel "Tien, C.L. - 田承禮"
2005-03-29 12:18 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 19:52 "Tien, C.L. - 田承禮"
2005-03-24 20:48 ` Takashi Iwai
2005-03-24 17:53 "Tien, C.L. - 田承禮"
2005-03-24 19:30 ` Lee Revell
2005-03-24 20:40 ` Takashi Iwai
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=s5hu0muir1f.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cltien@cmedia.com.tw \
/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