* DVICO Fusion Dual Express
2009-07-06 8:42 [linux-dvb] Status of em28xx support Mike Martin
@ 2009-07-06 10:21 ` Collier Family
0 siblings, 0 replies; 4+ messages in thread
From: Collier Family @ 2009-07-06 10:21 UTC (permalink / raw)
To: linux-media
I have a Dvico Fusion Dual Express. It is unfortunately rev 4 and the
firmware is not correct.
lspci -vv -nn
04:00.0 0400: 14f1:8852 (rev 04)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Step
ping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 193
Region 0: Memory at 57200000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <2us, L1 <4us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Vital Product Data
Capabilities: [a0] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable
-
Address: 0000000000000000 Data: 0000
the system recognises it 2.6.18-128.1.10.el5 using
video4linux-20090415-88.0.4.el5.x86_64 from atrpms
I'm getting the following from firmware load
Jul 6 20:18:41 localhost kernel: xc2028 1-0061: Loading firmware for
type=BASE F8MHZ (3), id 0000000000000000.
Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading firmware for
type=D2633 DTV7 (90), id 0000000000000000.
Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading SCODE for type=DTV6
QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id
0000000000000000.
Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Incorrect readback of
firmware version.
I suspect rev 4 uses different firmware.
Any help would be greatly appreciated.
Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DVICO Fusion Dual Express
@ 2009-07-06 17:04 sonofzev
2009-07-06 21:52 ` Collier Family
2009-07-08 10:26 ` Collier Family
0 siblings, 2 replies; 4+ messages in thread
From: sonofzev @ 2009-07-06 17:04 UTC (permalink / raw)
To: linux-media, 'Collier Family'
Hi there
I get this error message on some of my motherboards but not all, only when
another tuner is in the machine..
I think this was IRQ sharing related. When I have it on a newer board with more
interrupts it seems to work fine
On Mon Jul 6 20:21 , "Collier Family" sent:
>I have a Dvico Fusion Dual Express. It is unfortunately rev 4 and the
>firmware is not correct.
>
>lspci -vv -nn
>
>04:00.0 0400: 14f1:8852 (rev 04)
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Step
>ping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>
>SERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 193
> Region 0: Memory at 57200000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Express Endpoint IRQ 0
> Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
>ExtTag-
> Device: Latency L0s
> Device: AtnBtn- AtnInd- PwrInd-
> Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
> Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
> Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
> Link: Latency L0s
> Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
> Link: Speed 2.5Gb/s, Width x1
> Capabilities: [80] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
>PME(D0+,D1+,D2+,D3hot
>+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [90] Vital Product Data
> Capabilities: [a0] Message Signalled Interrupts: 64bit+ Queue=0/0
>Enable
>-
> Address: 0000000000000000 Data: 0000
>
>the system recognises it 2.6.18-128.1.10.el5 using
>video4linux-20090415-88.0.4.el5.x86_64 from atrpms
>
>I'm getting the following from firmware load
>
>Jul 6 20:18:41 localhost kernel: xc2028 1-0061: Loading firmware for
>type=BASE F8MHZ (3), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading firmware for
>type=D2633 DTV7 (90), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading SCODE for type=DTV6
>QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id
>0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Incorrect readback of
>firmware version.
>
>I suspect rev 4 uses different firmware.
>
>Any help would be greatly appreciated.
>
>Stephen
>
>
>
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-media" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DVICO Fusion Dual Express
2009-07-06 17:04 DVICO Fusion Dual Express sonofzev
@ 2009-07-06 21:52 ` Collier Family
2009-07-08 10:26 ` Collier Family
1 sibling, 0 replies; 4+ messages in thread
From: Collier Family @ 2009-07-06 21:52 UTC (permalink / raw)
To: sonofzev, linux-media
Thanks for the reply
After I sent the original message I pulled latest hg and installed.
It worked after that.
I suspect some relevent changes since Axel's last video4linux rpm.
Stephen
----- Original Message -----
From: <sonofzev@iinet.net.au>
To: <linux-media@vger.kernel.org>; "'Collier Family'"
<judithc@bigpond.net.au>
Sent: Tuesday, July 07, 2009 3:04 AM
Subject: Re: DVICO Fusion Dual Express
Hi there
I get this error message on some of my motherboards but not all, only when
another tuner is in the machine..
I think this was IRQ sharing related. When I have it on a newer board with
more
interrupts it seems to work fine
On Mon Jul 6 20:21 , "Collier Family" sent:
>I have a Dvico Fusion Dual Express. It is unfortunately rev 4 and the
>firmware is not correct.
>
>lspci -vv -nn
>
>04:00.0 0400: 14f1:8852 (rev 04)
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Step
>ping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>
>SERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 193
> Region 0: Memory at 57200000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Express Endpoint IRQ 0
> Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
>ExtTag-
> Device: Latency L0s
> Device: AtnBtn- AtnInd- PwrInd-
> Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
> Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
> Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port
> 0
> Link: Latency L0s
> Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
> Link: Speed 2.5Gb/s, Width x1
> Capabilities: [80] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
>PME(D0+,D1+,D2+,D3hot
>+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [90] Vital Product Data
> Capabilities: [a0] Message Signalled Interrupts: 64bit+ Queue=0/0
>Enable
>-
> Address: 0000000000000000 Data: 0000
>
>the system recognises it 2.6.18-128.1.10.el5 using
>video4linux-20090415-88.0.4.el5.x86_64 from atrpms
>
>I'm getting the following from firmware load
>
>Jul 6 20:18:41 localhost kernel: xc2028 1-0061: Loading firmware for
>type=BASE F8MHZ (3), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading firmware for
>type=D2633 DTV7 (90), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading SCODE for
>type=DTV6
>QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id
>0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Incorrect readback of
>firmware version.
>
>I suspect rev 4 uses different firmware.
>
>Any help would be greatly appreciated.
>
>Stephen
>
>
>
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-media" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DVICO Fusion Dual Express
2009-07-06 17:04 DVICO Fusion Dual Express sonofzev
2009-07-06 21:52 ` Collier Family
@ 2009-07-08 10:26 ` Collier Family
1 sibling, 0 replies; 4+ messages in thread
From: Collier Family @ 2009-07-08 10:26 UTC (permalink / raw)
To: sonofzev, linux-media
It accepted the firmware OK after the update but still wouldn't tune.
I did some debugging and found the version was the fault.
The code expects version 2 but this card supplies version 4 to the driver.
a quick patch added the lines below to cx23885-core.c at line 724
case 0x04:
/* CX23885-13Z */
dev->hwrevision = 0xb0;
break;
and all worked.
Stephen
----- Original Message -----
From: <sonofzev@iinet.net.au>
To: <linux-media@vger.kernel.org>; "'Collier Family'"
<judithc@bigpond.net.au>
Sent: Tuesday, July 07, 2009 3:04 AM
Subject: Re: DVICO Fusion Dual Express
Hi there
I get this error message on some of my motherboards but not all, only when
another tuner is in the machine..
I think this was IRQ sharing related. When I have it on a newer board with
more
interrupts it seems to work fine
On Mon Jul 6 20:21 , "Collier Family" sent:
>I have a Dvico Fusion Dual Express. It is unfortunately rev 4 and the
>firmware is not correct.
>
>lspci -vv -nn
>
>04:00.0 0400: 14f1:8852 (rev 04)
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Step
>ping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>
>SERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 193
> Region 0: Memory at 57200000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Express Endpoint IRQ 0
> Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
>ExtTag-
> Device: Latency L0s
> Device: AtnBtn- AtnInd- PwrInd-
> Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
> Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
> Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port
> 0
> Link: Latency L0s
> Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
> Link: Speed 2.5Gb/s, Width x1
> Capabilities: [80] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
>PME(D0+,D1+,D2+,D3hot
>+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [90] Vital Product Data
> Capabilities: [a0] Message Signalled Interrupts: 64bit+ Queue=0/0
>Enable
>-
> Address: 0000000000000000 Data: 0000
>
>the system recognises it 2.6.18-128.1.10.el5 using
>video4linux-20090415-88.0.4.el5.x86_64 from atrpms
>
>I'm getting the following from firmware load
>
>Jul 6 20:18:41 localhost kernel: xc2028 1-0061: Loading firmware for
>type=BASE F8MHZ (3), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading firmware for
>type=D2633 DTV7 (90), id 0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Loading SCODE for
>type=DTV6
>QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id
>0000000000000000.
>Jul 6 20:18:42 localhost kernel: xc2028 1-0061: Incorrect readback of
>firmware version.
>
>I suspect rev 4 uses different firmware.
>
>Any help would be greatly appreciated.
>
>Stephen
>
>
>
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-media" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-07-08 11:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-06 17:04 DVICO Fusion Dual Express sonofzev
2009-07-06 21:52 ` Collier Family
2009-07-08 10:26 ` Collier Family
-- strict thread matches above, loose matches on Subject: below --
2009-07-06 8:42 [linux-dvb] Status of em28xx support Mike Martin
2009-07-06 10:21 ` DVICO Fusion Dual Express Collier Family
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.