Re: cx23885, new hardware revision found

2009-07-08 Thread Collier Family
I found there is a revision change - doesn't seem to affect the operation 
but needs a patch to be detected.


See todays post.

Stephen 


--
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


Re: cx23885, new hardware revision found

2009-06-30 Thread Michael Krufky
On Mon, Jun 29, 2009 at 9:43 AM, Steven Toth wrote:
>>> cx23885_dev_checkrevision() New hardware revision found 0x0
>>> cx23885_dev_checkrevision() Hardware revision unknown 0x0
>>> cx23885[0]/0: found at :02:00.0, rev: 4, irq: 17, latency: 0,
>>> mmio: 0xfd80
>>> cx23885 :02:00.0: setting latency timer to 64
>>>
>>> I'm pretty sure that is the problem but I don't know how to fix it.  I
>
> The new revision isn't the problem, the above code is for information
> purposes so we can track new revs of the silicon in this mailing list. Most
> likely the demodulators / tuners are not configured correctly. DViCO
> probably changed something.
>
> Double check that the silicon and gpios / settings inside the cx23885 driver
> for the existing card definition match the silicon and configuration for
> this new card you have.
>

It's not a new revision.  Something else is wrong.  I have both
revisions of this board, and they display the same revision
information as Hauppauge cx23885-based products:

m...@codes:~$ dmesg | grep checkrevision
[  136.689267] cx23885_dev_checkrevision() Hardware revision = 0xb0
[  136.914968] cx23885_dev_checkrevision() Hardware revision = 0xb0
[  137.086548] cx23885_dev_checkrevision() Hardware revision = 0xb0

If it was a PCI card I would suggest moving it to another PCI slot,
but I'm not sure that would help at all in the case of PCIe.

DViCO has not updated their Windows driver since April of last year.
I think that Michael Kutyna should confirm that the device works in
windows before anybody proceeds to troubleshoot this any further -- it
might just be a bad board / platform.

-Mike Krufky
--
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


Re: cx23885, new hardware revision found

2009-06-29 Thread Steven Toth

cx23885_dev_checkrevision() New hardware revision found 0x0
cx23885_dev_checkrevision() Hardware revision unknown 0x0
cx23885[0]/0: found at :02:00.0, rev: 4, irq: 17, latency: 0,
mmio: 0xfd80
cx23885 :02:00.0: setting latency timer to 64

I'm pretty sure that is the problem but I don't know how to fix it.  I


The new revision isn't the problem, the above code is for information purposes 
so we can track new revs of the silicon in this mailing list. Most likely the 
demodulators / tuners are not configured correctly. DViCO probably changed 
something.


Double check that the silicon and gpios / settings inside the cx23885 driver for 
the existing card definition match the silicon and configuration for this new 
card you have.


--
Steven Toth - Kernel Labs
http://www.kernellabs.com
--
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


Re: cx23885, new hardware revision found

2009-06-29 Thread Michael Kutyna
So does anybody have any ideas how I can attempt to proceed with this?

I was thinking of looking in the code for the checkrevision function
and commenting it out to see what happens but I suspect that I'll get
the same lack of signal.  It has been a few years since I have coded
any C but I guess I can try.

Thanks in advance for any assitance,
mkutyna

On Sat, Jun 20, 2009 at 6:08 PM, Michael Kutyna wrote:
> Hi, I just purchased a Dvico FusionHDTV7 Dual Express and intend on
> using it with MythTV.  Unfortunately, the dvb-apps aren't working with
> it just yet and I think I've narrowed down why.
>
> I've used mercurial to get the latest v4l-dvb source, compiled and
> installed the modules.  I downloaded the firmware from Steven Toth's
> website, extracted and installed it.  This all seems to run fine.
>
> Running scan against the us-ATSC-center-frequencies file returns no
> channels and running femon -a 0 returns the following output:
>
> status S     | signal  | snr  | ber  | unc  |
>
> After examining dmesg output, I noticed the following bit:
>
> cx23885_dev_checkrevision() New hardware revision found 0x0
> cx23885_dev_checkrevision() Hardware revision unknown 0x0
> cx23885[0]/0: found at :02:00.0, rev: 4, irq: 17, latency: 0,
> mmio: 0xfd80
> cx23885 :02:00.0: setting latency timer to 64
>
> I'm pretty sure that is the problem but I don't know how to fix it.  I
> also tried using mercurial to get the v4l tree from
> http://linuxtv.org/hg/~stoth/v4l-dvb/ with the same results as above.
>
> Thanks in advance for any assistance you can offer.
>
> mkutyna
>
--
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


cx23885, new hardware revision found

2009-06-20 Thread Michael Kutyna
Hi, I just purchased a Dvico FusionHDTV7 Dual Express and intend on
using it with MythTV.  Unfortunately, the dvb-apps aren't working with
it just yet and I think I've narrowed down why.

I've used mercurial to get the latest v4l-dvb source, compiled and
installed the modules.  I downloaded the firmware from Steven Toth's
website, extracted and installed it.  This all seems to run fine.

Running scan against the us-ATSC-center-frequencies file returns no
channels and running femon -a 0 returns the following output:

status S | signal  | snr  | ber  | unc  |

After examining dmesg output, I noticed the following bit:

cx23885_dev_checkrevision() New hardware revision found 0x0
cx23885_dev_checkrevision() Hardware revision unknown 0x0
cx23885[0]/0: found at :02:00.0, rev: 4, irq: 17, latency: 0,
mmio: 0xfd80
cx23885 :02:00.0: setting latency timer to 64

I'm pretty sure that is the problem but I don't know how to fix it.  I
also tried using mercurial to get the v4l tree from
http://linuxtv.org/hg/~stoth/v4l-dvb/ with the same results as above.

Thanks in advance for any assistance you can offer.

mkutyna
--
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