Hi, I was just wondering if anyone could tell me is this card works
for analog TV (NTSC, PAL). I see from this page it says something
about analog not supported which doesn't seem right. What does this
really mean?
It is supported under Linux since kernel 2.6.27. (Note: Analog support
is not i
On Jan 15, 2011, at 12:37 AM, Jarod Wilson wrote:
> On Jan 14, 2011, at 11:35 PM, Andy Walls wrote:
>
>> On Fri, 2011-01-14 at 21:30 -0500, Jarod Wilson wrote:
>>> On Jan 14, 2011, at 5:08 PM, Jarod Wilson wrote:
>>
>> Registered IR keymap rc-hauppauge-new
>> input: i2c IR (HD PVR) as /d
On Jan 15, 2011, at 12:37 AM, Jarod Wilson wrote:
...
>> BTW, a checkpatch and compiler tested lirc_zilog.c is here:
>>
>> http://git.linuxtv.org/awalls/media_tree.git?a=shortlog;h=refs/heads/z8
>>
>> It should fix all the binding and allocation problems related to
>> ir_probe()/ir_remove(). Exc
On Jan 14, 2011, at 11:35 PM, Andy Walls wrote:
> On Fri, 2011-01-14 at 21:30 -0500, Jarod Wilson wrote:
>> On Jan 14, 2011, at 5:08 PM, Jarod Wilson wrote:
>
> Registered IR keymap rc-hauppauge-new
> input: i2c IR (HD PVR) as /devices/virtual/rc/rc1/input6
> rc1: i2c IR (HD PVR) as /
Hello I am running the following OS "Ubuntu 10.04.1 LTS"
with Mythtv I have a WinTv HVR-980 and hvae no sound with
video see errors below any assistance would be appreciated.
I should have a /dev/dsp1 but I can not find it?
[ 28.349674] em28xx #0: Config register raw data: 0xd0
[ 28.350444
On Fri, 2011-01-14 at 21:30 -0500, Jarod Wilson wrote:
> On Jan 14, 2011, at 5:08 PM, Jarod Wilson wrote:
> >>> Registered IR keymap rc-hauppauge-new
> >>> input: i2c IR (HD PVR) as /devices/virtual/rc/rc1/input6
> >>> rc1: i2c IR (HD PVR) as /devices/virtual/rc/rc1
> >>> ir-kbd-i2c: i2c IR (HD PV
On Jan 14, 2011, at 5:08 PM, Jarod Wilson wrote:
> On Fri, Jan 14, 2011 at 04:44:40PM -0500, Andy Walls wrote:
>> On Fri, 2011-01-14 at 14:54 -0500, Jarod Wilson wrote:
>>> A number of things going on here, but the end result is that the IR part
>>> on the hdpvr gets enabled, and can be used with
Hans,
A few weeks ago you asked if VIDIOC_INT_RESET is still needed in ivtv.
I can now say for certain, that yes, it is still needed.
See this from 2008:
http://www.mail-archive.com/ivtv-users@ivtvdriver.org/msg08613.html
It will not be needed after I get two things done:
1. patch ivtv to issu
On Fri, Jan 14, 2011 at 04:44:40PM -0500, Andy Walls wrote:
> On Fri, 2011-01-14 at 14:54 -0500, Jarod Wilson wrote:
> > A number of things going on here, but the end result is that the IR part
> > on the hdpvr gets enabled, and can be used with ir-kbd-i2c and/or
> > lirc_zilog.
> >
> > First up,
Add a hex dump of the received bytes for tester reporting of actual data
received from the hardware.
Signed-off-by: Andy Walls
---
My heart won't be broken if this never makes it into the kernel.
Regards,
Andy
diff --git a/drivers/media/video/ir-kbd-i2c.c b/drivers/media/video/ir-kbd-i2c.c
ind
On Fri, 2011-01-14 at 14:54 -0500, Jarod Wilson wrote:
> A number of things going on here, but the end result is that the IR part
> on the hdpvr gets enabled, and can be used with ir-kbd-i2c and/or
> lirc_zilog.
>
> First up, there are some conditional build fixes that come into play
> whether i2c
On Fri, 14 Jan 2011 16:08:38 -0500, Jarod Wilson wrote:
> The current hdpvr code kmalloc's a new buffer for every i2c read and
> write. Rather than do that, lets allocate a buffer in the driver's
> device struct and just use that every time.
>
> The size I've chosen for the buffer is the maximum s
The current hdpvr code kmalloc's a new buffer for every i2c read and
write. Rather than do that, lets allocate a buffer in the driver's
device struct and just use that every time.
The size I've chosen for the buffer is the maximum size I could
ascertain might be used by either ir-kbd-i2c or lirc_z
On Fri, Jan 14, 2011 at 09:35:24PM +0100, Jean Delvare wrote:
> Hi Jarod,
>
> On Fri, 14 Jan 2011 15:01:09 -0500, Jarod Wilson wrote:
> > The current hdpvr code kmalloc's a new buffer for every i2c read and
> > write. Rather than do that, lets allocate a buffer in the driver's
> > device struct an
Add a 10 bits per pixel greyscale format in a packed array representation,
naming it Y10P. Such pixel format is supplied for instance by the Kinect
sensor device.
Signed-off-by: Antonio Ospite
---
Hi, this version should look better than the previous one.
It's not marked as RFC anymore, is it in
Hi Jarod,
On Fri, 14 Jan 2011 15:01:09 -0500, Jarod Wilson wrote:
> The current hdpvr code kmalloc's a new buffer for every i2c read and
> write. Rather than do that, lets allocate a buffer in the driver's
> device struct and just use that every time.
>
> The size I've chosen for the buffer is th
The current hdpvr code kmalloc's a new buffer for every i2c read and
write. Rather than do that, lets allocate a buffer in the driver's
device struct and just use that every time.
The size I've chosen for the buffer is the maximum size I could
ascertain might be used by either ir-kbd-i2c or lirc_z
Alfredo Braunstein wrote:
> Hi & happy new year,
>
> I recently bought a Pinnacle 72e USB stick, (lsusb says: Bus 002
> Device 011: ID 2304:0236 Pinnacle Systems, Inc. [hex]. The stick says
> "pinnacle" on front
> and "72e" and "1100" on the back) which seemed to be supported by the
> dvb_usb_dib
A number of things going on here, but the end result is that the IR part
on the hdpvr gets enabled, and can be used with ir-kbd-i2c and/or
lirc_zilog.
First up, there are some conditional build fixes that come into play
whether i2c is built-in or modular. Second, we're swapping out
i2c_new_probed_
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 Jan 14 19:00:49 CET 2011
git master: 59365d136d205cc20fe666ca7f89b1c5001b0d5a
git media-master: gcc version: i6
Hi Hans,
here is second version of plugin support for libv4l2.
Changes in v2:
* Remove calls of v4l2_plugin_foo functions in the beginning of coresponding
v4l2_foo functions and instead replace SYS_FOO calls.
* Add to v4l2_dev_info device operation structure which can hold plugin
callbacks or
A libv4l2 plugin will sit in between libv4l2 itself and the
actual /dev/video device node a fd refers to. It will be called each time
libv4l2 wants to do an operation (read/write/ioctl/mmap/munmap) on the
actual /dev/video node in question.
Signed-off-by: Yordan Kamenov
---
lib/include/libv4l2-p
Hi again,
On Wed, 12 Jan 2011, Mauro Carvalho Chehab wrote:
Em 12-01-2011 11:17, Robin Humble escreveu:
Hi,
this is basically a re-post of
http://www.linuxtv.org/pipermail/linux-dvb/2010-September/032744.html
which fixes an Oops when tuning eg. AVerMedia DVB-T Volar, Hauppauge
Nova-T, Winfa
Hi Enric,
On Thursday 13 January 2011 13:27:43 Enric Balletbò i Serra wrote:
> 2011/1/12 Laurent Pinchart :
> > On Wednesday 12 January 2011 12:58:04 Enric Balletbò i Serra wrote:
> >> Hi all,
> >>
> >> As explained in my first mail I would like port the tvp515x driver to
> >> new media framework
> -Original Message-
> From: Andreas Oberritter [mailto:o...@linuxtv.org]
> Sent: Friday, January 14, 2011 5:32 PM
> Albeit, DVB-SI data isn't perfect and misconfiguration at the
> transmitter happens (e.g. wrong FEC values), especially where most of
> the parameters are signaled in-band
On 01/14/2011 04:12 PM, Devin Heitmueller wrote:
> On Fri, Jan 14, 2011 at 8:35 AM, Thierry LELEGARD
> wrote:
>> But there is worse. If I set a wrong parameter in the tuning operation,
>> for instance guard interval 1/32, the API V3 returns the correct value
>> which is actually used by the tuner
Radek,
Please attach the full dmesg output when starting video capture with
the second camera.
Also increase log verbosity first:
something like this:
rmmod uvcvideo
modprobe uvcvideo trace=65535
You should also refer your capture settings (if I remember MJPG
640x480@24 fps) and that if you use o
Hi Laurent,
My apologies that this reply is so late, but I knew I had to sit down and think
carefully about this and I didn't have time for that until today.
I've decided not to quote your post but instead restate the problem in my own
words.
Seen abstractly you have an entity with inputs, outpu
Hi Mauro,
if it is not too late, here is a pull request for some new devices from
DiBcom. It would be nice to have it in 2.6.38-rc1.
Pull from
git://linuxtv.org/pb/media_tree.git staging/for_2.6.38-rc1.dibcom
for
DiB: Codingstype updates
DiB0700: add support for several board-layouts
Di
Hi,
On Wed, 12 Jan 2011, Robin Humble wrote:
Ubuntu has a bug open for the issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/654791
but the disable pid filtering workaround one person uses there doesn't
work for me.
Sorry for the delay, but I only realized today that this bug exists
On Fri, Jan 14, 2011 at 8:35 AM, Thierry LELEGARD
wrote:
> But there is worse. If I set a wrong parameter in the tuning operation,
> for instance guard interval 1/32, the API V3 returns the correct value
> which is actually used by the tuner (GUARD_INTERVAL_1_8), while S2API
> returns the "cached"
Hello Thierry,
On 01/14/2011 02:35 PM, Thierry LELEGARD wrote:
> Dear all,
>
> I would like to report an annoying behavior difference between S2API and the
> legacy DVB API (V3) when _reading_ the current tuning configuration.
>
> In short, API V3 is able to report the _actual_ tuning parameters
On Thu, 13 Jan 2011 17:30:21 +0100
Jean-Francois Moine wrote:
> On Thu, 13 Jan 2011 12:38:04 +0100
> Antonio Ospite wrote:
>
> > > Jean-François Moine (9):
> > [...]
> > > gspca - ov534: Use the new video control mechanism
> >
> > In this commit, is there a reason why you didn't rena
Dear all,
I would like to report an annoying behavior difference between S2API and the
legacy DVB API (V3) when _reading_ the current tuning configuration.
In short, API V3 is able to report the _actual_ tuning parameters as used by
the driver and corresponding to the actual broadcast steam. On t
This patch implements tables for display timings,outputs and
other board related functionalities.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan Karicheri
Acked-by: Hans Verkuil
---
arch/arm/mach-davinci/board-dm644x-evm.c | 84 -
1 files changed, 69 insert
Please refer to this file for detailed documentation of
davinci vpbe v4l2 driver.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan Karicheri
Acked-by: Hans Verkuil
---
Documentation/video4linux/README.davinci-vpbe | 93 +
1 files changed, 93 insertions(+), 0 dele
version14 : addressed Shekhar's comments
on:
1. Implemetation of single io_remap of system module base address
2. Minor changes in the GPL comments
cover letter addition:
Need the 6 main driver patches for DM6446 VPBE v4l2 driver for build.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan K
This patch implements the overall device creation for the Video
display driver.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan Karicheri
Acked-by: Hans Verkuil
---
arch/arm/mach-davinci/devices.c | 11 +-
arch/arm/mach-davinci/dm355.c |3 +
arch/arm/m
This patch adds the build infra-structure for Davinci
VPBE dislay driver.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan Karicheri
Acked-by: Hans Verkuil
---
drivers/media/video/davinci/Kconfig | 22 ++
drivers/media/video/davinci/Makefile |2 ++
2 files chang
This patch implements the functionality of the OSD block
of the VPBE. The OSD in total supports 4 planes or Video
sources - 2 mainly RGB and 2 Video. The patch implements general
handling of all the planes, with specific emphasis on the Video
plane capabilities as the Video planes are supported thr
This patch adds the VENC or the Video encoder, which is responsible
for the blending of all source planes and timing generation for Video
modes like NTSC, PAL and other digital outputs. the VENC implementation
currently supports COMPOSITE and COMPONENT outputs and NTSC and PAL
resolutions through t
This patch implements the core functionality of the dislay driver,
mainly controlling the VENC and other encoders, and acting as
the one point interface for the main V4L2 driver. This implements
the core of each of the V4L2 IOCTLs.
Signed-off-by: Manjunath Hadli
Acked-by: Muralidharan Karicheri
$ cat /proc/version_signature
Ubuntu 2.6.32-26.47-generic 2.6.32.24+drm33.11
Building from git:
$ cd ~/git/clones/v4l-dvb
$ git log -1
commit aeb13b434d0953050306435cd3134d65547dbcf4
Author: Mauro Carvalho Chehab
Date: Wed Jan 5 13:31:15 2011 -0200
cx25821: Fix compilation breakage due to
On 1/13/11, Mauro Carvalho Chehab wrote:
>> This seems to be a relatively simple patch, inline below.
>> This is against the linux-media tree, I could not figure out how
>> to turn it into a clean patch of
>> media_build/backports/v2.6.35_i2c_new_probed_device.patch
>> I did look for guidance on
I added my comments.
I guess that Kamil's way could be possible to run seq. of dynamic resolution
change.
> -Original Message-
> From: Jonghun Han [mailto:jonghun@samsung.com]
> Sent: Friday, January 14, 2011 6:45 PM
> To: 'Kamil Debski'; linux-media@vger.kernel.org; linux-samsung-
> s
Hi,
I was confused the source and destination.
I agree with you mostly.
In my opinion, the way how to notify the resolution change is return value
of the DQBUF.
But if we use DQBUF, there are some problem as below.
DQBUF means that the buffer has been operated already and application will
have
Hi,
On 01/13/2011 11:05 PM, Jesper Juhl wrote:
usb_altnum_to_altsetting() may return NULL. If it does we'll dereference a
NULL pointer in
drivers/media/video/gspca/stv06xx/stv06xx_pb0100.c::pb0100_start().
As far as I can tell there's not really anything more sensible than
-ENODEV that we can re
47 matches
Mail list logo
