First ever crack at creating docbook documentation... Contains a bevy of
information on the various lirc device interface ioctls, as well as a
bit about the read and write interfaces.
Forgot about this in 0/3, so this is patch 4/3. Oops.
Signed-off-by: Jarod Wilson
---
.../DocBook/v4l/lirc_devi
v2: No changes from prior submission here.
Signed-off-by: Jarod Wilson
---
drivers/media/IR/keymaps/Makefile |1 +
drivers/media/IR/keymaps/rc-lirc.c | 41
include/media/rc-map.h |1 +
3 files changed, 43 insertions(+), 0 deletions(-)
v2: copy of buffer data from userspace done inside this plugin/driver,
keeping the actual drivers minimal, and more flexible in what we can
deliver to them later on (they may be fed from within kernelspace later
on, by an in-kernel IR encoder).
Signed-off-by: Jarod Wilson
---
drivers/media/IR/Kc
v2: currently unused ioctls are included, but #if 0'd out
Signed-off-by: Jarod Wilson
---
drivers/media/IR/Kconfig| 11 +
drivers/media/IR/Makefile |1 +
drivers/media/IR/lirc_dev.c | 761 +++
drivers/media/IR/lirc_dev.h | 226 +
On Tue, Jun 01, 2010 at 04:50:05PM -0400, Jarod Wilson wrote:
> This patch series adds the core lirc device interface, lirc_dev, and
> an ir-core bridge driver. Currently, only the receive side is wired
> up in the bridge driver, but adding transmit support is up next.
>
> Currently, adding this c
I have pinnacle hardware now. None of this pinnacle-specific crap is at
all necessary (in fact, some of it needed to be removed to actually make
it work). The only thing unique about this device is that it often
transfers inbound data w/a header of 0x90, meaning 16 bytes of IR data
following it, so
On Fri, Jun 4, 2010 at 2:38 PM, Mauro Carvalho Chehab
wrote:
...
> From my side, as I said before, I'd like to see a documentation of the
> defined API bits,
> and the removal of the currently unused ioctls (they can be added later,
> together
> with the patches that will introduce the code that
I'm confused as to what firmware in needed for the HVR-1110.
Scouring the web, everywhere claims that the dvb-fe-tda10046 is
required; however, dmesg logs show that this fails to be uploaded, and
instead it is looking for dvb-fe-tda-10048:
If I use tda-10048 then this seems to successfully loaded
This function is declared extern and exported, and should not be given
a generic name which may conflict with gpiolib in future.
Signed-off-by: Ben Hutchings
---
drivers/media/dvb/mantis/hopper_vp3028.c |4 ++--
drivers/media/dvb/mantis/mantis_core.c |2 +-
drivers/media/dvb/mantis/man
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Fri Jul 2 19:00:18 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14993:9652f85e688a
git master:
There's a problem with the tvtime application that affects recent v4l2
drivers. The tvtime application works fine the first time you run it,
but the second time tvtime is run, the call to VIDIOC_REQBUFS fails with
EBUSY.
The problem is that tvtime does a VIDIOC_STREAMOFF, then VIDIOC_QBUF a
few
Am Freitag, 2. Juli 2010, um 02:59:57 schrieb Douglas Schilling Landgraf:
> humm, not really :-/ Are you sure em28xx/device get loaded when your
> device is plugged?
>
> A good test:
>
> - unplug your device
> - dmesg -c (clear the dmesg)
> - plug your device
> - check your dmesg, see if there i
Adds support for Video-In (VIU) unit of Freescale
MPC5121e. The driver supports RGB888/RGB565 formats,
capture and overlay on MPC5121e DIU frame buffer.
Signed-off-by: Hongjun Chen
Signed-off-by: Anatolij Gustschin
---
Please review and consider for inclusion in 2.6.36. Thanks!
Changes since fi
Hi,
i tried tuning to a channel that has a SR < 1 Msps in DVB-S with szap and I get
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_SET_FRONTEND failed: Invalid argument
is there any limit in driver that doesn't allow my TT S2-3200 to try to tune
into that tranponder?
I k
"Dirk Langner" writes:
> I'm really pissed that whenever I try to find a TV-USB-stick (analog
> in my case), it's not in the shops any longer or it's not listed on
> the linuxtv validated sticks. The names of the USB sticks are only
> slightly changed, which may mean, this is only a rebranding or
Hi,
I recently got an TechniSat SkyStar S2 [13d0:2103] which uses an
FlexCop2-Bridge, which is supported, but an unsupported? CX24120 Demod.
(This card is rather cheap, 45€ LowProfile incl. IR-Remote, otherwise i'd
just have sent it back.)
TechniSat provides a Binary Driver
(
http://www.te
Hi Samuel,
On Friday 25 June 2010 12:01:42 Samuel Xu wrote:
> One correction: After make and make install, uvcvideo module can't
> auto loaded any more. I must manually "insmod uvcvideo.ko" to load it.
>
> Here is lsmod result, I never have chance to make uvcvideo module used
> bit to 1 :(
> [r..
Hi Samuel,
On Tuesday 29 June 2010 12:12:13 Samuel Xu wrote:
> Question on uvcvideo driver's power management:
> Q1: We found some USB material mentioned : Relationship between ACPI
> Dx states and USB PM states (active/suspended) is orthogonal.
> Suspend/resume might not effect device Dx state(e.
Hi,
I'm really pissed that whenever I try to find a TV-USB-stick (analog in my
case), it's not in the shops any longer or it's not listed on the linuxtv
validated sticks. The names of the USB sticks are only slightly changed, which
may mean, this is only a rebranding or a completely new hardwa
On Wed, 2010-06-30 at 23:11 +0200, Johannes Berg wrote:
> I'm pretty sure this was a regression in .34, but haven't checked right
> now, can bisect when I find time but wanted to inquire first if somebody
> had ideas. All I get is:
>
> [57372.078968] uvcvideo: Failed to query (130) UVC control 5 (
Hi,
We have/in process of developing a V4L2 driver for the FM Radio on the Texas
Instruments WiLink 7 module.
For transport/communication with the chip, we intend to use the shared
transport driver currently staged in mainline at drivers/staging/ti-st/.
To which tree should I generate patches
21 matches
Mail list logo
