[linux-dvb] Re: Problem: dib7000m don't know my vendor

2006-10-18 Thread Christian Timmer
Am Mittwoch, den 18.10.2006, 09:39 +0200 schrieb Patrick Boettcher: Hi, On Tue, 17 Oct 2006, Christian Timmer wrote: Am Dienstag, den 17.10.2006, 14:54 +0200 schrieb Patrick Boettcher: Hi, in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed a first working

Re: [linux-dvb] Re: Problem: dib7000m don't know my vendor

2006-10-18 Thread Christian Timmer
Hi Patrick, I've just give it a try with your latest commitments. [17180201.616000] usb 4-2: new high speed USB device using ehci_hcd and address 3 [17180201.748000] usb 4-2: configuration #1 chosen from 1 choice [17180201.952000] dvb_usb_dib0700: Unknown symbol dib7000p_get_i2c_master

Re: [linux-dvb] Re: Problem: dib7000m don't know my vendor

2006-10-18 Thread Christian Timmer
Am Mittwoch, den 18.10.2006, 17:52 +0200 schrieb Patrick Boettcher: On Wed, 18 Oct 2006, Christian Timmer wrote: Hi Patrick, I've just give it a try with your latest commitments. [17180201.616000] usb 4-2: new high speed USB device using ehci_hcd and address 3 [17180201.748000

[linux-dvb] Problem: dib7000m don't know my vendor

2006-10-17 Thread Christian Timmer
Am Dienstag, den 17.10.2006, 14:54 +0200 schrieb Patrick Boettcher: Hi, in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed a first working version of the dib7000m/p-driver along with some modifications in the dib0700-driver. I tested with a first generation Nova-T stick

[linux-dvb] dib0700 with hauppauge wintv nova t usb2

2006-10-12 Thread Christian Timmer
dvb_usb_device_init Thanks! Christian Timmer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] dib0700 with hauppauge wintv nova t usb2

2006-10-12 Thread Christian Timmer
Am Donnerstag, den 12.10.2006, 09:01 -0400 schrieb Michael Krufky: Patrick Boettcher wrote: On Thu, 12 Oct 2006, [EMAIL PROTECTED] wrote: Today there is a new problem. I updated with mercury v4l-dvb and now that's what the kernel-log say's if I plug in the device: You probably mixed