Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-11 Thread David Ward
On 06/10/2009 10:32 AM, Steven Toth wrote: David Ward wrote: Comcast checked the outlet on channels 2 (41 dB) and 83 (39 dB). I looked afterwards and saw that the first of those is analog programming, but the second just appears as analog noise on my TV set. (??) I asked them to check a

Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-10 Thread David Ward
On 06/09/2009 03:26 PM, Steven Toth wrote: 30db for the top end of ATSC sounds about right. David, when you ran the windows signal monitor - did it claim QAM64 or 256 when it was reporting 30db? Steven and Devin, All the digital signals are 256 QAM. 39 is very good, exceptional. And did t

Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-09 Thread David Ward
On 06/09/2009 10:24 AM, Steven Toth wrote: David has called out Comcast to review his installation. After replacing all the connectors and some cables from the pole all the way to the outlet, their meter ultimately showed 39-40dB at the outlet. My card is showing the same SNR values as before.

Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-08 Thread David Ward
On 06/08/2009 04:36 PM, Devin Heitmueller wrote: On Mon, Jun 8, 2009 at 4:20 PM, Steven Toth wrote: We're getting into the realm of 'do you need to amplify and/or debug your cable network', and out of the realm of driver development. Comcast is coming tomorrow to check out the signal

Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-08 Thread David Ward
On 06/08/2009 12:31 PM, Steven Toth wrote: Your SNR is very low, 0x12c is 30db. I assume you're using digital cable this is borderline. Oh okay ... I wasn't sure how to translate those values before. I like my cable system at home to be atleast 32db (0x140) bare minimum, it's typically 0x160 (

Re: cx18, s5h1409: chronic bit errors, only under Linux

2009-06-08 Thread David Ward
On 06/08/2009 10:17 AM, Devin Heitmueller wrote: On Mon, Jun 8, 2009 at 10:14 AM, Steven Toth wrote: Please let me know how I should proceed in solving this. I would be happy to provide samples of captured video, results from new tests, etc. When you tune using azap, and you can s

cx18, s5h1409: chronic bit errors, only under Linux

2009-06-08 Thread David Ward
me know how I should proceed in solving this. I would be happy to provide samples of captured video, results from new tests, etc. Thanks, David Ward -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.or

Re: [PATCH] cx18: Use do_div for 64-bit division to fix 32-bit kernels

2009-05-29 Thread David Ward
On 05/29/2009 07:09 AM, Andy Walls wrote: On Thu, 2009-05-28 at 20:27 -0400, David Ward wrote: Use the do_div macro for 64-bit division. Otherwise, the module will reference __udivdi3 under 32-bit kernels, which is not allowed in kernel space. Follows style used in cx88 module

[PATCH] cx18: Use do_div for 64-bit division to fix 32-bit kernels

2009-05-28 Thread David Ward
Use the do_div macro for 64-bit division. Otherwise, the module will reference __udivdi3 under 32-bit kernels, which is not allowed in kernel space. Follows style used in cx88 module. Signed-off-by: David Ward diff -r 65ec132f20df -r 91b89f13adb7 linux/drivers/media/video/cx18/cx18-av

Re: "Unknown symbol __udivdi3" with rev >= 11873

2009-05-28 Thread David Ward
On 05/28/2009 03:12 PM, Michael Krufky wrote: On Thu, May 28, 2009 at 12:05 AM, David Ward wrote: Revision 11873 (committed earlier today) has broken the cx18 driver for me, with the line "cx18: Unknown symbol __udivdi3" appearing in dmesg when the module tries to load. I'

"Unknown symbol __udivdi3" with rev >= 11873

2009-05-27 Thread David Ward
on to Mauro for fixing the build for older kernels today, as it is very desirable for me to use a distribution/kernel which has long-term support and updates, but I simply need to add a DVB driver that wasn't part of the older kernel. Thanks so much. David Ward -- To unsubscribe from this

Re: videodev: Unknown symbol i2c_unregister_device (in kernels older than 2.6.26)

2009-05-24 Thread David Ward
On 05/24/2009 07:10 PM, Matt Doran wrote: Hi there, I tried using the latest v4l code on an Mythtv box running 2.6.20, but the v4l videodev module fails to load with the following warnings: videodev: Unknown symbol i2c_unregister_device v4l2_common: Unknown symbol v4l2_device_register_sub

Re: v4l-dvb rev 11757 broke building under Ubuntu Hardy

2009-05-23 Thread David Ward
On 05/14/2009 07:53 PM, Andy Walls wrote: David Ward wrote: I am using v4l-dvb in order to add the cx18 driver under Ubuntu Hardy (8.04). The build is currently broken under Hardy, which uses kernel 2.6.24. I have traced the origin of the problem to revision 11757. As seen in the latest

Re: OpenSuse 11.1 + v4l

2009-05-13 Thread David Ward
On 05/13/2009 03:27 AM, Peter Forstmeier wrote: Hi, i tried to build v4l and did tho following: pe...@linux-d9lb:~> hg clone http://linuxtv.org/hg/v4l-dvb destination directory: v4l-dvb requesting all changes adding changesets adding manifests adding file changes added 11759 changesets with 297

v4l-dvb rev 11757 broke building under Ubuntu Hardy

2009-05-12 Thread David Ward
ecified in initializer Thanks for resolving this. David Ward -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

v4l-dvb rev 11757 broke building under Ubuntu Hardy

2009-05-12 Thread David Ward
ecified in initializer Thanks for resolving this. David Ward -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html