| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
An Qt OpenGL/OpenGL ES video viewer that can read from video nodes,
raw files, stream from the network and generate video using the
test pattern generator.
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Co-Developed-by: Bård Eirik Winther <bwinther@cisco.com>
Signed-off-by: Bård Eirik Winther <bwinther@cisco.com>
|
|
Add a few BPF protocols and infrastructure for building them.
Signed-off-by: Sean Young <sean@mess.org>
|
|
We use a modified version of samples/bpf/bpf_load.c from the linux kernel
tree to load elf based BPF protocols and display the BPF program names.
Any global int variables can be overrided from the command line. The
immediate values are patched in the BPF LD instructions.
Write a BPF protocol decoder in C, and compile with:
clang -O2 -c --target=bpf foo.c
Now you can load the object file like so:
ir-keytable -p foo.o -v
Any parameters can be specified using -e name=value.
Signed-off-by: Sean Young <sean@mess.org>
|
|
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>
|
|
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>
|
|
Use autoreconf -vfi to bootstrap
Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
|
|
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>
|
