dfcb546256
the corresponding pad device open, or we get EIO from audio accesses Explained and fix provided by Nathanial Sloss <nat@n.o> Note: if we are testing and using real audio hardware, the open of /dev/pad0 is irrelevant (but harmless, so we don't attempt to check) and what's more it doesn't matter if it succeeds or fails. If we're testing under qemu (or any other situation where the only audio "hardware" is pad) then the open will work, and there should be no more EIO. If there is no audio hardware of any kind on the system being tested, the attempt top open /dev/mixer should fail, and the test will be skipped. |
||
---|---|---|
.. | ||
awk | ||
basename | ||
bzip2 | ||
cc | ||
cmp | ||
config | ||
cut | ||
diff | ||
dirname | ||
find | ||
gdb | ||
grep | ||
gzip | ||
id | ||
infocmp | ||
jot | ||
ld | ||
m4 | ||
make | ||
mixerctl | ||
mkdep | ||
nbperf | ||
netpgpverify | ||
pkill | ||
pr | ||
rump_server | ||
sdiff | ||
sed | ||
shmif_dumpbus | ||
sort | ||
tmux | ||
tr | ||
unifdef | ||
uniq | ||
vmstat | ||
xlint | ||
Makefile |