Re: [linux-dvb] DViCO Dual Digital 4 and remote

2007-11-15 Thread Robert Backhaus
Just to let those on this list know, Chris Pascoe posted patches to
enable the remote on his page
[http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/] on Monday. He may
want some more time to work on them before posting an announcement, so
caveat downlodeur.

Big thanks to all the very smart people who are working on this. (Big
Lartings to the manufacturers who are _NOT!!!)

I'm off home to apply the patches and see what happens.

Robert Backhaus.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] A link DTU advice needed

2007-11-15 Thread Dag Nygren

Hi again,

is there anything I can do to help debugging the
A-link DTU USB stick Tuning failed problem?
The stick seems to be the old model without the (m),
using the modules:

qt1010 
zl10353 
dvb_usb_gl861
dvb_usb 

and now tunes to 3 of the 4 MUX:es we have here
in Espoo, Finland but no deal with one of them whatever I do.

Best
Dag


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DViCO Dual Digital 4 and remote

2007-11-15 Thread Gabriel Noronha
Great News i'll give it a try probably Monday. Tuesday 

Thanks Chris for the patch.. 

P.S tell me if you need your own Dual digital 4 not just a friends. 

On Thu, 15 Nov 2007 04:30:02 pm Robert Backhaus wrote:
 Just to let those on this list know, Chris Pascoe posted patches to
 enable the remote on his page
 [http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/] on Monday. He may
 want some more time to work on them before posting an announcement, so
 caveat downlodeur.

 Big thanks to all the very smart people who are working on this. (Big
 Lartings to the manufacturers who are _NOT!!!)

 I'm off home to apply the patches and see what happens.

 Robert Backhaus.

 ___
 linux-dvb mailing list
 linux-dvb@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DViCO Dual Digital 4 and remote

2007-11-15 Thread Michael Krufky
Robert Backhaus wrote:
 Big thanks to all the very smart people who are working on this. (Big
 Lartings to the manufacturers who are _NOT!!!)

That's not cool.

DViCO is being very helpful.

-Mike

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Jeff Rosenberg
I just purchase the PCTV HD Ultimate Stick.  I decided upon this since it 
supported clear QAM and had flash space for recording to the stick in addition 
to the hardrive.  I read that the PCTV HD Pro Stick was supported with the 
latest Experimental build based on the em2883 chipset.  I took the risk and 
went with the Ultimate instead of the Pro.
   
  I have download the latest DVB Experimental from the Mercurial repository at 
http://mcentral.de/hg/~mrec/v4l-dvb-experimental
   
  I compiled the drivers and installed them and did the modprobe on em28xx.
   
  The Kernel Ring buffer had the following:
   
  [  191.298763] Linux video capture interface: v2.00
[  191.321285] em28xx v4l2 driver version 0.0.1 loaded
[  191.321874] usbcore: registered new interface driver em28xx
   
   
  I then plugged in the PCTV USB ultimate stick and it found the flash drive 
and readonly memory on the card used for installing the XP and Vista software 
(ugh!!!) but never found the actual PCTV USB device.
   
  After plugging in the USB device the following was displayed in the Kernel 
Ring buffer:
   
  [  233.604404] usb 3-3: new high speed USB device using ehci_hcd and
address 2
[  233.671309] usb 3-3: configuration #1 chosen from 1 choice
[  233.671487] hub 3-3:1.0: USB hub found
[  233.671649] hub 3-3:1.0: 4 ports detected
[  233.824406] usb 3-3.1: new high speed USB device using ehci_hcd and
address 3
[  233.872796] usb 3-3.1: configuration #1 chosen from 1 choice
[  233.978809] usbcore: registered new interface driver libusual
[  234.024864] Initializing USB Mass Storage driver...
[  234.025175] scsi0 : SCSI emulation for USB Mass Storage devices
[  234.025733] usb-storage: device found at 3
[  234.025739] usb-storage: waiting for device to settle before scanning
[  234.025255] usbcore: registered new interface driver usb-storage
[  234.025260] USB Mass Storage support registered.
[  236.525005] usb-storage: device scan complete
[  236.525668] scsi 0:0:0:0: Direct-Access GENERIC  TORAGE  
2269 PQ: 0 ANSI: 0
[  236.526282] scsi 0:0:0:1: CD-ROMGENERIC  TORAGE  
2269 PQ: 0 ANSI: 0 CCS
[  236.576309] sd 0:0:0:0: [sda] 2027520 512-byte hardware sectors (1038
MB)
[  236.577248] sd 0:0:0:0: [sda] Write Protect is off
[  236.577253] sd 0:0:0:0: [sda] Mode Sense: 02 00 00 00
[  236.577256] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  236.578928] sd 0:0:0:0: [sda] 2027520 512-byte hardware sectors (1038
MB)
[  236.579804] sd 0:0:0:0: [sda] Write Protect is off
[  236.579808] sd 0:0:0:0: [sda] Mode Sense: 02 00 00 00
[  236.579810] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  236.579814]  sda:3Buffer I/O error on device sda, logical block 0
[  236.580587] Buffer I/O error on device sda, logical block 0
[  236.580772] Buffer I/O error on device sda, logical block 0
[  236.580951] Buffer I/O error on device sda, logical block 0
[  236.581128] Buffer I/O error on device sda, logical block 0
[  236.581135] ldm_validate_partition_table(): Disk read failed.
[  236.581471] Buffer I/O error on device sda, logical block 0
[  236.581650] Buffer I/O error on device sda, logical block 0
[  236.581828] Buffer I/O error on device sda, logical block 0
[  236.582006] Buffer I/O error on device sda, logical block 0
[  236.582013] Dev sda: unable to read RDB block 0
[  236.582349] Buffer I/O error on device sda, logical block 0
[  236.582559]  unable to read partition table
[  236.582957] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  236.595599] sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
[  236.595716] sr 0:0:0:1: Attached scsi CD-ROM sr0
[  236.610971] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  236.611247] sr 0:0:0:1: Attached scsi generic sg1 type 5
[  236.758222] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  236.894038] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  236.989461] sd 0:0:0:0: [sda] 2027520 512-byte hardware sectors (1038
MB)
[  237.061904] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  237.158851] sd 0:0:0:0: [sda] Write Protect is off
[  237.158860] sd 0:0:0:0: [sda] Mode Sense: 02 00 00 00
[  237.158865] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  237.233777] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  237.405648] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  237.577529] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  237.675053] sd 0:0:0:0: [sda] 2027520 512-byte hardware sectors (1038
MB)
[  237.749401] usb 3-3.1: reset high speed USB device using ehci_hcd and
address 3
[  237.846355] sd 0:0:0:0: [sda] Write Protect is off
[  237.846366] sd 0:0:0:0: [sda] Mode Sense: 02 00 00 00
[  237.846370] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  237.846376]  sda:6usb 3-3.1: reset high speed USB device using
ehci_hcd and address 3
[  238.033050] 
[  238.144987] usb 3-3.1: reset high 

Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Michael Krufky
Jeff Rosenberg wrote:
 I just purchase the PCTV HD Ultimate Stick.  I decided upon this since it 
 supported clear QAM and had flash space for recording to the stick in 
 addition to the hardrive.  I read that the PCTV HD Pro Stick was supported 
 with the latest Experimental build based on the em2883 chipset.  I took the 
 risk and went with the Ultimate instead of the Pro.

[snip]

   Any chance that there will be support for this newly released USB stick ?

You wont find native support for this in any Linux Distribution's native kernel 
anytime soon.

Your best bet, in this case, is to look at Markus' experimental repository.  I 
don't think that he has support for this exact device yet, but he does have 
most of the pieces required.

#1) You need em2880-dvb support, which is not yet in the master v4l-dvb 
development branch

#2) (I think) you'll need an xc5000 driver, also not yet merged into the 
v4l-dvb master branch.

You might be able to assemble the right pieces of code together, but I don't 
know where you'll find it all at this time.

Given a few months (or weeks, in a perfect world) time, the situation may 
become clearer.

Good Luck,

Mike Krufky

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Michael Krufky
Markus Rechberger wrote:
 On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote:
   
 Jeff Rosenberg wrote:
 
 I just purchase the PCTV HD Ultimate Stick.  I decided upon this since it
   
 supported clear QAM and had flash space for recording to the stick in
 addition to the hardrive.  I read that the PCTV HD Pro Stick was supported
 with the latest Experimental build based on the em2883 chipset.  I took the
 risk and went with the Ultimate instead of the Pro.

 [snip]

 
   Any chance that there will be support for this newly released USB stick
   
 ?

 You wont find native support for this in any Linux Distribution's native
 kernel anytime soon.

 Your best bet, in this case, is to look at Markus' experimental repository.
 I don't think that he has support for this exact device yet, but he does
 have most of the pieces required.

 #1) You need em2880-dvb support, which is not yet in the master v4l-dvb
 development branch

 #2) (I think) you'll need an xc5000 driver, also not yet merged into the
 v4l-dvb master branch.

 You might be able to assemble the right pieces of code together, but I don't
 know where you'll find it all at this time.

 Given a few months (or weeks, in a perfect world) time, the situation may
 become clearer.

 

 Michael,

 this is no em28xx based device, I guess it's a dibcom one.
Ah, OK.  Thanks, Markus.

In which case, bridge-wise, it may be a bit easier (or more difficult,
depending) than I thought.

Jeff, it might be helpful if you could crack open the device and tell us
all of the chips featured inside.

Hi-res digital photos are always helpful :-)  If you can take photos,
please post them to a website (like bttv-gallery) and post links here.

Regards,

Mike


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Jeff Rosenberg
I think Patrick already has a driver for it?
   
  If you could point me towards the driver, that would be awesome.
   
  Thanks for all the help !!!
   
  Jeff
  
.Markus Rechberger [EMAIL PROTECTED] wrote:
  On 11/15/07, Michael Krufky wrote:
 Markus Rechberger wrote:
  On 11/15/07, Michael Krufky wrote:
 
  Jeff Rosenberg wrote:
 
  I just purchase the PCTV HD Ultimate Stick. I decided upon this since
 it
 
  supported clear QAM and had flash space for recording to the stick in
  addition to the hardrive. I read that the PCTV HD Pro Stick was
 supported
  with the latest Experimental build based on the em2883 chipset. I took
 the
  risk and went with the Ultimate instead of the Pro.
 
  [snip]
 
 
  Any chance that there will be support for this newly released USB
 stick
 
  ?
 
  You wont find native support for this in any Linux Distribution's native
  kernel anytime soon.
 
  Your best bet, in this case, is to look at Markus' experimental
 repository.
  I don't think that he has support for this exact device yet, but he does
  have most of the pieces required.
 
  #1) You need em2880-dvb support, which is not yet in the master v4l-dvb
  development branch
 
  #2) (I think) you'll need an xc5000 driver, also not yet merged into the
  v4l-dvb master branch.
 
  You might be able to assemble the right pieces of code together, but I
 don't
  know where you'll find it all at this time.
 
  Given a few months (or weeks, in a perfect world) time, the situation may
  become clearer.
 
 
 
  Michael,
 
  this is no em28xx based device, I guess it's a dibcom one.
 Ah, OK. Thanks, Markus.

 In which case, bridge-wise, it may be a bit easier (or more difficult,
 depending) than I thought.

 Jeff, it might be helpful if you could crack open the device and tell us
 all of the chips featured inside.

 Hi-res digital photos are always helpful :-) If you can take photos,
 please post them to a website (like bttv-gallery) and post links here.


I think that's not really necessary, my one is already open (I could
take a foto if not already available) although I think Patrick already
has a driver for it?
The usb device includes a hub and shows up 2 more usbids on the host,
one is a storage device, the other one is the dibcom tuner as far as I
remember.

Markus


   
-
Never miss a thing.   Make Yahoo your homepage.___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Markus Rechberger
On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote:
 Markus Rechberger wrote:
  On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote:
 
  Jeff Rosenberg wrote:
 
  I just purchase the PCTV HD Ultimate Stick.  I decided upon this since
 it
 
  supported clear QAM and had flash space for recording to the stick in
  addition to the hardrive.  I read that the PCTV HD Pro Stick was
 supported
  with the latest Experimental build based on the em2883 chipset.  I took
 the
  risk and went with the Ultimate instead of the Pro.
 
  [snip]
 
 
Any chance that there will be support for this newly released USB
 stick
 
  ?
 
  You wont find native support for this in any Linux Distribution's native
  kernel anytime soon.
 
  Your best bet, in this case, is to look at Markus' experimental
 repository.
  I don't think that he has support for this exact device yet, but he does
  have most of the pieces required.
 
  #1) You need em2880-dvb support, which is not yet in the master v4l-dvb
  development branch
 
  #2) (I think) you'll need an xc5000 driver, also not yet merged into the
  v4l-dvb master branch.
 
  You might be able to assemble the right pieces of code together, but I
 don't
  know where you'll find it all at this time.
 
  Given a few months (or weeks, in a perfect world) time, the situation may
  become clearer.
 
 
 
  Michael,
 
  this is no em28xx based device, I guess it's a dibcom one.
 Ah, OK.  Thanks, Markus.

 In which case, bridge-wise, it may be a bit easier (or more difficult,
 depending) than I thought.

 Jeff, it might be helpful if you could crack open the device and tell us
 all of the chips featured inside.

 Hi-res digital photos are always helpful :-)  If you can take photos,
 please post them to a website (like bttv-gallery) and post links here.


I think that's not really necessary, my one is already open (I could
take a foto if not already available) although I think Patrick already
has a driver for it?
The usb device includes a hub and shows up 2 more usbids on the host,
one is a storage device, the other one is the dibcom tuner as far as I
remember.

Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] mt20xx.c code bugs!

2007-11-15 Thread Mauro Carvalho Chehab

Em Qui, 2007-11-15 às 09:43 +0800, kevin liu escreveu:
 Dear everyone:
 I am reading v4l2 tuner part code these days, when I come to mt20xx.c,
 in microtune_init(), the use of the char pointer name maybe cause some
 fatal error sometimes for this state:
 ++
 507 name = unknown;
 ++
 while pointer name doesn't have its memory.
 And I wonder why gcc can't give any warnings?

Because this works properly and it has a valid syntax/semantic.

Any C compiler will add unknown string to the data segment and 'name'
will point to this area.
 
Cheers,
Mauro


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] A link DTU advice needed

2007-11-15 Thread Antti Palosaari

moi
attached patch should fix it. I have been too busy to find proper 
solution for ZL10353, though I now know how it should be done.


regards
Antti Palosaari

Dag Nygren wrote:

Hi again,

is there anything I can do to help debugging the
A-link DTU USB stick Tuning failed problem?
The stick seems to be the old model without the (m),
using the modules:

qt1010 
zl10353 
dvb_usb_gl861
dvb_usb 


and now tunes to 3 of the 4 MUX:es we have here
in Espoo, Finland but no deal with one of them whatever I do.

Best
Dag


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb



--
  |||
 (0-0)
-oOO--(_)--OOo-
 http://palosaari.fi/
-Kahta asiaa en ymmärrä.. C-kielen syntaksi ja naisten logiikka..

diff -r 496bf62d9e03 linux/drivers/media/dvb/dvb-usb/au6610.c
--- a/linux/drivers/media/dvb/dvb-usb/au6610.c	Thu Nov 15 12:07:19 2007 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/au6610.c	Thu Nov 15 17:02:19 2007 +0200
@@ -123,10 +123,23 @@ static int au6610_identify_state(struct 
 	return 0;
 }
 
+static int au6610_zl10353_demod_init(struct dvb_frontend *fe)
+{
+	u8 unk1[] = { 0x8e , 0x00 };
+	u8 unk2[] = { 0x90, 0x00, 0xff, 0xff, 0x00, 0xff, 0x3f, 0x3f };
+
+	zl10353_write_(fe, unk1, sizeof(unk1));
+	zl10353_write_(fe, unk2, sizeof(unk2));
+
+	return 0;
+}
+
 static struct zl10353_config au6610_zl10353_config = {
 	.demod_address = 0x0f,
 	.no_tuner = 1,
 	.parallel_ts = 1,
+	.agc2 = 1,
+	.demod_init = au6610_zl10353_demod_init
 };
 
 static int au6610_zl10353_frontend_attach(struct dvb_usb_adapter *adap)
diff -r 496bf62d9e03 linux/drivers/media/dvb/dvb-usb/gl861.c
--- a/linux/drivers/media/dvb/dvb-usb/gl861.c	Thu Nov 15 12:07:19 2007 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/gl861.c	Thu Nov 15 17:02:19 2007 +0200
@@ -45,6 +45,8 @@ static int gl861_i2c_msg(struct dvb_usb_
 		return -EINVAL;
 	}
 
+	udelay(10); /* avoid usb i2c timeouts */
+
 	return usb_control_msg(d-udev, usb_rcvctrlpipe(d-udev, 0), req, type,
 			   value, index, rbuf, rlen, 2000);
 }
@@ -100,10 +102,23 @@ static int gl861_identify_state(struct u
 	return 0;
 }
 
+static int gl861_zl10353_demod_init(struct dvb_frontend *fe)
+{
+	u8 unk1[] = { 0x8e , 0x00 };
+	u8 unk2[] = { 0x90, 0x00, 0xff, 0xff, 0x00, 0xff, 0x3f, 0x3f };
+
+	zl10353_write_(fe, unk1, sizeof(unk1));
+	zl10353_write_(fe, unk2, sizeof(unk2));
+
+	return 0;
+}
+
 static struct zl10353_config gl861_zl10353_config = {
 	.demod_address = 0x0f,
 	.no_tuner = 1,
 	.parallel_ts = 1,
+	.agc2 = 1,
+	.demod_init = gl861_zl10353_demod_init
 };
 
 static int gl861_frontend_attach(struct dvb_usb_adapter *adap)
@@ -156,6 +171,7 @@ static int gl861_probe(struct usb_interf
 }
 
 static struct usb_device_id gl861_table [] = {
+//		{ USB_DEVICE(USB_VID_MSI, 123) },
 		{ USB_DEVICE(USB_VID_MSI, USB_PID_MSI_MEGASKY580_55801) },
 		{ USB_DEVICE(USB_VID_ALINK, USB_VID_ALINK_DTU) },
 		{ }		/* Terminating entry */
diff -r 496bf62d9e03 linux/drivers/media/dvb/frontends/qt1010.c
--- a/linux/drivers/media/dvb/frontends/qt1010.c	Thu Nov 15 12:07:19 2007 -0200
+++ b/linux/drivers/media/dvb/frontends/qt1010.c	Thu Nov 15 17:02:19 2007 +0200
@@ -28,7 +28,7 @@ MODULE_PARM_DESC(debug, Turn on/off deb
 
 #define dprintk(args...) \
 	do { \
-		if (debug) printk(KERN_DEBUG QT1010:  args); \
+		if (debug) printk(KERN_DEBUG qt1010:  args); \
 	} while (0)
 
 /* read single register */
@@ -42,7 +42,7 @@ static int qt1010_readreg(struct qt1010_
 	};
 
 	if (i2c_transfer(priv-i2c, msg, 2) != 2) {
-		printk(KERN_WARNING qt1010 I2C read failed\n);
+		printk(KERN_WARNING qt1010: i2c read failed (reg:%02x)\n, reg);
 		return -EREMOTEIO;
 	}
 	return 0;
@@ -56,12 +56,13 @@ static int qt1010_writereg(struct qt1010
 			   .flags = 0, .buf = buf, .len = 2 };
 
 	if (i2c_transfer(priv-i2c, msg, 1) != 1) {
-		printk(KERN_WARNING qt1010 I2C write failed\n);
+		printk(KERN_WARNING qt1010: i2c write failed (reg:%02x val:%02x)\n, reg, val);
 		return -EREMOTEIO;
 	}
 	return 0;
 }
 
+#if 0
 /* dump all registers */
 static void qt1010_dump_regs(struct qt1010_priv *priv)
 {
@@ -71,7 +72,7 @@ static void qt1010_dump_regs(struct qt10
 	for (reg = 0; ; reg++) {
 		if (reg % 16 == 0) {
 			if (reg)
-printk(%s\n, buf);
+dprintk(%s\n, buf);
 			sprintf(buf, %02x: , reg);
 		}
 		if (qt1010_readreg(priv, reg, val) == 0)
@@ -82,333 +83,579 @@ static void qt1010_dump_regs(struct qt10
 		if (reg == 0x2f)
 			break;
 	}
-	printk(%s\n, buf);
-}
-
-static int qt1010_set_params(struct dvb_frontend *fe,
-			 struct dvb_frontend_parameters *params)
-{
-	struct qt1010_priv *priv;
+	dprintk(%s\n, buf);
+}
+#endif
+
+/* read register in the loop until mask match or timeout occurs */
+static int qt1010_readreg_looping(struct qt1010_priv *priv, u8 reg, u8 mask, u8 *val)
+{
+	int err = 0;
+	u8 tmpval;
+	unsigned long timeout;
+
+	timeout = jiffies + msecs_to_jiffies(30);

Re: [linux-dvb] [v4l-dvb-maintainer] HVR1500 status

2007-11-15 Thread Mauro Carvalho Chehab

Em Ter, 2007-11-13 às 15:05 -0500, Steven Toth escreveu:
 Michel Ludwig wrote:
  Hi Steven,
  
  On Tuesday 13 November 2007 17:20:56 you wrote:
  It's worth pointing out the current state of the HVR1500 support under
  Linux.
 
  1. None of it's functions are currently supported, they are awaiting a
  xc3028 driver change. I have some patchsets which will add support, but
  they reply on the xc3028 change.
  
  What changes are you waiting for exactly?
 
 The xc3028 driver needs more firmware for different I/F's to support the 
 s5h1409 for ATSC.
 
 Mauro said he'd add them, I offered to integrate once done.

I've added today the capability of supporting the newer I/F's at
tuner-xc2028 driver. Still, we need to work on it to provide a nice
interface inside DVB core and to userspace.
 
Cheers,
Mauro


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Patrick Boettcher
Hi all,

the driver is already merged inside the main v4l-dvb. Except that the USB 
IDs are not the same. (I'm refering to your previous email saying the PID 
is 0x0233 - whereas the one of the device I had was 0x228 and it was 
called DVB-T Flash).

To give it a try, just go the dib0700_devices.c and add your IDs in the 
stk7070p-part.

good luck,
Patrick.

On Thu, 15 Nov 2007, Jeff Rosenberg wrote:

 I think Patrick already has a driver for it?

   If you could point me towards the driver, that would be awesome.

   Thanks for all the help !!!

   Jeff
   
 .Markus Rechberger [EMAIL PROTECTED] wrote:
   On 11/15/07, Michael Krufky wrote:
  Markus Rechberger wrote:
   On 11/15/07, Michael Krufky wrote:
  
   Jeff Rosenberg wrote:
  
   I just purchase the PCTV HD Ultimate Stick. I decided upon this since
  it
  
   supported clear QAM and had flash space for recording to the stick in
   addition to the hardrive. I read that the PCTV HD Pro Stick was
  supported
   with the latest Experimental build based on the em2883 chipset. I took
  the
   risk and went with the Ultimate instead of the Pro.
  
   [snip]
  
  
   Any chance that there will be support for this newly released USB
  stick
  
   ?
  
   You wont find native support for this in any Linux Distribution's native
   kernel anytime soon.
  
   Your best bet, in this case, is to look at Markus' experimental
  repository.
   I don't think that he has support for this exact device yet, but he does
   have most of the pieces required.
  
   #1) You need em2880-dvb support, which is not yet in the master v4l-dvb
   development branch
  
   #2) (I think) you'll need an xc5000 driver, also not yet merged into the
   v4l-dvb master branch.
  
   You might be able to assemble the right pieces of code together, but I
  don't
   know where you'll find it all at this time.
  
   Given a few months (or weeks, in a perfect world) time, the situation may
   become clearer.
  
  
  
   Michael,
  
   this is no em28xx based device, I guess it's a dibcom one.
  Ah, OK. Thanks, Markus.
 
  In which case, bridge-wise, it may be a bit easier (or more difficult,
  depending) than I thought.
 
  Jeff, it might be helpful if you could crack open the device and tell us
  all of the chips featured inside.
 
  Hi-res digital photos are always helpful :-) If you can take photos,
  please post them to a website (like bttv-gallery) and post links here.
 
 
 I think that's not really necessary, my one is already open (I could
 take a foto if not already available) although I think Patrick already
 has a driver for it?
 The usb device includes a hub and shows up 2 more usbids on the host,
 one is a storage device, the other one is the dibcom tuner as far as I
 remember.
 
 Markus
 
 

 -
 Never miss a thing.   Make Yahoo your homepage.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread mkrufky
Markus Rechberger wrote:
 I think that's not really necessary, my one is already open (I could
 take a foto if not already available) although I think Patrick already
 has a driver for it?
 The usb device includes a hub and shows up 2 more usbids on the host,
 one is a storage device, the other one is the dibcom tuner as far as I
 remember.
   
Interesting... In which case, then I'm probably wrong, and it's not an 
xc5000.  Do you know WHICH dibcom tuner?  Is it a 7070?

-Mike

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Markus Rechberger
On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote:
 Jeff Rosenberg wrote:
  I just purchase the PCTV HD Ultimate Stick.  I decided upon this since it
 supported clear QAM and had flash space for recording to the stick in
 addition to the hardrive.  I read that the PCTV HD Pro Stick was supported
 with the latest Experimental build based on the em2883 chipset.  I took the
 risk and went with the Ultimate instead of the Pro.

 [snip]

Any chance that there will be support for this newly released USB stick
 ?

 You wont find native support for this in any Linux Distribution's native
 kernel anytime soon.

 Your best bet, in this case, is to look at Markus' experimental repository.
 I don't think that he has support for this exact device yet, but he does
 have most of the pieces required.

 #1) You need em2880-dvb support, which is not yet in the master v4l-dvb
 development branch

 #2) (I think) you'll need an xc5000 driver, also not yet merged into the
 v4l-dvb master branch.

 You might be able to assemble the right pieces of code together, but I don't
 know where you'll find it all at this time.

 Given a few months (or weeks, in a perfect world) time, the situation may
 become clearer.


Michael,

this is no em28xx based device, I guess it's a dibcom one.

regards,
Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Markus Rechberger
On 11/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Markus Rechberger wrote:
  I think that's not really necessary, my one is already open (I could
  take a foto if not already available) although I think Patrick already
  has a driver for it?
  The usb device includes a hub and shows up 2 more usbids on the host,
  one is a storage device, the other one is the dibcom tuner as far as I
  remember.
 
 Interesting... In which case, then I'm probably wrong, and it's not an
 xc5000.  Do you know WHICH dibcom tuner?  Is it a 7070?


I have no idea last time when I looked at it was around 6 months ago.
I'll check it when I'm at home.

Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Jeff Rosenberg
The Pinnacle PCTV HD Ultimate stick just came out (a couple of weeks ago).  
   
  I looked in the Windoze .inf files and it appears that the drivers used are 
the same for the PCTV HD Pro and PCTV HD Ultimate.  I looked in the 
developmental build of DVB and saw that in the file em288x-cards.c there was 
the correct USB_DEVICE # of 0x2304 but the next value was not 0x0233.  I 
changed it and recompiled.  
   
  When the driver loads it now has the following message in the kernel buffer 
log:
   
  FIXME:em28xx_i2c_send_bytes(c2): write failed:
   
   
  Any ideas ?  I am pretty sure the correct driver is the em28xx.
   
  Regards,
  Jeff
   
  

Markus Rechberger [EMAIL PROTECTED] wrote:
  On 11/15/07, [EMAIL PROTECTED] wrote:
 Markus Rechberger wrote:
  I think that's not really necessary, my one is already open (I could
  take a foto if not already available) although I think Patrick already
  has a driver for it?
  The usb device includes a hub and shows up 2 more usbids on the host,
  one is a storage device, the other one is the dibcom tuner as far as I
  remember.
 
 Interesting... In which case, then I'm probably wrong, and it's not an
 xc5000. Do you know WHICH dibcom tuner? Is it a 7070?


I have no idea last time when I looked at it was around 6 months ago.
I'll check it when I'm at home.

Markus


   
-
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread mkrufky
Jeff Rosenberg wrote:
 The Pinnacle PCTV HD Ultimate stick just came out (a couple of weeks 
 ago). 
  
 I looked in the Windoze .inf files and it appears that the drivers 
 used are the same for the PCTV HD Pro and PCTV HD Ultimate.  I looked 
 in the developmental build of DVB and saw that in the file 
 em288x-cards.c there was the correct USB_DEVICE # of 0x2304 but the 
 next value was not 0x0233.  I changed it and recompiled. 
  
 When the driver loads it now has the following message in the kernel 
 buffer log:
  
 FIXME:em28xx_i2c_send_bytes(c2): write failed:
  
  
 Any ideas ?  I am pretty sure the correct driver is the em28xx.

As both Patrick and Markus explained, this device is not empia hardware, 
and the code that supports it is located inside dib0700_devices.c -- 
you'll want to edit dvb-usb-ids.h

Also, please do not top-post.

-Mike

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Lifeview PCI TRIO DVB-S problems: can not tune half transponders, low SS and SNR

2007-11-15 Thread Vangelis Nonas
Hello Hermann,

Your suggestion helped a lot indeed. I can now get about 2000 services 
on Hotbird using scan from dvb-apps. Moreover the reception is better, 
SNR is about 90%, SS is around 50% or more and I dont often get high 
error rates. I also tested viewing channels and I can now see channels 
that didn't exist before. One minor negative side effect is that 
channelscan on vdr crashes.

However, I still can not tume to 12 transponders on hotbird (out of 94 
in total). These are the failing transponders:
  tune to: 11334:h:S0.0W:27500: (tuning failed)
  tune to: 11373:h:S0.0W:27500: (tuning failed)
  tune to: 11432:v:S0.0W:27500: (tuning failed)
  tune to: 12264:v:S13.0E:27500: (tuning failed)
  tune to: 11954:h:S19.2E:27500: (tuning failed)
  tune to: 11597:v:S19.2E:22000: (tuning failed)
  tune to: 12480:v:S19.2E:27500: (tuning failed)
  tune to: 12500:v:S13.0E:27500: (tuning failed)
  tune to: 11533:v:S13.0E:27500: (tuning failed)
  tune to: 11996:v:S13.0E:27500: (tuning failed)
  tune to: 12722:h:S68.5E:26657: (tuning failed)
  tune to: 11344:h:S8.0W:27500: (tuning failed)

Although the DVB-S part of the card is now much more usable. I feel 
there is still room for improvement of the Linux driver.

Any suggestions on how  to improve the reception further?

I have to mention here that I have a single LNB on my installation, no 
disecq, however the patch helped a lot.

Thank you
Vagelis




hermann pitton wrote:
 Hi,

 Am Mittwoch, den 14.11.2007, 21:36 + schrieb Vangelis Nonas:
   
 Hello,

 I have been trying to use the DVB-S frontend of lifeview pci trio to 
 scan and watch channels from Hotbird. I have the following two problems:
 

 please try again with that patch applied and report again.
 http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html

 I don't get a Medion Quad, not in the original triple bus master PCI
 slot, to behave well on supplying voltage and tone on a ISL6405ER, but
 with the RF loop through from an external receiver providing the missing
 I have more than thousand broadcasts available from Hotbird-13.OE.

 Cheers,
 Hermann


   
 A) When I scan (using the scan utility from the hg tree, or the scan 
 utility of my distribution) almost half of the transponders can not be 
 tuned. I get the error tuning failed and of course almost half of 
 Hotbitd's channels are not found. My transponders file is correct 
 because it comes from my set top box which also runs linux :) or from hg 
 dvb-apps or from other dvb software (e.g. prog dvb). I have also tried 
 scanning with channelscan plugin of vdr with the same results. When I 
 use kaffeine to scan for channels I get an Oops. I am attaching the 
 output of my scan command using the scan util from dvb-apps fresh hg 
 pull. (scan.log.gz)

 B) When I use ready made channel lists downloaded from the internet I 
 get low SNR and SS on almost half of the transponders and in some cases 
 high error rate. When I use szap on those transponders I can not get a lock.

 My kernel is:
 Linux vagoshome 2.6.22-gentoo-r9 #1 SMP Tue Oct 30 16:02:08 UTC 2007 
 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ AuthenticAMD GNU/Linux
 with a fresh hg mercurial pull and installation.

 I attach also my dmesg as dmesg.log.gz

 I also attach my lsmod as lsmod.log.gz

 In case you need more info about the Oops I get when I scan from 
 Kaffeine, I can reproduce it and send you the output.

 The card works correctly under windows on the same machine, sat cable, dish.

 Thank you
 Vagelis

 



 .

   


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread CityK
[EMAIL PROTECTED] wrote:
 Jeff Rosenberg wrote:
   
 The Pinnacle PCTV HD Ultimate stick just came out (a couple of weeks 
 ago). 
  
 I looked in the Windoze .inf files and it appears that the drivers 
 used are the same for the PCTV HD Pro and PCTV HD Ultimate.  I looked 
 in the developmental build of DVB and saw that in the file 
 em288x-cards.c there was the correct USB_DEVICE # of 0x2304 but the 
 next value was not 0x0233.  I changed it and recompiled. 
  
 When the driver loads it now has the following message in the kernel 
 buffer log:
  
 FIXME:em28xx_i2c_send_bytes(c2): write failed:
  
  
 Any ideas ?  I am pretty sure the correct driver is the em28xx.
 

 As both Patrick and Markus explained, this device is not empia hardware, 
 and the code that supports it is located inside dib0700_devices.c -- 
 you'll want to edit dvb-usb-ids.h

 Also, please do not top-post.
   

However, Jeff will still need xc5000 support  the dib0700 is purely
the usb bridge  while, I'm guessing that the stick uses a xc5000, I
believe that it is indeed a pretty safe bet (given other factors)

 Interesting... In which case, then I'm probably wrong, and it's not an 
 xc5000.  Do you know WHICH dibcom tuner?  Is it a 7070?
   

It definitely won't be from Dibicom --- no support for ATSC


 Hi-res digital photos are always helpful  :-)   If you can take photos,
 please post them to a website (like bttv-gallery) and post links here.

Jeff, if you take a photo, could you please up load it to the LinuxTV wiki:
http://www.linuxtv.org/wiki/index.php/Special:Upload
(Please also use an appropriate filename)

If you wish to submit it too bttv-gallery too, go ahead, but
i) as was noted on the m/l last month, Gunther (bttv-gallery's
proprietor) hasn't been around for ages
ii) doing so alone would continue the trend of a fractured distribution
of information regarding Linux  PC tvtuners.

Linuxtv should become the one stop shop. We don't need to compete with
ourselves, so lets make requests for photos to the wiki please.


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] AF9015 (A-Link DTU(m)) test results

2007-11-15 Thread arris
Am Dienstag 13 November 2007 schrieb Peter Parkkali:
 Hi all,

 I tried to run the af9015 driver from http://jusst.de/hg/af901x/ on the
 A-Link DTU (m) dongle (USB ID 15a4:9016).  The firmware seems to load
 fine, but there are a few errors from mt2060, after which the driver
 apparently tries to reload the firmware. Running dvbscan with the
 fi-Espoo scan file (which apparently applies for Helsinki too(?)) seems
 to get stuck without any results.

 The driver version is 40fc9491ff06, from Sun, 11 Nov 2007 00:47:17
 +0400), with http://jusst.de/manu/fw/AFA/dvb-usb-af9015.fw_a-link saved
 to /lib/firmware/2.6.22-14-server/dvb-usb-af9015.fw .

 The kernel is 2.6.22-14-server from Ubuntu, version 2.6.22-14.46

 The complete kernel log is at http://pfp.iki.fi/af9015_results_20071112.txt

think it is also an (non fatal) error in the sequence check

Nov 12 23:55:26 crm-114 kernel: [  180.55] af9015_biu_read: Sequence 
error! Seq RD=0xff, Expect=0x00
Nov 12 23:55:26 crm-114 kernel: [  180.55] af9015_biu_read: Read Error

in case ucSN = 0 (ucSN - 1) is 0x and not 0xff (as buf[0])

if (buf[0] != (ucSN - 1)) should be if (buf[0] != (u8)(ucSN - 1))


zsolt

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DViCO Dual Digital 4 and remote

2007-11-15 Thread Robert Backhaus
On Nov 15, 2007 10:34 PM, Michael Krufky [EMAIL PROTECTED] wrote:
 Robert Backhaus wrote:
  Big thanks to all the very smart people who are working on this. (Big
  Lartings to the manufacturers who are _NOT!!!)

 That's not cool.

 DViCO is being very helpful.

 -Mike


In that case, I apologise. Still, we would like them to employ staff to produce
patches (or even be comitters), making sure the support is there before the
devices are released (wishing for a perfect world...).
That said, I realise that getting any support from the manufacturer is better
than average, and invaluable; so I publicly apologise, and thank DViCO for
their assistance.

Robert Backhaus.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Lifeview PCI TRIO DVB-S problems: can not tune half transponders, low SS and SNR

2007-11-15 Thread hermann pitton
Hi Vangelis!

Am Donnerstag, den 15.11.2007, 21:00 + schrieb Vangelis Nonas:
 Hello Hermann,
 
 Your suggestion helped a lot indeed. I can now get about 2000 services 
 on Hotbird using scan from dvb-apps. Moreover the reception is better, 
 SNR is about 90%, SS is around 50% or more and I dont often get high 
 error rates. I also tested viewing channels and I can now see channels 
 that didn't exist before. One minor negative side effect is that 
 channelscan on vdr crashes.
 
 However, I still can not tume to 12 transponders on hotbird (out of 94 
 in total). These are the failing transponders:
   tune to: 11334:h:S0.0W:27500: (tuning failed)
   tune to: 11373:h:S0.0W:27500: (tuning failed)
   tune to: 11432:v:S0.0W:27500: (tuning failed)
   tune to: 12264:v:S13.0E:27500: (tuning failed)
   tune to: 11954:h:S19.2E:27500: (tuning failed)
   tune to: 11597:v:S19.2E:22000: (tuning failed)
   tune to: 12480:v:S19.2E:27500: (tuning failed)
   tune to: 12500:v:S13.0E:27500: (tuning failed)
   tune to: 11533:v:S13.0E:27500: (tuning failed)
   tune to: 11996:v:S13.0E:27500: (tuning failed)
   tune to: 12722:h:S68.5E:26657: (tuning failed)
   tune to: 11344:h:S8.0W:27500: (tuning failed)
 
 Although the DVB-S part of the card is now much more usable. I feel 
 there is still room for improvement of the Linux driver.
 
 Any suggestions on how  to improve the reception further?
 
 I have to mention here that I have a single LNB on my installation, no 
 disecq, however the patch helped a lot.
 
 Thank you
 Vagelis
 

I'm a bloody beginner on DVB-S and have a simple dish just since a few
days.

The reason for that is, that we have the code from Andrew since long for
the newer silicon stuff, also saa7134 triple devices, which should
support DVB-S as well since for over two years, but we don't make much
progress, since only the Trio seems to be supported and on others not
even testing happens.

For sure I can see, that whole fleets of such triple stuff are coming in
from all seas.

For now, I'm only on a device, hard enough to barely hold it in a not
triple capable PCI slot, and likely not fully initialized for the ISL
stuff.

I'm looking forward to get something normal next and then maybe I can
contribute to your questions in the future.

For now, try to exchange with people on the same hardware than you and
hope for hints of the DVB guys.

BTW, that outstanding patch is committed since 7 days to v4l-dvb master.

For what I can see the patchlet from me, attaching the ISL6421 for the
ISL6405 on the Medion Quad should not do any harm, quite the same for
the first LNB.

If somebody recognizes any possible risks to the hardware, please say
so. I don't.

Cheers,
Hermann


 


 
 hermann pitton wrote:
  Hi,
 
  Am Mittwoch, den 14.11.2007, 21:36 + schrieb Vangelis Nonas:

  Hello,
 
  I have been trying to use the DVB-S frontend of lifeview pci trio to 
  scan and watch channels from Hotbird. I have the following two problems:
  
 
  please try again with that patch applied and report again.
  http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
 
  I don't get a Medion Quad, not in the original triple bus master PCI
  slot, to behave well on supplying voltage and tone on a ISL6405ER, but
  with the RF loop through from an external receiver providing the missing
  I have more than thousand broadcasts available from Hotbird-13.OE.
 
  Cheers,
  Hermann
 
 

  A) When I scan (using the scan utility from the hg tree, or the scan 
  utility of my distribution) almost half of the transponders can not be 
  tuned. I get the error tuning failed and of course almost half of 
  Hotbitd's channels are not found. My transponders file is correct 
  because it comes from my set top box which also runs linux :) or from hg 
  dvb-apps or from other dvb software (e.g. prog dvb). I have also tried 
  scanning with channelscan plugin of vdr with the same results. When I 
  use kaffeine to scan for channels I get an Oops. I am attaching the 
  output of my scan command using the scan util from dvb-apps fresh hg 
  pull. (scan.log.gz)
 
  B) When I use ready made channel lists downloaded from the internet I 
  get low SNR and SS on almost half of the transponders and in some cases 
  high error rate. When I use szap on those transponders I can not get a 
  lock.
 
  My kernel is:
  Linux vagoshome 2.6.22-gentoo-r9 #1 SMP Tue Oct 30 16:02:08 UTC 2007 
  i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ AuthenticAMD GNU/Linux
  with a fresh hg mercurial pull and installation.
 
  I attach also my dmesg as dmesg.log.gz
 
  I also attach my lsmod as lsmod.log.gz
 
  In case you need more info about the Oops I get when I scan from 
  Kaffeine, I can reproduce it and send you the output.
 
  The card works correctly under windows on the same machine, sat cable, 
  dish.
 
  Thank you
  Vagelis
 



___
linux-dvb mailing list
linux-dvb@linuxtv.org

Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Express?

2007-11-15 Thread Michael Krufky
[EMAIL PROTECTED] wrote:
 Hi dvb list,
 
 I'm in need of another dual tuner card and am currently debating between
 getting another DD4 or getting one of the newer PCIe cards.  Can anyone 
 confirm
 that the PCIe Dual Express works with linux (negative responses also 
 helpful)? 
 I would ideally prefer to go the PCIe path but given the amount of time I have
 already spent getting the DD4 working in Australia I would prefer not to have
 to do it again for a PCIe variant without some hope of being successful. 
 Failing an affirmative does anybody in Australia have a card they're willing 
 to
 loan me for a few weeks to see if I can get it going?

DVB-T Dual Express is not yet supported.

Some people have been emailing me privately about this  --  too many people for 
me to respond to... Hopefully they'll see this message.

There is a new xceive driver in the master branch, but it's lacking a dvb entry 
point at this time... Once that's done, it will pave the way for cx23885 + 
xc3028 device support.  After support for the Hauppauge HVR1500 (atsc only) is 
added, it will be easier to add support for other cx23885 + xc3028 devices, 
such as the DViCO DVB-T Dual Express.

A while back, I was sending out test patches that used the xc3028-fe module, 
from the infamous xc-bluebird.patch ...  I am no longer going to bother with 
this method, since there finally is an xceive driver in the master development 
branch.

Once the xceive dvb entry point is ready, I (or Chris) will re-spin the Dual 
Digital 4 / DVB-T Nano2 support to use the new tuner module.

Things are moving along...

-Mike

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] mt20xx.c code bugs!

2007-11-15 Thread kevin liu
You mean all the c compilers will give 'unknown' a special process???


On Nov 15, 2007 11:04 PM, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote:

 Em Qui, 2007-11-15 às 09:43 +0800, kevin liu escreveu:

  Dear everyone:
  I am reading v4l2 tuner part code these days, when I come to mt20xx.c,
  in microtune_init(), the use of the char pointer name maybe cause some
  fatal error sometimes for this state:
  ++
  507 name = unknown;
  ++
  while pointer name doesn't have its memory.
  And I wonder why gcc can't give any warnings?

 Because this works properly and it has a valid syntax/semantic.

 Any C compiler will add unknown string to the data segment and 'name'
 will point to this area.

 Cheers,
 Mauro



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] DViCO FusionHDTV DVB-T Dual Express?

2007-11-15 Thread ras243-dvb
Hi dvb list,

I'm in need of another dual tuner card and am currently debating between
getting another DD4 or getting one of the newer PCIe cards.  Can anyone confirm
that the PCIe Dual Express works with linux (negative responses also helpful)? 
I would ideally prefer to go the PCIe path but given the amount of time I have
already spent getting the DD4 working in Australia I would prefer not to have
to do it again for a PCIe variant without some hope of being successful. 
Failing an affirmative does anybody in Australia have a card they're willing to
loan me for a few weeks to see if I can get it going?

Roger.


  Make the switch to the world's best email. Get the new Yahoo!7 Mail now. 
http://au.yahoo.com/worldsbestmail/viagra/index.html



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] mt20xx.c code bugs!

2007-11-15 Thread Mauro Carvalho Chehab

Em Sex, 2007-11-16 às 09:08 +0800, kevin liu escreveu:
 You mean all the c compilers will give 'unknown' a special process???

Huh?

I mean:

{
char *name = unknown;

and 

{
char *name;

/* some code */

name = unknown;

are equivalent.

Cheers,
Mauro


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick

2007-11-15 Thread Markus Rechberger
On 11/15/07, CityK [EMAIL PROTECTED] wrote:
 [EMAIL PROTECTED] wrote:
  Jeff Rosenberg wrote:
 
  The Pinnacle PCTV HD Ultimate stick just came out (a couple of weeks
  ago).
 
  I looked in the Windoze .inf files and it appears that the drivers
  used are the same for the PCTV HD Pro and PCTV HD Ultimate.  I looked
  in the developmental build of DVB and saw that in the file
  em288x-cards.c there was the correct USB_DEVICE # of 0x2304 but the
  next value was not 0x0233.  I changed it and recompiled.
 
  When the driver loads it now has the following message in the kernel
  buffer log:
 
  FIXME:em28xx_i2c_send_bytes(c2): write failed:
 
 
  Any ideas ?  I am pretty sure the correct driver is the em28xx.
 
 
  As both Patrick and Markus explained, this device is not empia hardware,
  and the code that supports it is located inside dib0700_devices.c --
  you'll want to edit dvb-usb-ids.h
 
  Also, please do not top-post.
 

 However, Jeff will still need xc5000 support  the dib0700 is purely
 the usb bridge  while, I'm guessing that the stick uses a xc5000, I
 believe that it is indeed a pretty safe bet (given other factors)

  Interesting... In which case, then I'm probably wrong, and it's not an
  xc5000.  Do you know WHICH dibcom tuner?  Is it a 7070?
 

 It definitely won't be from Dibicom --- no support for ATSC


  Hi-res digital photos are always helpful  :-)   If you can take photos,
  please post them to a website (like bttv-gallery) and post links here.

 Jeff, if you take a photo, could you please up load it to the LinuxTV wiki:
 http://www.linuxtv.org/wiki/index.php/Special:Upload
 (Please also use an appropriate filename)

 If you wish to submit it too bttv-gallery too, go ahead, but
 i) as was noted on the m/l last month, Gunther (bttv-gallery's
 proprietor) hasn't been around for ages
 ii) doing so alone would continue the trend of a fractured distribution
 of information regarding Linux  PC tvtuners.

 Linuxtv should become the one stop shop. We don't need to compete with
 ourselves, so lets make requests for photos to the wiki please.


The outcome is it's an Empiatech device with completly new components
on it. It's hard to programm... although they'll submit the specs
(NDA) as soon as I'm done with the current project.

Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] libdvben50221 docs and debuging

2007-11-15 Thread Ben Bucksch
I am trying to use libdvben50221 from linuxtv-dvb-apps (version 20070114
from Gentoo) to drive the CI/CA/CAM for some encrypted channels. I get
some printouts on the console, but it doesn't work, the channel is not
decrypted.

CAM supports the following ca system ids:
0x1702
0x1722
0x1762
0x4a20
0x0500
CAM Application type: 01
CAM Application manufacturer: 4a20
CAM Manufacturer code: 4a20
CAM Menu string: AlphaCrypt Light

I sometimes also get
Received new PMT - sending to CAM...
between the 0x0500 and CAM Application type: 01, which is promising,
but decryption still doesn't work. I also don't know why I sometimes get
that line and sometimes not.

The same card and CI/CAM works with MythTV. zap also seems to work.

Most likely I'm doing something wrong, but I don't know what I am
supposed to do, as there is absolutely no documentation / howto. I used
the zap code as example (and use the unchanged zap_ca.* files), but
still I must be doing something wrong.

I'm at a loss here.
Can somebody please give some hints on how to debug this, and/or
describe what I'm supposed to do?

Relevant source attached.

Thanks in advance,

Ben


P.S. Sometimes, at the first tune(s), I also get, before that:

en50221_tl_handle_sb: Received T_SB for connection not in T_STATE_ACTIVE
from module on slot 00

en50221_stdcam_llci_poll: Error reported by stack:-7

I don't remember whether I get this particular error with the normal
DVB-S card and driver or only with the SkyStar HD DVB-S2 card and the
multiprotocol branch which I use currently.
/**
 * This listens to the DVB stream for the PAT/PMT and time,
 * which is unfortunately needed as input for the CA.
 *
 * You call either ca_start_in_new_thread() or
 * (if you create the thread yourself) ca_start() and later
 * ca_stop_thread() / ca_stop().
 *
 * Uses open()/close(), poll() and ioctl() system calls.
 *
 * Based on zap_dvb.c and zap_ca.c
 *
 * Copyright (C) 2007 Ben Bucksch
 * Copyright (C) 2004, 2005 Manu Abraham ([EMAIL PROTECTED])
 * Copyright (C) 2006 Andrew de Quincey ([EMAIL PROTECTED])
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU Lesser General Public License as
 * published by the Free Software Foundation; either version 2.1 of
 * the License, or (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
 */

#include poll.h
#include zap_ca.h
#include jni.h
#include sys/ioctl.h
#include sys/poll.h
#include fcntl.h
#include linux/dvb/frontend.h
#include linux/dvb/dmx.h
#include libucsi/mpeg/section.h
#include libucsi/dvb/section.h
#include iostream
#include string


static void process_pat(int pat_fd, const char* demuxDeviceFilename, int channel_service_id, int *pmt_fd, struct pollfd *pollfd);
static void process_tdt(int tdt_fd);
static void process_pmt(int pmt_fd, int channel_service_id);
static void* ca_start_run(void* params);
static int create_filter(const char* demuxDeviceFilename, uint16_t pid, uint8_t table_id);

/
// Thread
/

class CAThread
{
public:
	int myAdapterNo;
	int myChannelServiceID;
	bool myStopSignal;
	JNIEnv* myEnv; // only temporary
	pthread_t myThreadID;
};

static int pat_version = -1; // TODO move to CAThread?
static int ca_pmt_version = -1;

/**
 * Creates a thread and starts ca_start()
 */
CAThread* ca_start_in_new_thread(int adapterNo, int channelServiceID, JNIEnv* env)
{
  CAThread* thread = new CAThread();
  thread-myAdapterNo = adapterNo;
  thread-myChannelServiceID = channelServiceID;
  thread-myEnv = env;
  thread-myStopSignal = false;
  pthread_create((thread-myThreadID), NULL, ca_start_run, (void*) thread);
  return thread;
}

// callback, for use in ca_start_in_new_thread() only
// starting point of thread
static void* ca_start_run(void* param)
{
  CAThread* thread = (CAThread*) param;
  ca_start(thread-myAdapterNo, thread-myChannelServiceID, (thread-myStopSignal), thread-myEnv);
  thread-myEnv = 0;
  return 0;
}

void ca_stop_thread(CAThread* thread)
{
ca_stop((thread-myStopSignal));
	pthread_join(thread-myThreadID, NULL);
	delete thread;
}


/
// ca_start(), incl. setup and poll()
/

void ca_stop(bool* stopSignal)
{
	(*stopSignal) = true;
	zap_ca_stop();
}

#define ERROR_INCASTART(test, message) \
{ \
  if (test) \
  { \
  	delete[] demuxDeviceFilename; \
  	if (pat_fd  0) 

[linux-dvb] mt20xx.c code bugs!

2007-11-15 Thread Vincent Pelletier
On Nov 15, 2007 2:43 AM, kevin liu [EMAIL PROTECTED] wrote:
 while pointer name doesn't have its memory.

Don't you confuse
  char *foo = bar;
with
  char *foo;
  strcpy(foo, bar);
?

The first needs *no* runtime memory allocation, as it was pointed out.
The second does need runtime memory allocation, and as such is a bug.

The code you point out belongs to the first category.

Vincent Pelletier

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb