Having a SRC_URI called ${PN} is asking for trouble. When extending FILESPATH,
alsa-state can be treated as a directory and copied over the contents of ${WORKDIR}
which is invariably not what the user wants.
Avoid this by renaming the SRC_URI to something else and only call
it alsa-state at install time.
(From OE-Core rev: 04c73333e4b539de96f096ca2954b2313175edc4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
An empty asound.conf should work for most cases. The existing asound.conf
uses plug dmix which causes arecord to fail without a special -D device
specification on the command line (as no capture device is defined).
Clear asound.conf for the default case. Any needed changes should be
made in the BSP layers.
(From OE-Core rev: 736b0da53b3b38224ae3cb6f0ebd21da7fb04f4d)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
alsactl creates the state files in /var/lib/alsa by default so switch
alsa-state to use files in that location.
Further, update the alsa-state init script to have the location of the
state files sed'ed into the script at do_install time (so as to remove
hard coding of directory paths).
(From OE-Core rev: 896924c72e7b37c18819229e8160c34cdf4465c8)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
alsa-state adds an init script and configuration files to enable a
consistent and centralised mechanism for setting and restoring alsa
configuration.
(From OE-Core rev: 8bc43c40cf72d5543924229146fa4106ad87b147)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie
Darren Hart
Joshua Lock