path: root/v4l-utils.spec.in
AgeCommit message (Collapse)AuthorFilesLines
2016-07-13ir-ctl: add new tool for sending & receiving raw IRSean Young1-2/+4
Currently v4l-utils has no tooling provided for receiving and sending raw IR using the lirc interface. Some of this can be done using various tools from the user-space lirc package, but not everything is covered. We want to be able to do the following: - List all the features that a lirc device provides - Set all possible receiving and sending parameters - Send raw IR, formatted as a text file - Record raw IR, with output in the same format as for sending - Testbed for lirc drivers. Driver misbehaviour is reported The need for this is not new. The manufacturer of the IguanaWorks IR device have a similar tool which is IguanaIR specific: http://www.iguanaworks.net/2012/igclient-examples/ Also RedRat3 provide a similar tools but this uses a signal database for sending IR, and is redrat specific. http://www.redrat.co.uk/software/redrat-linux-ir-tools/ Lirc provides a tool for reading raw IR but no method of sending it. http://www.lirc.org/html/mode2.html None of these provides full coverage of the basic raw IR lirc interface, hence v4l-utils seems like logical place to provide this functionality. It can be used as a tool for testing features of lirc drivers. Signed-off-by: Sean Young <sean@mess.org>
2014-01-14libv4l: Update the README name for libv4lLad, Prabhakar1-1/+1
The README for libv4l was renamed from README.lib to README.libv4l but the reference to it was not fixed. This patch fixes the above. Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com> Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2012-01-14buildsystem: Convert to autotools buildsystemGregor Jasny1-1/+1
Use autoreconf -vfi to bootstrap Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
2011-10-07Add support to disable libv4l and/or v4l-utilsMauro Carvalho Chehab1-0/+167
Add some autogen magic to allow disabling the compilation of v4l-utils or libv4l. If libv4l is disabled but v4l-utils is enabled, it will still build libv4l statically, and will linkedit the v4l-utils against the static libraries. This way distributions can ship v4l-utils on a separate package from libv4l, and even having things like providing a v4l-utils based on a different version of libv4l. This changeset also opens space to add more libraries and other packages, as the first step to turn it into a media-utils tree. While here, adds a v4l-utils.spec rpm file, as found on Fedora. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

Privacy Policy