I'm getting these errors:
cx22702_writereg: error (reg == 0x0c, val == 0x40, ret == -6)
cx22702_writereg: error (reg == 0x00, val == 0x01, ret == -6)
cx22702_writereg: error (reg == 0x0d, val == 0x00, ret == -6)
cx22702_writereg: error (reg == 0x0d, val == 0x01, ret == -6)
cx22702_readreg:
Alan Stern wrote On 22-10-2009 17:05:
On Thu, 22 Oct 2009, [UTF-8] Ozan Çağlayan wrote:
Here's the outputs from /sys/kernel/debug/usb/ehci:
periodic:
size = 1024
1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8)
There's something odd about this. I'd like to
On Fri, Oct 23, 2009 at 12:10 AM, Hans Verkuil hverk...@xs4all.nl wrote:
The attach patch modifies v4l2-ctl -I to also output signal status as
detected by the driver/hardware. This info is available in the status
field of the data returned by VIDIOC_ENUMINPUT which v4l2-ctl -I
already calls.
Hi.
I have written a driver for the TI WL1273 FM Radio but it's not yet
quite ready for up-streaming because of its interface. Now I've started
to change the interface to v4l2 and I'm following Eduardo Valentin's
Si4713 TX driver as an example. However, WL1273 radio has RX and TX so
there are
Hi,
Here's the version 2.2 of the video events RFC. It's based on Laurent
Pinchart's original RFC and versions 2 and 2.1 which I wrote. The old
RFC is available here:
URL:http://www.spinics.net/lists/linux-media/msg11056.html
Added Mauro to Cc.
Changes to version 2.1
The variables are unsigned so the test `= 0' is always true,
the ` 0' test always fails. In these cases the other part of
the test catches wrapped values.
Signed-off-by: Roel Kluin roel.kl...@gmail.com
---
diff --git a/drivers/media/common/tuners/tda9887.c
b/drivers/media/common/tuners/tda9887.c
Attached patch changes v4l2-ctl -T so that the reported strength is
rounded to nearest integer rather than allways rounding down. With
this patch you get 100% when driver returns 0x.
Best regards
Sigmund Augdal
v4l2-ctl-signal-strength-rounding.diff
Description: Binary data
Hi Devin,
On Thu, 22 Oct 2009 15:27:20 -0400, Devin Heitmueller wrote:
On Thu, Oct 22, 2009 at 3:13 PM, Jean Delvare kh...@linux-fr.org wrote:
Hi folks,
I am looking for details regarding the DVB frontend API. I've read
linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
Hi Sakari,
On Fri, 2009-10-23 at 13:18 +0300, Sakari Ailus wrote:
Hi,
Here's the version 2.2 of the video events RFC. It's based on Laurent
Pinchart's original RFC and versions 2 and 2.1 which I wrote. The old
RFC is available here:
On Fri, Oct 23, 2009 at 9:35 AM, Sigmund Augdal sigm...@snap.tv wrote:
On Fri, Oct 23, 2009 at 12:10 AM, Hans Verkuil hverk...@xs4all.nl wrote:
The attach patch modifies v4l2-ctl -I to also output signal status as
detected by the driver/hardware. This info is available in the status
field of
On Fri, Oct 23, 2009 at 9:35 AM, Sigmund Augdal sigm...@snap.tv wrote:
On Fri, Oct 23, 2009 at 12:10 AM, Hans Verkuil hverk...@xs4all.nl wrote:
The attach patch modifies v4l2-ctl -I to also output signal status as
detected by the driver/hardware. This info is available in the status
field of
Hi,
My Nebula DigiTV DVB-T (PCI) card no longer works. It's on a
multi-boot Kubuntu system and works fine when I boot into Intrepid
(v2.6.27-11-generic#1 SMP i686), but it does not work with Jaunty
(2.6.28-11-generic i686). I've also tried a beta of the latest Kubuntu
release Karmic and that also
Op 23-10-09 12:59, Roel Kluin schreef:
The variables are unsigned so the test `= 0' is always true,
the ` 0' test always fails. In these cases the other part of
the test catches wrapped values.
Signed-off-by: Roel Kluin roel.kl...@gmail.com
---
I forgot the stats:
Hi everybody,
while working on device node support for subdevs I ran into an issue with the
way v4l2 objects are structured.
We currently have the following structure:
- video_device represents a device that complies with the V4L1 or V4L2 API.
Every video_device has a corresponding device
Nobody has an idea? I think this cpu load isn't normal, becuase everywhere
you can read, that the bealgeboard is very fast and it has 500MHz...
Regards, Joern
- Original Message -
From: Rath maili...@hardware-datenbank.de
To: Linux-Media linux-media@vger.kernel.org
Sent: Sunday,
Hi!
I found my old Pinnacle PCTV DVB-T card and thought I might put it to use.
Since I have used it on linux before (about two years ago) with the em28xx
driver I didn't think it would be any problems.
However I can't seem to get it to work.
I'm using Ubuntu Karmic and a uname -a yields:
Linux
On Fri, Oct 23, 2009 at 10:12 AM, m...@spanberg.se wrote:
Hi!
I found my old Pinnacle PCTV DVB-T card and thought I might put it to use.
Since I have used it on linux before (about two years ago) with the em28xx
driver I didn't think it would be any problems.
However I can't seem to get it
On Thu, 22 Oct 2009 21:13:30 +0200, Jean Delvare wrote:
For example, the signal strength. All I know so far is that this is a
16-bit value. But then what? Do greater values represent stronger
signal or weaker signal? Are 0x and 0x special values? Is the
returned value meaningful even
Hello,
I have a Pinnacle pctv 7010ix that is oddly recognized as a Pinnacle
PCTV 3010iX [1].
I found that the SAA7162 chip used in that device is supported while
the device itself is not. I was a bit confused wich of the various
repositories I encountered reflects the latest version of
On Fri, Oct 23, 2009 at 11:45 AM, Benjamin Valentin
benpi...@zedat.fu-berlin.de wrote:
Hello,
I have a Pinnacle pctv 7010ix that is oddly recognized as a Pinnacle
PCTV 3010iX [1].
I found that the SAA7162 chip used in that device is supported while
the device itself is not. I was a bit
On Fri, Oct 23, 2009 at 11:47 AM, Jean Delvare kh...@linux-fr.org wrote:
On Thu, 22 Oct 2009 21:13:30 +0200, Jean Delvare wrote:
For example, the signal strength. All I know so far is that this is a
16-bit value. But then what? Do greater values represent stronger
signal or weaker signal? Are
Kevin Hilman wrote:
santiago.nu...@ridgerun.com writes:
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides support for TVP7002 in architecture definitions
within DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
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 Oct 23 19:00:04 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 13156:f6680fa8e7ec
gcc version: gcc
I am an Ubuntu user. Since I switched to the new Karmic release with the
new kernel my TV card stopped working. Even explicitly setting the tuner
doesnt seem to work. Setting the options explicitly with saa7134
i2c_scan=1 card=49 tuner=5 and tuner no_autodetect=5 addr=0xc6 / 0x63
and any
On Thu, Oct 22, 2009 at 1:29 PM, Manu Abraham abraham.m...@gmail.com wrote:
Sometime back, (some time in April) i proposed a patch which addressed
the issue to scale even those devices which have a weird scale or
none. Though based on an older tree of mine, here is the patch again.
If it looks
Hans,
following IOCTLS :-
- verify the new v4l2_input capabilities flag added
- Enumerate available presets using VIDIOC_ENUM_DV_PRESETS
- Set one of the supported preset using VIDIOC_S_DV_PRESET
- Get current preset using VIDIOC_G_DV_PRESET
- Detect current preset using
On Fri, 23 Oct 2009, [UTF-8] Ozan ÃaÄlayan wrote:
There's something odd about this. I'd like to see this file again,
after the patch below has been applied.
periodic
size = 1024
1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8) t
On closer study and more careful thought,
On Fri, Oct 23, 2009 at 9:02 PM, VDR User user@gmail.com wrote:
On Thu, Oct 22, 2009 at 1:29 PM, Manu Abraham abraham.m...@gmail.com wrote:
Sometime back, (some time in April) i proposed a patch which addressed
the issue to scale even those devices which have a weird scale or
none. Though
On Wed, 21 Oct 2009, Valentin Longchamp wrote:
Sascha Hauer wrote:
On Mon, Oct 19, 2009 at 06:41:13PM +0200, Valentin Longchamp wrote:
Hi Guennadi,
Guennadi Liakhovetski wrote:
Hi
On Thu, 15 Oct 2009, Valentin Longchamp wrote:
We have two mt9t031 cameras that
29 matches
Mail list logo
