Hello
It would be nice if there was a feature in alsa that would let the user
tell alsa which speakers are plugged into which sound card sockets.
E.g. On sound card 0, I have: -
Left speaker in Stereo Jack 1-Left
Right speaker in Stereo Jack 1-Right
Rear Left in Stereo Jack 2 - Left
Rear Right
Hi all,
I was wondering when we can expect an update to ALSA in the kernel source -
we're still on -rc2, aren't we? Now that 2.5.x is getting a little more
useable, I'd like to start running it again (I stopped at 2.5.25 as it really
did become too dangerous). But I want ALSA :-)
I'm
Takashi Iwai [EMAIL PROTECTED] writes:
* via8233 -- fixed
no problems now (on cvs it's merged together with via686 as
snd-via82xx driver)
i got reports saying via686 produce digital noise since we switched
from alsa-0.9.0 rc2 to rc3
At Wed, 02 Oct 2002 13:25:00 +0200,
Thierry Vignaud wrote:
Takashi Iwai [EMAIL PROTECTED] writes:
* via8233 -- fixed
no problems now (on cvs it's merged together with via686 as
snd-via82xx driver)
i got reports saying via686 produce digital noise since we switched
from
Takashi Iwai [EMAIL PROTECTED] writes:
i got reports saying via686 produce digital noise since we
switched from alsa-0.9.0 rc2 to rc3
drivers for via chip were merged now to snd-via82xx, and many fixes
have been done on it. please check the cvs version.
that's what i said to the guy but
Hi Paul,
At Wed, 2 Oct 2002 07:57:57 -0400,
Paul Davis wrote:
takashi - i can't post to alsa-devel at the moment (my ISP and sf.net
have messed up their configuration somehow).
oh it's bad...
i tried sending these via
jaroslav, but i got no reply whatsoever and they never showed up on
On Wednesday 02 Oct 2002 11:44, Jaroslav Kysela wrote:
On Wed, 2 Oct 2002, Peter L Jones wrote:
Hi all,
I was wondering when we can expect an update to ALSA in the kernel source
- we're still on -rc2, aren't we? Now that 2.5.x is getting a little
more useable, I'd like to start
Takashi Iwai [EMAIL PROTECTED] writes:
2) i recently compiled rc3 on a mandrake 8.2 system. everything
went smoothly. when i went to modprobe, i got messages suggesting
to me that there a mismatch between the kernels and the ALSA
modules with respect to symbol versioning. (several
Takashi Iwai [EMAIL PROTECTED] writes:
4) note that if you boot with a kernel with alsa-0.9.0, all your
alsa apps won't work unless you use them in oss emulation mode.
why? is there any incompatibility?
i presume you joke ?
remember the incompatible apis of alsa-0.5.x and alsa-0.9.x
At Thu, 26 Sep 2002 12:42:32 -0700 (PDT),
Fedor G. Pikus [EMAIL PROTECTED] wrote:
This is the right interface and altset (I was capturing with -r 96000 -f
S16_LE). Two more files from proc about this pcm:
pcm0c/sub0/hw_params
access: RW_INTERLEAVED
format: S16_LE
subformat: STD
channels:
Hello!
I haven't done any development for sound in the userspace, so don't put
too much weight into my words, but for what it's worth ...
i'd like to rewrite configure for alsa-utils and alsa-tools to use
pkg-config for alsa-lib. you might have found alsa.pc already in
alsa-lib. the only
Hi,
At Wed, 2 Oct 2002 09:46:52 -0400 (EDT),
Pavel Roskin wrote:
Hello!
I haven't done any development for sound in the userspace, so don't put
too much weight into my words, but for what it's worth ...
i'd like to rewrite configure for alsa-utils and alsa-tools to use
pkg-config
---BeginMessage---
[ please forward to [EMAIL PROTECTED] ]
While at this issue, is it possible to compile everything from CVS without
intermediate installs? I mean, compile alsa-lib against the headers of
alsa-driver in CVS and alsa-util against alsa-lib in CVS. If it's
possible, please make
---BeginMessage---
[ the usual forward request for [EMAIL PROTECTED] ]
i have a bit of a problem with all of this. why doesn't ALSA build
out of the box? the description you've given of what is necessary
to get this to work seems (for the most part) to be a bit
ridiculous.
insulting
Paul Davis [EMAIL PROTECTED] writes:
its just that my experience of using ALSA for several years when
built with a kernel from kernel.org has been that i just type:
cd .../alsa-cvs/alsa-{driver,lib,utils}
then
cvscompile
or
./configure make make install
and it works. i
i have a bit of a problem with all of this. why doesn't ALSA build
out of the box? the description you've given of what is necessary
to get this to work seems (for the most part) to be a bit
ridiculous.
insulting people that take time to answer you has always been a
constructive
Once upon a time, Takashi wrote :
the problem is that many different kernel binaries are built using the
same kernel tree, i.e. there are many different kernel configs while
there is only one kernel-source package.
thus you have to adjust the kernel config by yourself anyway.
in case
Takashi Iwai wrote:
Hi,
At Wed, 02 Oct 2002 15:17:10 +0200,
Thierry Vignaud wrote:
Takashi Iwai [EMAIL PROTECTED] writes:
2) i recently compiled rc3 on a mandrake 8.2 system. everything
went smoothly. when i went to modprobe, i got messages suggesting
to me that there a mismatch between
On Wed, 2 Oct 2002, Peter L Jones wrote:
On Wednesday 02 Oct 2002 11:44, Jaroslav Kysela wrote:
[snip]
ALSA tree was fully synced with kernel yesterday. Not all changes are in
2.5.40. Please, wait for 2.5.41 or get the kernel sources from BitKeeper
repository of 2.5.
Matthias Saou [EMAIL PROTECTED] writes:
I've managed to work something out for Red Hat Linux that should be
easily portable to Mandrake I guess (then again, they already have
ALSA 0.5.x built in, is that what I understood from the last few
mails??).
yep, we shipped alsa-0.5.x for quite some
Once upon a time, Thierry wrote :
since it must be rebuild for each kernel, we integrated in our kernel
package (first as a separate tarball with configure/make/..., now we
untar it under sound in kernel linux sources and apply a few patches
to config.in so that there's one make to run)
On Wednesday 02 Oct 2002 11:44, Jaroslav Kysela wrote:
[snip]
ALSA tree was fully synced with kernel yesterday. Not all changes are in
2.5.40. Please, wait for 2.5.41 or get the kernel sources from BitKeeper
repository of 2.5.
Jaroslav
Takashi,
Matthias Saou [EMAIL PROTECTED] writes:
All this will get so much easier once stable kernels used by Linux
distributions come with ALSA by default ;-)
Sure will.
Providing we stay focused on maintaining binary compatibility... :-)
--
Jack O'Quin
Austin, Texas, USA
Matthias Saou [EMAIL PROTECTED] writes:
All this will get so much easier once stable kernels used by Linux
distributions come with ALSA by default ;-)
suse mandrake come with alsa in their kernel, debian has a package,
rh doesn't
since linus posts on klm seems to indicate we'll have a new
Hello!
ALSA on CVS doesn't compile. alsa-driver/include/adriver.h has several
problems:
/usr/local/src/alsa/alsa-driver/include/adriver.h:186: parse error before
`dir'
/usr/local/src/alsa/alsa-driver/include/adriver.h:188: multiple storage
classes in declaration of
This is a re-post. We are still interested to know if work is planned to
implement digital I/O support for the M-Audio Audiophile 2496. Analog I/O
works fine with ALSA.
Thank you.
Robbie
---
This sf.net email is sponsored by:ThinkGeek
Welcome
Hi,
I was wondering for the example xrun_recovery function:
http://www.alsa-project.org/alsa-doc/alsa-lib/_2test_2pcm_8c-example.html#a15
In the ESTRPIPE case, it repeats to resume until it does not return EAGAIN
anymore. Then it calls snd_pcm_prepare only if snd_pcm_resume returned a
negative
27 matches
Mail list logo
