Hello
I have managed to attach the device without any error messages now but the
tuning and playback of DVB still doesn't work. I get a lot of these error
messages:
[ 247.268152] em28xx #0: reading i2c device failed (error=-110)
[ 247.268161] xc2028 1-0061: i2c input error: rc = -110 (should
On Fri, Nov 13, 2009 at 4:37 PM, Lauri Laanmets
lauri.laanm...@proekspert.ee wrote:
Hello
I have managed to attach the device without any error messages now but the
tuning and playback of DVB still doesn't work. I get a lot of these error
messages:
[ 247.268152] em28xx #0: reading i2c
em28xx: fix for Leadtek winfast tv usbii deluxe
From: Magnus Alm magnus@gmail.com
This patch adds working:
Video and Sound for Television, Svideo and Composite.
Radio.
Stereo.
Also ir-remote for kernel 2.6.30 and higher.
Priority: high
diff -r 19c0469c02c3
Hi
Sorry if I wasn't clear enough. I'm trying to get V4l code working. So I'm
playing around with GPIO's and have managed to get the I2C communication
working but something is still missing. I was thinking that because mcentral
code worked, maybe some information can be taken over from it but
Dear Guennadi
Thank you for checking patch
+ ret = i2c_smbus_write_byte_data(client, OUTCTR1,
+ VSP_LO | VSSL_VVALID |
+ HSP_LO | HSSL_DVALID);
now you dropped VSP_LO | HSP_LO, could you, please, explain, why?
On Fri, 13 Nov 2009, Kuninori Morimoto wrote:
Dear Guennadi
Thank you for checking patch
+ ret = i2c_smbus_write_byte_data(client, OUTCTR1,
+ VSP_LO | VSSL_VVALID |
+ HSP_LO | HSSL_DVALID);
now you dropped
Stefan Richter wrote on 2009-10-17:
Since 2.6.32(-rc1), DVB core checks the return value of
dvb_frontend_ops.set_frontend. Now it becomes apparent that firedtv
always returned a bogus value from its set_frontend method.
Signed-off-by: Stefan Richter stef...@s5r6.in-berlin.de
Hi Mauro,
Stefan Richter wrote:
...the firedtv-avc.c part of the patch vanished when you committed it.
It was still there in the linuxtv-commits message of the respective
Mercurial commit, BTW. Something wrong with the hg to git workflow?
--
Stefan Richter
-=-==--= =-== -==-=
http://arcgraph.de/sr/
Hi!
If this is the right place, I can as well try to describe it now.
(And I hope I makes sense.)
The bug is about the Enable/Disable signal detection.
As it is now in videoinput.c:
int videoinput_check_for_signal( videoinput_t *vidin, int check_freq_present )
{
if(
Hi,
IMO, querystd() should make use of the auto mode to detect the current
standard and is internal to the driver how it achieves that. Also I agree
that locking the standard while streaming is ongoing and reverting back
to auto mode when it stops is okay based on the use cases that I have
come
On Fri, Nov 13, 2009 at 9:43 AM, Magnus Alm magnus@gmail.com wrote:
Hi!
If this is the right place, I can as well try to describe it now.
(And I hope I makes sense.)
The bug is about the Enable/Disable signal detection.
As it is now in videoinput.c:
int videoinput_check_for_signal(
Em Wed, 11 Nov 2009 18:59:09 +0100
Hans Verkuil hverk...@xs4all.nl escreveu:
On Wednesday 11 November 2009 18:29:52 Sakari Ailus wrote:
Hans Verkuil wrote:
On Saturday 24 October 2009 23:56:24 Sakari Ailus wrote:
Ivan T. Ivanov wrote:
Hi Sakari,
Hi,
On Fri, 2009-10-23 at
Em Wed, 11 Nov 2009 18:59:09 +0100
Hans Verkuil hverk...@xs4all.nl escreveu:
On Wednesday 11 November 2009 18:29:52 Sakari Ailus wrote:
Hans Verkuil wrote:
On Saturday 24 October 2009 23:56:24 Sakari Ailus wrote:
Ivan T. Ivanov wrote:
Hi Sakari,
Hi,
On Fri, 2009-10-23 at
Hi Devin,
I'm sorry. I just realized that I was only subscribed to linux-dvb but
not to linux-media. I fixed that now but my reply to your emails will
not have the correct In-Reply-To/References headers.
I have to wonder if maybe we are simply using the wrong tool for the
job. Perhaps it
On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad
jan-conceptro...@hoogenraad.net wrote:
Would it be possible to store this information in the CODE archives, and
extract it from there ?
Right now, I end up putting essentially the same information into structures
in the driver and into
Would it be possible to store this information in the CODE archives, and
extract it from there ?
Right now, I end up putting essentially the same information into
structures in the driver and into documentation.
This is hard to keep synchronised.
Basic information like device IDs, vendors,
I recently updated my play/work/fiddle with workstation and I wanted
to see if my USB card still worked (OK, it never really worked).
Previously, I was running Ubuntu 9.04 with a version retrieved from
mercurial with the patch from
http://linuxtv.org/hg/~mkrufky/teledongle/raw-rev/676e2f4475ed.
On 11/13/2009 8:00 AM, Hans Verkuil wrote:
Em Wed, 11 Nov 2009 18:59:09 +0100
Hans Verkuilhverk...@xs4all.nl escreveu:
On Wednesday 11 November 2009 18:29:52 Sakari Ailus wrote:
Hans Verkuil wrote:
On Saturday 24 October 2009 23:56:24 Sakari Ailus wrote:
Mauro Carvalho Chehab wrote:
[clip]
Hi Sakari,
What is that status of the event API? It is my impression that it is pretty
much finished. Sakari, can you make a final 2.3 RFC? Then Guru can take over
and start the implementation.
Ah.
One thing that I was still wondering was that are there use
On Fri, Nov 13, 2009 at 11:45:07AM -0500, Devin Heitmueller wrote:
On Fri, Nov 13, 2009 at 11:38 AM, Jan Hoogenraad
jan-conceptro...@hoogenraad.net wrote:
Would it be possible to store this information in the CODE archives, and
extract it from there ?
Right now, I end up putting
Hi,
I have downloaded the tree for Documentation and Applications and started first
building documentation.
make media-spec
It seems to build. What output it creates? Do I edit one of the xml file
to add the documentation? After adding the documentation, I guess I need
to build again and
Eino-Ville Talvala wrote:
I think we have a use case for events that would require correlating
with frames, although I agree that the buffer index would be far simpler
to match with than a timestamp. The specific feature is letting the
application know exactly what sensor settings were used
On Fri, Nov 13, 2009 at 1:01 PM, Devin Heitmueller
dheitmuel...@kernellabs.com wrote:
On Fri, Nov 13, 2009 at 12:01 PM, James Klaas
jkl...@appalachian.dyndns.org wrote:
I recently updated my play/work/fiddle with workstation and I wanted
to see if my USB card still worked (OK, it never really
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 Nov 13 19:00:04 CET 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 13328:aba823ecaea6
gcc version: gcc
2009/11/13 Nicolau Werneck nwern...@gmail.com:
Hello.
I bought me a new webcam. lsusb said me it was a 17a1:0128 device, for
which the gspca_t613 module is available. But it did not recognize the
sensor number, 0x0802.
I fiddled with the driver source code, and just made it recognize it
as
I have four of them and they work perfectly, but not out of the box from
the v4l-dvb tree. If it's patched with the patches posted on this list a
few weeks ago by Andreas Regel (or used with his repo at
http://powarman.dyndns.org/hg/v4l-dvb) it locks perfectly on every
transonder on 1.0W,
Hi!
Am Freitag, den 13.11.2009, 12:23 +0200 schrieb rul...@meta.ua:
Here is dmesg of analog (only analog, with FM-tuner) AverMedia Super 007
when tvtime is running:
[snip]
[ 11.549190] Linux video capture interface: v2.00
[ 12.409456] saa7130/34: v4l2 driver version 0.2.15 loaded
[
On Fri, Nov 13, 2009 at 09:04:23PM +0100, Erik Andrén wrote:
2009/11/13 Nicolau Werneck nwern...@gmail.com:
Hello.
I bought me a new webcam. lsusb said me it was a 17a1:0128 device, for
which the gspca_t613 module is available. But it did not recognize the
sensor number, 0x0802.
I
Mauro,
Please pull from http://jusst.de/hg/v4l-dvb for the following
changeset: 13339:b8eb9e860545
changeset: 13338:bababbc9ddfc
changeset: 13337:27db3dcc12a9
changeset: 13336:3f3113d2ead1
changeset: 13335:e9b90fb35417
changeset: 13334:4e9c155206ba
changeset: 1:ac7ac94ccbd2
29 matches
Mail list logo
