Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?

On 06/29/2010 07:54 AM, Jan Hoogenraad wrote: I see: apparently the versions earlier than V3.0 of CTVDIGRCU used Realtek RTL2831U. I'll make a note of that on the wiki page. Thank you; indeed I provided incomplete information (i forgot the v3.0 part). Is it possible to force the driver to tr

Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?

On 06/28/2010 09:48 PM, Jan Hoogenraad wrote: Matteo: If I read this well, CTVDIGUSB2 1b80:d393 (Afatech) is not at all similar to the CTVDIGRCU. The CTVDIGRCU has a Realtek RTL2831U decoder, and is NOT included in the standard dvb list. So is the table at http://linuxtv.org/wiki/index.php

v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?

device to the source code of the driver somewhere and recompiling it and it would work?? If so, is it something I may try following some step-by-step guide? Thanks m. -- Matteo Sisti Sette matteosistise...@gmail.com http://www.matteosistisette.com -- To unsubscribe from this list: send the line

Re: v4l-dvb bug report

sources to compile v4l-dvb, it does not mean that you're recompiling the kernel, does it? :$ Thanks m. 2010/6/27 Villy Thomsen : > Hi Matteo, > > I had the same problem a while ago. Short answer, the firedtv driver > needs full kernel source to compile. I think I ended up with t

v4l-dvb bug report

/v4l-dvb/v4l/firedtv-1394.c:288: error: implicit declaration of function 'hpsb_register_protocol' /home/teo/v4l-dvb/v4l/firedtv-1394.c:291: error: implicit declaration of function 'hpsb_unregister_highlevel' /home/teo/v4l-dvb/v4l/firedtv-1394.c: In function 'fdtv_1394_exi

Re: DVB-S2 Multistream (?)

/mailings/Product_updates/Multistream/Newtec-Customer-Case_Multistream_TelecomItaliaMediaBroadcasting_2010-02-25.pdf 2010/3/5 Matteo : > Hi, > > I have problems with some frequencies which I suppose are broadcasted > in DVB-S2 Multistream,  I think it's the same topic already discus

DVB-S2 Multistream (?)

I use a TechnoTrend S2-1600, and I was wondering if there is any plan to eventually support this feature (if it's not an hardware limitation). Thanks Matteo -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org

Re: pctv nanoStick Solo not recognized

Hi Patrick, here it is the requested patch... note that I don't have a PCTV282E device, so I cannot test it! Thanks for the assistance, Matteo On Tue, Oct 20, 2009 at 9:42 AM, Patrick Boettcher wrote: > Hi Matteo, > > Sorry for being quite in the first place. > > On Tue,

Re: pctv nanoStick Solo not recognized

Devin, it worked. I added the new vendor, and changed the other entry. I'm wondering if exists a "pinnacle" pctv 73e se usb device... attached to this mail there is the (easy) patch. Thank you very much! Matteo On Mon, Oct 19, 2009 at 11:56 PM, Devin Heitmueller wrote: > On

Re: pctv nanoStick Solo not recognized

e the 57th line to { USB_DEVICE(USB_VID_PINNACLE2, USB_PID_PINNACLE_PCTV73ESE) }, or should I do something else? Thank you again, Matteo On Mon, Oct 19, 2009 at 10:41 PM, Devin Heitmueller wrote: > On Mon, Oct 19, 2009 at 4:28 PM, Matteo Miraz > wrote: >> in the changeset 12886:ba

Re: pctv nanoStick Solo not recognized

, and try if the module works? I'm new to the kernel development, so I'm afraid to make mistakes! Thanks, Matteo On Mon, Oct 19, 2009 at 9:18 PM, Devin Heitmueller wrote: > On Sun, Oct 18, 2009 at 5:41 PM, Matteo Miraz > wrote: >> Hi, >> >> I've just bought a

pctv nanoStick Solo not recognized

chip seems to be a "73E SE". Looking at the lsusb output (reported below), it seems that it is not a pinnacle, but a new brand (the Vendor ID is different from the pinnacle's one). Can you help me? Thanks, Matteo --- lsusb output: Bus 001 Device 011: ID 2013:0245 Device D