Revert dmix.conf and dsnoop.conf.
The ipc key offset had been already modified to be unique for
each card, stream, device and subdevice interanally in dmix &
co plugins.
- add long card name to device description
- create empty PCM plugin to allow right hint description parsing
- reorder devices in alsa.conf
- make namehint more configurable (using default.namehint.showall switch)
- add two levels basic and exteded for hints to default configuration files
- do not show direct device aliases
- removed all known memory leaks
- add snd_device_name_hint() and snd_device_name_free_hint() functions
- add snd_ctl_iface_conf_name() functions
- do not accept parameters for the plugin definition without @args section
- add defaults.pcm.dmix.card/device and dsnoop.card/device definitions
- add hints for HDA-Intel.conf, pcm/dmix.conf, pcm/dsnoop.conf and alsa.conf
- add test/namehint test utility
- doxygen related cleanups
-lm -ldl -lpthread are _not_ needed in Libs (since the alsa interface
doesn't depend on libm, libdl or libpthread interface) and just bring
unneeded dependencies. These should rather be put in Libs.private:
Libs: -L${libdir} -lasound
Libs.private: -lm -ldl -lpthread
See ALSA bug#2212 .
Use dmix/dsnoop for maestro3 boards. Although maestro3 has multiple
playback capability, it supports only two streams (with the currently
available firmware).
the current configure script assumes that it will be run in the srcdir ... i
often build things out of tree so you can quickly punt all the generated
files:
mkdir build
cd build
../configure
cd ..
rm -r build
clean!
this tweaks the configure script in a few places to use the correct variable
instead of assuming that configure is always in $PWD ...
i say "sort of" in the subject because there is still the issues of the pcm
symbols list being generated in $builddir instead of $srcdir and the alsa
include symlink, but these doesnt really concern me for what i need ;)
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Some architectures, such as AMD64, IA64 and Alpha cannot mix PIC and non-PIC
objects when creating a PIC output. Hardened compilers (which uses SSP and
PIE) creates PIC executables, passing -static in CFLAGS for tests in make
check in alsa-lib makes their linking to fail.
See bug#1541
If volume or switch write fails, the internal contents for element
is changed, but it is wrong. Reread the whole simple element in this
case to get correct values.
See: bug#2274
checking for versioned symbols... ./configure: line 19347: test: "1: integer
expression expected
./configure: line 19350: test: "1: integer expression expected
This is caused by my libtool VERSION string:
VERSION="1.5.22 Debian 1.5.22-2"
The test in configure.in can't currently deal with the quotes.
Make sure that the rate plugin does not try to change the slave's
boundary value when setting software parameters; such a change wouldn't
affect the slave pcm.
Furthermore, the stop_threshold conversion code used the wrong boundary
value, and the silence_size conversion code did not take into account
the boundary value at all.
the alisp.c file includes wordexp.h even though it doesnt actually use any
wordexp functions ... causes trouble when target doesnt have wordexp
support :)
patch attached to scrub said headers
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
the src/names.c file includes many more headers than it actually needs ...
this causes troubles when porting to a target that lacks those headers :)
patch attached to scrub said headers
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
From: Mike Frysinger <vapier@gentoo.org>
some architectures, like Blackfin, have a prefix added to all symbols (in our
case it's historical baggage)
while normally packages shouldnt care, when code starts mixing assembler with
C (like symbol versioning), you need to dip down into the inner details.
find attached a patch which queries gcc for the prefix (all gcc toolchains
have a builtin define of __USER_LABEL_PREFIX__) and then automatically has
asm() constructs utilize this
since most targets define __USER_LABEL_PREFIX__ to nothing, hopefully this
shouldnt cause any problems :)
safe_strtoll() now accepts numbers in any base. It formerly assumed that
its input was a decimal number, which had the consequence that
hexadecimal or octal numbers would be parsed as strings when occurring
outside of parameter lists.
This obsoletes some workarounds in the file permission parsing code that
relied on this bug.
Check whether non-zero size TLV is really returned by comparing
with the pre-filled pattern. ALSA 1.0.12 driver doesn't notify
the error even if user TLV is empty, so the previous value is
passed bogusly.
