From: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [ANN] ALSA 1.0 schedule
Date: Sat, 25 Oct 2003 22:22:27 +0200 [thread overview]
Message-ID: <3F9ADB83.20008@gmx.de> (raw)
In-Reply-To: <s5hpth558n8.wl@alsa2.suse.de>
Hi,
this is not a *very* important issue, but the problem should be solved
quite easy:
For me, 4channel output (indep. front and rear output) works with the
Terratec XFire (cs46xx), but for some not -- at least not without
modifying the driver.
for the problem description see:
http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg08393.html
the problem was solved as described here:
http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg08500.html
Maybe the changes to alsa-kernel/pci/cs46xx/cs46xx_lib.c described there
are already the correct solution.
fe
Takashi Iwai wrote:
> Hi,
>
> as many of you might expect, we're reaching to the ALSA version 1.0.
> Now as the 2.6.0-test kernel is being frozen, we also decided to
> freeze the ALSA 1.0 feature. The 1.0 release is scheduled at the end
> of October.
>
> You can find some TODOs for 1.0 and 1.1 in the cvs repository
> (TODO-1.0, and TODO-1.1).
>
> If you have *important* bugs not listed there, please let us know.
> We'll try to fix before 1.0 release.
> Also, if you have pending patches, please submit them ASAP.
>
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-25 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 17:01 [ANN] ALSA 1.0 schedule Takashi Iwai
2003-10-25 20:22 ` Friedrich Ewaldt [this message]
2003-10-27 11:24 ` 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=3F9ADB83.20008@gmx.de \
--to=friedrich.ewaldt@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--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 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.