Re: [linux-dvb] VHF tuning broken for TDA8275A cards?
Il Friday 21 December 2007 00:35:20 hai scritto: > Hi Nico, > > > You likely noticed some reports, that on VHF some transmitters > changed from FEC 3/4 to 2/3 recently. If not already done, it might > be worth a try creating a new channels.conf. > > Let me know, if you like to see some mplayer or other logs. > > Cheers, > Hermann apparently it's the opposite here: from 2/3 to 3/4. FEC_AUTO solves all problems. Thanks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] VHF tuning broken for TDA8275A cards?
Hi Nico, Am Donnerstag, den 20.12.2007, 12:01 +0100 schrieb Nico Sabbi: > Hi, > in recent kernels (up to 2.6.23xxx) my Lifeview Trio can't tune > anymore VHF channels, that used to work in previous kernels > (after a patch by Hartmutt that IIRC was integrated in several months > ago). I haven't tried an hg snapshot yet, but I'd like to know if > other users have my problem. you asked the other way round, but at least I can confirm that my tda8275a cards and also such with the FMD1216ME and tda10046ht/a still tune the single VHF transponder we have here. I'm using about ten to four days old v4l-dvb mercurial master on some 2.6.23 and an old 2.6.20 currently. You likely noticed some reports, that on VHF some transmitters changed from FEC 3/4 to 2/3 recently. If not already done, it might be worth a try creating a new channels.conf. Let me know, if you like to see some mplayer or other logs. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problems with building own module
Hi, I was able to enable my module in "make config" (though only by removing the ieee1394 dependancy), but even then, no module is compiled :-( Greetings, Ben -Original Message- From: Christian Praehauser [mailto:[EMAIL PROTECTED] Sent: 20 December 2007 12:06 To: Ben Backx Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Problems with building own module Hello! Did you do a "make config" and enabled your module for the build process? Cheers, Christian. Ben Backx wrote: > Hi, > > > > I'm almost finished with the beta of a new driver, but the final part is > giving me a headache. > > I created my own Makefile, and as long as I compile with that Makefile, > everything goes fine (except insmodding, but perhaps this goes better > when I build the module together with the rest of the v4l-tree). > > First, my system specs: > > It's an AMD Athlon XP 2500+ with Ubuntu 7.10 and standard kernel of > Ubuntu (version 2.6.22-14). > > > > The makefile I created looks something like this: > > > > *obj-m += dvb-driver.o* > > * * > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core * > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)* > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)/include* > > * * > > *all:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > modules* > > * * > > *clean:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > clean* > > * * > > Compilation using this file goes fine. > So, I modified this file as is stated in README.patches and created > something like this: > > > > *obj-$(CONFIG_DVB_DRIVER) := dvb-driver.o* > > ** > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core* > > ** > > *driver.c: driver.h otherfile.h another.h* > > *otherfile.c: otherfile.h driver.h* > > *another.c: another.h otherfile.h* > > * * > > I added all the source-files to the directory dvb-driver in the folder > linux/drivers/media/dvb off the v4l-dvb-tree. > > Then, I modified linux/drivers/media/dvb/Makefile so it contains the > folder of my driver. Finally, I added "source > "drivers/media/dvb/dvb-driver/Kconfig" to linux/drvers/media/dvb/Kconfig. > > > > Now, when I try to build the complete library, there's no dvb-driver.o > (or any other off the .o-files) created. Some source-files are copied to > the v4l-directory, but no object is created. > > Can anyone help me out with this? Because I'm rather stuck for the moment L > > > > > > Greetings, > > Ben > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Christian Praehauser <[EMAIL PROTECTED]> || //\\//\\ || Multimedia Communications Group, ||// \/ \\|| Department of Computer Sciences, University of Salzburg http://www.cosy.sbg.ac.at/~cpraehaus/ http://www.network-research.org/ http://www.uni-salzburg.at/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Conceptronic CTVCOMBOi
Hi Miguel Angel, Am Donnerstag, den 20.12.2007, 16:32 +0100 schrieb Miguel Ángel Fernández: > I'm sorry, I had sent this message directly to Hermann's e-mail instead of to > the list. > I forward it again, I ask for excuses for this mistake. sorry too, I have a cold currently and did not even notice it. > > From: hermann > > Date: Tue, 18 Dec 2007 02:10:29 +0100 > > > Holla, > Hello! > > > do you have to do anything actively? > No I don't. It's automatically detected. Fine! > > > > It is a dual tuner device and what about the remote so far? > It has a digital tuner and an analogue tuner. You can watch 1 dvb-t channel + > 1 analogue channel at > the same time. But it is not posible to see 2 dvb-t channels at the same time > or 2 analogue channels. > > Sorry, about the remote I can't tell you anything because I don't know how to > configure it. It should have a KS700 i2c remote controller then. There is a patch around from Dwaine Garden for the Kworld ATSC110 based on a patch by Henry Wong for the MSI [EMAIL PROTECTED] with KS300. > > > > Please send us "dmesg" for the saa713x and tuner stuff. > [ 24.468000] saa7130/34: v4l2 driver version 0.2.14 loaded > [ 24.468000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 > [ 24.468000] ACPI: PCI Interrupt :00:0d.0[A] -> Link [LNKC] -> GSI 11 > (level, low) -> IRQ 11 > [ 24.468000] saa7133[0]: found at :00:0d.0, rev: 209, irq: 11, latency: > 32, mmio: 0xde001000 > [ 24.468000] saa7133[0]: subsystem: 17de:7201, board: Tevion/KWorld DVB-T > 220RF [card=88,autodetected] > [ 24.468000] saa7133[0]: board init: gpio is 100 > [ 24.604000] saa7133[0]: i2c eeprom 00: de 17 01 72 ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 24.604000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff > [ 25.212000] tuner 1-004b: chip found @ 0x96 (saa7133[0]) > [ 25.26] tuner 1-004b: setting tuner address to 61 > [ 25.308000] tuner 1-004b: type set to tda8290+75a > [ 25.592000] parport_pc 00:0a: reported by Plug and Play ACPI > [ 25.592000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 > [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] > [ 25.804000] pnp: Device 01:01.02 activated. > [ 25.824000] gameport: NS558 PnP Gameport is pnp01:01.02/gameport0, io > 0x200, speed 438kHz > [ 27.092000] tuner 1-004b: setting tuner address to 61 > [ 27.132000] tuner 1-004b: type set to tda8290+75a > [ 28.452000] saa7133[0]: registered device video0 [v4l2] > [ 28.456000] saa7133[0]: registered device vbi0 > [ 28.456000] saa7133[0]: registered device radio0 > [ 28.544000] ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKD] -> GSI 11 > (level, low) -> IRQ 11 > [ 28.744000] saa7134 ALSA driver for DMA sound loaded > [ 28.744000] saa7133[0]/alsa: saa7133[0] at 0xde001000 irq 11 registered as > card -2 > [ 28.812000] DVB: registering new adapter (saa7133[0]). > [ 28.812000] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... > [ 28.92] tda1004x: setting up plls for 48MHz sampling clock > [ 29.204000] tda1004x: found firmware revision 29 -- ok > [ 30.968000] lp0: using parport0 (interrupt-driven). > [ 31.068000] Adding 939792k swap on /dev/hda3. Priority:-1 extents:1 > across:939792k > [ 31.708000] EXT3 FS on hda2, internal journal > [ 33.06] NET: Registered protocol family 10 > [ 33.06] lo: Disabled Privacy Extensions > [ 43.608000] eth0: no IPv6 routers present > [ 47.308000] No dock devices found. > [ 47.556000] input: Power Button (FF) as /class/input/input4 > [ 47.556000] ACPI: Power Button (FF) [PWRF] > [ 47.604000] input: Power Button (CM) as /class/input/input5 > [ 47.604000] ACPI: Power Button (CM) [PWRB] > [ 47.628000] input: Sleep Button (CM) as /class/input/input6 > [ 47.628000] ACPI: Sleep Button (CM) [SLPB] > [ 61.244000] ppdev: user-space parallel port driver > [ 71.412000] audit(1198074711.646:3): type=1503 > operation="inode_permission" requested_mask="a" denied_mask="a" > name="/dev/tty" pid=4753 profile="/usr/sbin/cupsd" > [ 88.308000] tda1004x: setting up plls for 48MHz sampling clock > [ 88.592000] tda1004x: found firmware revision 29 -- ok > Seems all fine, will have a closer look after Christmas. > > > > > Thanks for your report! > It is the minimal thing that I can do for the community Thanks again, Hermann ___
Re: [linux-dvb] [PATCH] mt312: coding style improvements
On Donnerstag, 20. Dezember 2007, Andreas Oberritter wrote: > Matthias Schwarzott wrote: > > Changing mt312 driver today. > > > > The first patch improves codingstyle - I did fix almost all things > > checkpatch lists. > > I did not change if ((ret = func(a)) < 0) { > > Btw. what do you think about this coding pattern? Should that also be changed to (as checkpatch suggests): ret = func(a); if (ret < 0) { As the first form seems to be used in very many lines and different drivers. Matthias -- Matthias Schwarzott (zzam) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] budget-av.c Patch for DVB-T card "EasyWatch " from Satelco
Hi. Here is my patch for Satelco DVB-T which I posted earlier already once. Been using it now for some weeks and seems to work nicely with vdr. Signed-off-by: Kim Sandberg <[EMAIL PROTECTED]> diff -u -r v4l-dvb.orig/linux/drivers/media/dvb/ttpci/budget-av.c v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c --- v4l-dvb.orig/linux/drivers/media/dvb/ttpci/budget-av.c 2007-12-20 22:29:47.0 +0200 +++ v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c 2007-12-20 22:33:50.0 +0200 @@ -910,6 +910,7 @@ #define SUBID_DVBC_CINERGY1200 0x1156 #define SUBID_DVBC_CINERGY1200_MK3 0x1176 +#define SUBID_DVBT_EASYWATCH 0x003a #define SUBID_DVBT_KNC1_PLUS 0x0031 #define SUBID_DVBT_KNC10x0030 #define SUBID_DVBT_CINERGY1200 0x1157 @@ -1018,6 +1019,7 @@ } break; + case SUBID_DVBT_EASYWATCH: case SUBID_DVBT_KNC1: case SUBID_DVBT_KNC1_PLUS: case SUBID_DVBT_CINERGY1200: @@ -1248,6 +1250,7 @@ MAKE_BUDGET_INFO(satewps, "Satelco EasyWatch DVB-S", BUDGET_KNC1S); MAKE_BUDGET_INFO(satewplc, "Satelco EasyWatch DVB-C", BUDGET_KNC1CP); MAKE_BUDGET_INFO(satewcmk3, "Satelco EasyWatch DVB-C MK3", BUDGET_KNC1C_MK3); +MAKE_BUDGET_INFO(satewt, "Satelco EasyWatch DVB-T", BUDGET_KNC1C_MK3); MAKE_BUDGET_INFO(knc1sp, "KNC1 DVB-S Plus", BUDGET_KNC1SP); MAKE_BUDGET_INFO(knc1cp, "KNC1 DVB-C Plus", BUDGET_KNC1CP); MAKE_BUDGET_INFO(knc1cmk3, "KNC1 DVB-C MK3", BUDGET_KNC1C_MK3); @@ -1272,6 +1275,7 @@ MAKE_EXTENSION_PCI(satewps, 0x1894, 0x001b), MAKE_EXTENSION_PCI(satewplc, 0x1894, 0x002a), MAKE_EXTENSION_PCI(satewcmk3, 0x1894, 0x002c), + MAKE_EXTENSION_PCI(satewt, 0x1894, 0x003a), MAKE_EXTENSION_PCI(knc1c, 0x1894, 0x0020), MAKE_EXTENSION_PCI(knc1cp, 0x1894, 0x0021), MAKE_EXTENSION_PCI(knc1cmk3, 0x1894, 0x0022), satelco_easywatch_dvb-t.diff Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
CityK wrote: > John Goacher wrote: > >> I have no problem with the images being added to the wiki, but I would >> prefer if you or some other kind individual would undertake this as >> I've no experience of updating the wiki. >> > > Thanks, I'll add them in a few minutes or so. Okay, done ... had to shrink them some first before uploading, but they still are of good quality: http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_Sat_HDTV_Pro_USB_%28452e%29#Overview.2FFeatures Note, as I've added to the wiki article, it would seem to be the case that this is a TechnoTrend rebrand (though, not a great surprise really). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV-CI from Hauppauge
Luc Brosens wrote: > all, > > so I got the WinTV-CI from Hauppauge. Nice little thing, powered through the > USB(2)-port. > On the box, is says "Common-Interface extension over USB". Cool. > > There's software with it, but of course only XP and Vista... which are out of > the question ;-) > > I'm contacting Hauppauge's tech support for specs, let's hope they're > responsive. They won't be able to help, I can - but not for a few weeks. I'm expecting to release public USB protocol information during Jan 08 which would allow a GPL driver to be written. Right now I have nothing to give you. If you feel adventurous, feel free to start now by reverse engineering the protocol with a windows software USB sniffer, it won't be wasted work. The device is Cypress FX2 based (which Linux has lots of examples for) and it loads custom firmware (which Linux has lots of examples of) apart from that I think the protocol is very simple. How to integrate it with the kernel s/w demux would be an interesting debate. Let me know if I can help. Regards, - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Freecom DVB-T - 2 devices?
Hi all, I've had this stick in stock and haven;t used it for a while. I have just compiled a current hg tree and plugged the device and notices that it came up twice. I don't remember that behaviour in my initial usage. Kaffeine sees 2 devices too. How normal or not is it? Nico Dec 20 18:44:38 youkaida kernel: [ 112.744000] usb 5-5: new high speed USB device using ehci_hcd and address 4 Dec 20 18:44:38 youkaida kernel: [ 112.876000] usb 5-5: configuration #1 chosen from 1 choice Dec 20 18:44:38 youkaida kernel: [ 113.02] dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware Dec 20 18:44:38 youkaida kernel: [ 113.036000] dvb-usb: downloading firmware from file 'dvb-usb-wt220u-fc03.fw' Dec 20 18:44:38 youkaida kernel: [ 113.128000] usbcore: registered new interface driver dvb_usb_dtt200u Dec 20 18:44:40 youkaida kernel: [ 114.488000] usb 5-5: USB disconnect, address 4 Dec 20 18:44:40 youkaida kernel: [ 114.488000] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Dec 20 18:44:41 youkaida kernel: [ 115.62] usb 5-5: new high speed USB device using ehci_hcd and address 5 Dec 20 18:44:41 youkaida kernel: [ 115.756000] usb 5-5: configuration #1 chosen from 1 choice Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: will use the device's hardware PID filter (table count: 15). Dec 20 18:44:41 youkaida kernel: [ 115.756000] DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)) Dec 20 18:44:41 youkaida kernel: [ 115.756000] DVB: registering frontend 0 (WideView USB DVB-T)... Dec 20 18:44:41 youkaida kernel: [ 115.756000] input: IR-receiver inside an USB DVB receiver as /class/input/input7 Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: schedule remote query interval to 300 msecs. Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: will use the device's hardware PID filter (table count: 15). Dec 20 18:44:41 youkaida kernel: [ 115.756000] DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)) Dec 20 18:44:41 youkaida kernel: [ 115.756000] DVB: registering frontend 1 (WideView USB DVB-T)... Dec 20 18:44:41 youkaida kernel: [ 115.756000] input: IR-receiver inside an USB DVB receiver as /class/input/input8 Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: schedule remote query interval to 300 msecs. Dec 20 18:44:41 youkaida kernel: [ 115.756000] dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. Bus 005 Device 005: ID 14aa:0226 AVerMedia (again) or C&E ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] WinTV-CI from Hauppauge
all, so I got the WinTV-CI from Hauppauge. Nice little thing, powered through the USB(2)-port. On the box, is says "Common-Interface extension over USB". There's software with it, but of course only XP and Vista... which are out of the question ;-) I'm contacting Hauppauge's tech support for specs, let's hope they're responsive. any pointers on writing a device driver for this thing are appreciated here's the dmesg and lsusb -v output : usb 1-7: new high speed USB device using ehci_hcd and address 2 usb 1-7: new device found, idVendor=2040, idProduct=1100 usb 1-7: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-7: configuration #1 chosen from 1 choice Bus 001 Device 002: ID 2040:1100 Hauppauge Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x2040 Hauppauge idProduct 0x1100 bcdDevice0.02 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 171 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x88 EP 8 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 2 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
John Goacher wrote: > I have no problem with the images being added to the wiki, but I would > prefer if you or some other kind individual would undertake this as > I've no experience of updating the wiki. Thanks, I'll add them in a few minutes or so. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
CityK wrote: > John Goacher wrote: > >> Manu Abraham wrote: >> >> >>> In either case, can you please put up some high resolution pictures of >>> your device up some place >>> > > Of course, as I've said before on a couple of occasions, image upload > requests to "some place" should instead be -- "can you please put up > some high resolution pictures of your device in the wiki" > >> I've uploaded high resolution photos of the top and underside of the pcb >> at >> the following URLs: >> >> http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_top.jpg >> >> and >> >> http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_base.jpg >> >> > > John can you, or with your permission, have these images added to the > wiki? > I have no problem with the images being added to the wiki, but I would prefer if you or some other kind individual would undertake this as I've no experience of updating the wiki. regards, John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
John Goacher wrote: > Manu Abraham wrote: > > >> In either case, can you please put up some high resolution pictures of >> your device up some place >> Of course, as I've said before on a couple of occasions, image upload requests to "some place" should instead be -- "can you please put up some high resolution pictures of your device in the wiki" > I've uploaded high resolution photos of the top and underside of the pcb at > the following URLs: > > http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_top.jpg > > and > > http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_base.jpg > > John can you, or with your permission, have these images added to the wiki? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] mt312: coding style improvements
Matthias Schwarzott wrote: > Changing mt312 driver today. > > The first patch improves codingstyle - I did fix almost all things checkpatch > lists. > I did not change if ((ret = func(a)) < 0) { > > The second patch does remove extra KERN_DEBUG from dprintk calls, as dprintk > already adds KERN_DEBUG: > #define dprintk(args...) \ > do { \ > if (debug) printk(KERN_DEBUG "mt312: " args); \ > } while (0) Thank you, Matthias! Mauro, can you please apply both patches to your tree? Best regards, Andreas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] mt312: coding style improvements
Hi Andreas, Hi List! Changing mt312 driver today. The first patch improves codingstyle - I did fix almost all things checkpatch lists. I did not change if ((ret = func(a)) < 0) { The second patch does remove extra KERN_DEBUG from dprintk calls, as dprintk already adds KERN_DEBUG: #define dprintk(args...) \ do { \ if (debug) printk(KERN_DEBUG "mt312: " args); \ } while (0) Matthias -- Matthias Schwarzott (zzam) Index: v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c === --- v4l-dvb.orig/linux/drivers/media/dvb/frontends/mt312.c +++ v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c @@ -37,9 +37,9 @@ struct mt312_state { - struct i2c_adapter* i2c; + struct i2c_adapter *i2c; /* configuration settings */ - const struct mt312_config* config; + const struct mt312_config *config; struct dvb_frontend frontend; u8 id; @@ -49,14 +49,15 @@ struct mt312_state { static int debug; #define dprintk(args...) \ do { \ - if (debug) printk(KERN_DEBUG "mt312: " args); \ + if (debug) \ + printk(KERN_DEBUG "mt312: " args); \ } while (0) #define MT312_SYS_CLK 9000UL /* 90 MHz */ #define MT312_LPOWER_SYS_CLK 6000UL /* 60 MHz */ #define MT312_PLL_CLK 1000UL /* 10 MHz */ -static int mt312_read(struct mt312_state* state, const enum mt312_reg_addr reg, +static int mt312_read(struct mt312_state *state, const enum mt312_reg_addr reg, void *buf, const size_t count) { int ret; @@ -79,7 +80,7 @@ static int mt312_read(struct mt312_state return -EREMOTEIO; } - if(debug) { + if (debug) { int i; dprintk("R(%d):", reg & 0x7f); for (i = 0; i < count; i++) @@ -90,14 +91,14 @@ static int mt312_read(struct mt312_state return 0; } -static int mt312_write(struct mt312_state* state, const enum mt312_reg_addr reg, +static int mt312_write(struct mt312_state *state, const enum mt312_reg_addr reg, const void *src, const size_t count) { int ret; u8 buf[count + 1]; struct i2c_msg msg; - if(debug) { + if (debug) { int i; dprintk("W(%d):", reg & 0x7f); for (i = 0; i < count; i++) @@ -123,13 +124,13 @@ static int mt312_write(struct mt312_stat return 0; } -static inline int mt312_readreg(struct mt312_state* state, +static inline int mt312_readreg(struct mt312_state *state, const enum mt312_reg_addr reg, u8 *val) { return mt312_read(state, reg, val, 1); } -static inline int mt312_writereg(struct mt312_state* state, +static inline int mt312_writereg(struct mt312_state *state, const enum mt312_reg_addr reg, const u8 val) { return mt312_write(state, reg, &val, 1); @@ -140,12 +141,12 @@ static inline u32 mt312_div(u32 a, u32 b return (a + (b / 2)) / b; } -static int mt312_reset(struct mt312_state* state, const u8 full) +static int mt312_reset(struct mt312_state *state, const u8 full) { return mt312_writereg(state, RESET, full ? 0x80 : 0x40); } -static int mt312_get_inversion(struct mt312_state* state, +static int mt312_get_inversion(struct mt312_state *state, fe_spectral_inversion_t *i) { int ret; @@ -160,7 +161,7 @@ static int mt312_get_inversion(struct mt return 0; } -static int mt312_get_symbol_rate(struct mt312_state* state, u32 *sr) +static int mt312_get_symbol_rate(struct mt312_state *state, u32 *sr) { int ret; u8 sym_rate_h; @@ -192,7 +193,8 @@ static int mt312_get_symbol_rate(struct dec_ratio = ((buf[0] >> 5) & 0x07) * 32; - if ((ret = mt312_read(state, SYM_RAT_OP_H, buf, sizeof(buf))) < 0) + if ((ret = mt312_read(state, SYM_RAT_OP_H, buf, + sizeof(buf))) < 0) return ret; sym_rat_op = (buf[0] << 8) | buf[1]; @@ -207,7 +209,7 @@ static int mt312_get_symbol_rate(struct return 0; } -static int mt312_get_code_rate(struct mt312_state* state, fe_code_rate_t *cr) +static int mt312_get_code_rate(struct mt312_state *state, fe_code_rate_t *cr) { const fe_code_rate_t fec_tab[8] = { FEC_1_2, FEC_2_3, FEC_3_4, FEC_5_6, FEC_6_7, FEC_7_8, @@ -224,14 +226,15 @@ static int mt312_get_code_rate(struct mt return 0; } -static int mt312_initfe(struct dvb_frontend* fe) +static int mt312_initfe(struct dvb_frontend *fe) { struct mt312_state *state = fe->demodulator_priv; int ret; u8 buf[2]; /* wake up */ - if ((ret = mt312_writereg(state, CONFIG, (state->frequency == 60 ? 0x88 : 0x8c))) < 0) + if ((ret = mt312_writereg(state, CONFIG, + (state->frequency == 60 ? 0x88 : 0x8c))) < 0) return ret; /* wait at least 150 usec */ @@ -241,17 +244,20 @@ static int mt312_initfe(struct dvb_front if ((ret = mt312_reset(state, 1)) < 0) return ret; -// Per datasheet, write correct values. 09/28/03 ACCJr. -// If we don't do this, we won't get FE_HAS_VITERBI in the VP310. +/* Per datasheet, write correct values. 09/28/03 ACCJr. + * If we don't do this, we won't get FE_HAS_VITERBI in the VP310. */ { - u8 buf_def[8]={0x14, 0x12, 0x03, 0x02, 0x01, 0x00, 0x00, 0x00
Re: [linux-dvb] Conceptronic CTVCOMBOi
I'm sorry, I had sent this message directly to Hermann's e-mail instead of to the list. I forward it again, I ask for excuses for this mistake. > From: hermann > Date: Tue, 18 Dec 2007 02:10:29 +0100 > Holla, Hello! > do you have to do anything actively? No I don't. It's automatically detected. > > It is a dual tuner device and what about the remote so far? It has a digital tuner and an analogue tuner. You can watch 1 dvb-t channel + 1 analogue channel at the same time. But it is not posible to see 2 dvb-t channels at the same time or 2 analogue channels. Sorry, about the remote I can't tell you anything because I don't know how to configure it. > > Please send us "dmesg" for the saa713x and tuner stuff. [ 24.468000] saa7130/34: v4l2 driver version 0.2.14 loaded [ 24.468000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [ 24.468000] ACPI: PCI Interrupt :00:0d.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 [ 24.468000] saa7133[0]: found at :00:0d.0, rev: 209, irq: 11, latency: 32, mmio: 0xde001000 [ 24.468000] saa7133[0]: subsystem: 17de:7201, board: Tevion/KWorld DVB-T 220RF [card=88,autodetected] [ 24.468000] saa7133[0]: board init: gpio is 100 [ 24.604000] saa7133[0]: i2c eeprom 00: de 17 01 72 ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 24.604000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 25.212000] tuner 1-004b: chip found @ 0x96 (saa7133[0]) [ 25.26] tuner 1-004b: setting tuner address to 61 [ 25.308000] tuner 1-004b: type set to tda8290+75a [ 25.592000] parport_pc 00:0a: reported by Plug and Play ACPI [ 25.592000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] [ 25.804000] pnp: Device 01:01.02 activated. [ 25.824000] gameport: NS558 PnP Gameport is pnp01:01.02/gameport0, io 0x200, speed 438kHz [ 27.092000] tuner 1-004b: setting tuner address to 61 [ 27.132000] tuner 1-004b: type set to tda8290+75a [ 28.452000] saa7133[0]: registered device video0 [v4l2] [ 28.456000] saa7133[0]: registered device vbi0 [ 28.456000] saa7133[0]: registered device radio0 [ 28.544000] ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 28.744000] saa7134 ALSA driver for DMA sound loaded [ 28.744000] saa7133[0]/alsa: saa7133[0] at 0xde001000 irq 11 registered as card -2 [ 28.812000] DVB: registering new adapter (saa7133[0]). [ 28.812000] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... [ 28.92] tda1004x: setting up plls for 48MHz sampling clock [ 29.204000] tda1004x: found firmware revision 29 -- ok [ 30.968000] lp0: using parport0 (interrupt-driven). [ 31.068000] Adding 939792k swap on /dev/hda3. Priority:-1 extents:1 across:939792k [ 31.708000] EXT3 FS on hda2, internal journal [ 33.06] NET: Registered protocol family 10 [ 33.06] lo: Disabled Privacy Extensions [ 43.608000] eth0: no IPv6 routers present [ 47.308000] No dock devices found. [ 47.556000] input: Power Button (FF) as /class/input/input4 [ 47.556000] ACPI: Power Button (FF) [PWRF] [ 47.604000] input: Power Button (CM) as /class/input/input5 [ 47.604000] ACPI: Power Button (CM) [PWRB] [ 47.628000] input: Sleep Button (CM) as /class/input/input6 [ 47.628000] ACPI: Sleep Button (CM) [SLPB] [ 61.244000] ppdev: user-space parallel port driver [ 71.412000] audit(1198074711.646:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=4753 profile="/usr/sbin/cupsd" [ 88.308000] tda1004x: setting up plls for 48MHz sampling clock [ 88.592000] tda1004x: found firmware revision 29 -- ok > > Thanks for your report! It is the minimal thing that I can do for the community > > Cheers, > Hermann Bye! _ Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar siempre a la última Guapos y guapas, clips musicales y estrenos de cine. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problems with building own module
Hey, I haven't tried that, but I did now. There's nothing to see about my driver/device and there's also something wrong with writing the config-file (Error during writing of the kernel configuration, that's all there is to read). Also: I executed make config as root (and as non root), problem stayed. Gr, Ben -Original Message- From: Christian Praehauser [mailto:[EMAIL PROTECTED] Sent: 20 December 2007 12:06 To: Ben Backx Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Problems with building own module Hello! Did you do a "make config" and enabled your module for the build process? Cheers, Christian. Ben Backx wrote: > Hi, > > > > I'm almost finished with the beta of a new driver, but the final part is > giving me a headache. > > I created my own Makefile, and as long as I compile with that Makefile, > everything goes fine (except insmodding, but perhaps this goes better > when I build the module together with the rest of the v4l-tree). > > First, my system specs: > > It's an AMD Athlon XP 2500+ with Ubuntu 7.10 and standard kernel of > Ubuntu (version 2.6.22-14). > > > > The makefile I created looks something like this: > > > > *obj-m += dvb-driver.o* > > * * > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core * > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)* > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)/include* > > * * > > *all:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > modules* > > * * > > *clean:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > clean* > > * * > > Compilation using this file goes fine. > So, I modified this file as is stated in README.patches and created > something like this: > > > > *obj-$(CONFIG_DVB_DRIVER) := dvb-driver.o* > > ** > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core* > > ** > > *driver.c: driver.h otherfile.h another.h* > > *otherfile.c: otherfile.h driver.h* > > *another.c: another.h otherfile.h* > > * * > > I added all the source-files to the directory dvb-driver in the folder > linux/drivers/media/dvb off the v4l-dvb-tree. > > Then, I modified linux/drivers/media/dvb/Makefile so it contains the > folder of my driver. Finally, I added "source > "drivers/media/dvb/dvb-driver/Kconfig" to linux/drvers/media/dvb/Kconfig. > > > > Now, when I try to build the complete library, there's no dvb-driver.o > (or any other off the .o-files) created. Some source-files are copied to > the v4l-directory, but no object is created. > > Can anyone help me out with this? Because I'm rather stuck for the moment L > > > > > > Greetings, > > Ben > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Christian Praehauser <[EMAIL PROTECTED]> || //\\//\\ || Multimedia Communications Group, ||// \/ \\|| Department of Computer Sciences, University of Salzburg http://www.cosy.sbg.ac.at/~cpraehaus/ http://www.network-research.org/ http://www.uni-salzburg.at/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: hauppauge nova-t stick driver problem... driver hacking?
Hi, related to this problem/dirty-hack, I've tried different things ("soft reinitialisations") and they didn't seem to work. In the file dvb-core/dvb_frontend.c, in function dvb_frontend_ioctl, inside the "case FE_SET_FRONTEND", I've tried different options before the retunning: 1) added a call to dvb_frontend_reinitialise, same problem 2) added a call to dvb_frontend_init, same problem 3) added a call to dvb_frontend_stop / dvb_frontend_start, same problem Since the problem also persists if I just rmmod/modprobe the module (dvb_usb_dib0700), and the only solution working right now is to unplug/plug the stick, I assume that I must do something more in order to force an almost-full stop of the stick, firmware reload, etc. Is this possible? Does anybody have any idea about how to do this? I know that's very dirty, but I just want my stick to work reliabily :-) Anyway, if anybody has an idea about where to look in order to fix this behaviour, I'll be glad to help with tests/debug, etc. Best, Jose -- Forwarded message -- From: José Oliver Segura <[EMAIL PROTECTED]> Date: Dec 19, 2007 9:20 PM Subject: hauppauge nova-t stick driver problem... driver hacking? To: linux-dvb [...] I'm wondering if anybody knows a solution for this behaviour... if not: can anybody point me (give me some directions) about implementing a hack in order to do a "fake reload" of the module and/or a "reinitialization" of the stick in each channel zap? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
Manu Abraham wrote: >>> John Goacher wrote: >>> When i looked at the pctv452 driver it was based on a older stb0899 >>> driver >>> snapshot. >>> It still is based on the same ? There were many issues fixed in newer >>> changesets, so >>> i don't know whether the issue that you see is really a stb0899 driver >>> issue which has >>> been fixed already or maybe that the pctv device requires some specific >>> settings ? I >>> don't know.. I don't have much info on this device. >>> >>> Regards, >>> Manu >>> >> >> Hi Manu, >> >> I was using an older snapshot, but I've now rebuilt and re-installed the >> driver following the instructions in the wiki entry at >> http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_Sat_HDTV_Pro_USB_%28452e%29 >> >> I'm using what I believe to be the latest snapshot of STB0899 which is >> revision 5882 at http://linuxtv.org/hg/~manu/stb0899/rev/5b19ac1cddb5 >> >> Unfortunately, I still get the packet loss problem with this snapshot. > > > There can be 2 possibilities > * some pctv452 specific setting required, due to the hardware difference > * some unknown bug that gets explicitly noticed in a specific combination > > In either case, can you please put up some high resolution pictures of > your > device up some place (since i don't have much of an understanding about > your hardware configuration, hoping that the pictures might yield some > clues) ? > > Regards, > Manu > I've uploaded high resolution photos of the top and underside of the pcb at the following URLs: http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_top.jpg and http://www.goacher.dsl.pipex.com/pctv/pctv452e_rev01_base.jpg The device is revision 01. By the way, is there any method for getting more error information from the device ? Do you know whether packets in error are discarded by the device without being passed to the device driver ? If so, is there a programmable option to pass error packets through to the device driver and application ? regards, John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problems with building own module
Hello! Did you do a "make config" and enabled your module for the build process? Cheers, Christian. Ben Backx wrote: > Hi, > > > > I’m almost finished with the beta of a new driver, but the final part is > giving me a headache. > > I created my own Makefile, and as long as I compile with that Makefile, > everything goes fine (except insmodding, but perhaps this goes better > when I build the module together with the rest of the v4l-tree). > > First, my system specs: > > It’s an AMD Athlon XP 2500+ with Ubuntu 7.10 and standard kernel of > Ubuntu (version 2.6.22-14). > > > > The makefile I created looks something like this: > > > > *obj-m += dvb-driver.o* > > * * > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core * > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)* > > *EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)/include* > > * * > > *all:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > modules* > > * * > > *clean:* > > *make -C /lib/modules/$(shell uname -r)/build M=$(PWD) > clean* > > * * > > Compilation using this file goes fine. > So, I modified this file as is stated in README.patches and created > something like this: > > > > *obj-$(CONFIG_DVB_DRIVER) := dvb-driver.o* > > ** > > *dvb-driver-objs := driver.o otherfile.o another.o* > > * * > > *EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394* > > *EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core* > > ** > > *driver.c: driver.h otherfile.h another.h* > > *otherfile.c: otherfile.h driver.h* > > *another.c: another.h otherfile.h* > > * * > > I added all the source-files to the directory dvb-driver in the folder > linux/drivers/media/dvb off the v4l-dvb-tree. > > Then, I modified linux/drivers/media/dvb/Makefile so it contains the > folder of my driver. Finally, I added “source > “drivers/media/dvb/dvb-driver/Kconfig” to linux/drvers/media/dvb/Kconfig. > > > > Now, when I try to build the complete library, there’s no dvb-driver.o > (or any other off the .o-files) created. Some source-files are copied to > the v4l-directory, but no object is created. > > Can anyone help me out with this? Because I’m rather stuck for the moment L > > > > > > Greetings, > > Ben > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Christian Praehauser <[EMAIL PROTECTED]> || //\\//\\ || Multimedia Communications Group, ||// \/ \\|| Department of Computer Sciences, University of Salzburg http://www.cosy.sbg.ac.at/~cpraehaus/ http://www.network-research.org/ http://www.uni-salzburg.at/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] VHF tuning broken for TDA8275A cards?
Hi, in recent kernels (up to 2.6.23xxx) my Lifeview Trio can't tune anymore VHF channels, that used to work in previous kernels (after a patch by Hartmutt that IIRC was integrated in several months ago). I haven't tried an hg snapshot yet, but I'd like to know if other users have my problem. Thanks, Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Start thinking about potential Google Summer of Code Projects we could run
On Wed, 19 Dec 2007 11:26:35 -0500 CityK <[EMAIL PROTECTED]> wrote: > Hi folks, > > Google summer of code will be rolling around in a couple of months. Now > I know we've talked a little bit about it before, but I don't recall > what the thoughts on it were. In any regard, on the surface of things, > it would seem a perfect opportunity for the LinuxTV Project to leverage > -- i.e. enslave a few students to get some desperately needed tasks, > components, apps, drivers or whatever done. Side benefit -- it might > hopefully attact a few more developers to the project too -- get some > new blood, stir up the pot, chase after nagging/long-time bugs etc, etc. > > So, I suggest we start thinking about or, better yet, discussing > ideas/projects for which we could make use of the GSOC. > > (I, of course, was kidding about the enslavement part) The userspace library seems interesting for me. On kernel side, a good contribution would be the V4L2 conversion. There are still several V4L1 only drivers that need conversions (mostly webcams). Another good contribution would be testset tools to allow checking regressions at the drivers and driver compliance with the API. This tool should check both DVB and V4L APIs, identifying the differences between an old version driver and the newer one, running all possible supported ioctls. I've started working on such tool, for V4L, but never finished, due to the lack of time (the current work is at v4l2-apps/test/). Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] drivers for Freecom rev 4 DVB-T USB Stick
Hello, I would like to know if there is any progress with the drivers for the RTL2831U Chipset as it is used in the Freecom DVB-T USB-Stick rev 4. Also i would like to help testing and debugging, if there is need for it. Steven ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] VP1032 + Cryptoworks
On Wed, Dec 19, 2007 at 11:49:42PM +0400, Manu Abraham wrote: > > en50221_app_ai_parse_app_info: Received short data > > > > I think, it could be that the stack at some point sends some junk to > the device, thereby causing the device to go crazy. Please do not that > the library is divided into 2 parts , the High Level and the Low Level > API's . In this case the Low level API part in the library might be > sending junk, thereby causing the breakage, also it could be the > hardware, but something like a few minutes doesn't seem to be a > hardware issue. > > This requires quite a bit as to what messages are sent to the driver. > Also possible is a bug in the driver, which can't be ruled out either. Is there any other relevant info I can post to the list to help debugging? I could even allow root access to the machine in question. Do you think the CAM could be ruled out, or should I try a Philips Cryptoworks module instead of the SCM one? Thanks, David -- David Santinoli Tieffe Sistemi S.r.l. viale Piceno 21, Milano www.tieffesistemi.com tel. +39 02 76115215 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problems with building own module
The second CFLAGS-rule of the modified makefile looks like this off-course: EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core Apparently, something went wrong during copy-paste :-s From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Backx Sent: 20 December 2007 10:09 To: linux-dvb@linuxtv.org Subject: [linux-dvb] Problems with building own module Hi, I'm almost finished with the beta of a new driver, but the final part is giving me a headache. I created my own Makefile, and as long as I compile with that Makefile, everything goes fine (except insmodding, but perhaps this goes better when I build the module together with the rest of the v4l-tree). First, my system specs: It's an AMD Athlon XP 2500+ with Ubuntu 7.10 and standard kernel of Ubuntu (version 2.6.22-14). The makefile I created looks something like this: obj-m += dvb-driver.o dvb-driver-objs := driver.o otherfile.o another.o EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394 EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r) EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)/include all: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules clean: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean Compilation using this file goes fine. So, I modified this file as is stated in README.patches and created something like this: obj-$(CONFIG_DVB_DRIVER) := dvb-driver.o dvb-driver-objs := driver.o otherfile.o another.o EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394 EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core driver.c: driver.h otherfile.h another.h otherfile.c: otherfile.h driver.h another.c: another.h otherfile.h I added all the source-files to the directory dvb-driver in the folder linux/drivers/media/dvb off the v4l-dvb-tree. Then, I modified linux/drivers/media/dvb/Makefile so it contains the folder of my driver. Finally, I added "source "drivers/media/dvb/dvb-driver/Kconfig" to linux/drvers/media/dvb/Kconfig. Now, when I try to build the complete library, there's no dvb-driver.o (or any other off the .o-files) created. Some source-files are copied to the v4l-directory, but no object is created. Can anyone help me out with this? Because I'm rather stuck for the moment L Greetings, Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problems with building own module
Hi, I'm almost finished with the beta of a new driver, but the final part is giving me a headache. I created my own Makefile, and as long as I compile with that Makefile, everything goes fine (except insmodding, but perhaps this goes better when I build the module together with the rest of the v4l-tree). First, my system specs: It's an AMD Athlon XP 2500+ with Ubuntu 7.10 and standard kernel of Ubuntu (version 2.6.22-14). The makefile I created looks something like this: obj-m += dvb-driver.o dvb-driver-objs := driver.o otherfile.o another.o EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394 EXTRA_CFLAGS += -I/usr/src/linux-source-2.6.22/drivers/media/dvb/dvb-core EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r) EXTRA_CFLAGS += -I/usr/src/linux-headers-$(shell uname -r)/include all: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules clean: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean Compilation using this file goes fine. So, I modified this file as is stated in README.patches and created something like this: obj-$(CONFIG_DVB_DRIVER) := dvb-driver.o dvb-driver-objs := driver.o otherfile.o another.o EXTRA_CFLAGS := -I/usr/src/linux-source-2.6.22/drivers/ieee1394 EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core driver.c: driver.h otherfile.h another.h otherfile.c: otherfile.h driver.h another.c: another.h otherfile.h I added all the source-files to the directory dvb-driver in the folder linux/drivers/media/dvb off the v4l-dvb-tree. Then, I modified linux/drivers/media/dvb/Makefile so it contains the folder of my driver. Finally, I added "source "drivers/media/dvb/dvb-driver/Kconfig" to linux/drvers/media/dvb/Kconfig. Now, when I try to build the complete library, there's no dvb-driver.o (or any other off the .o-files) created. Some source-files are copied to the v4l-directory, but no object is created. Can anyone help me out with this? Because I'm rather stuck for the moment L Greetings, Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb