From: Tim Farrington <timf@iinet.net.au>
To: David Porter <dvb-t@iinet.com.au>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV DVB-T Dual Express
Date: Wed, 06 Aug 2008 16:51:47 +0800 [thread overview]
Message-ID: <48996623.4010703@iinet.net.au> (raw)
In-Reply-To: <41A3723BDBA947399F2CBD960E4AFB94@mce>
David Porter wrote:
> Hi
>
> I have one of these, saw Stevens post and thought i would give it a go.
>
> I built from : http://linuxtv.org/hg/~stoth/v4l-dvb
> All seemed to go well with no errors.
>
> dmesg reads:
>
> [ 31.964424] CORE cx23885[0]: subsystem: 18ac:db78, board: DViCO
> FusionHDTV DVB-T Dual Express [card=11,autodetected]
> [ 32.104767] cx23885[0]: i2c bus 0 registered
> [ 32.104781] cx23885[0]: i2c bus 1 registered
> [ 32.104794] cx23885[0]: i2c bus 2 registered
> [ 32.164385] input: i2c IR (FusionHDTV) as /devices/virtual/input/input8
> [ 32.422764] ir-kbd-i2c: i2c IR (FusionHDTV) detected at i2c-1/1-006b/ir0
> [cx23885[0]]
> [ 32.423135] cx23885[0]: cx23885 based dvb card
> [ 32.492021] xc2028 1-0061: creating new instance
> [ 32.492027] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
> [ 32.492036] DVB: registering new adapter (cx23885[0])
> [ 32.492040] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
> [ 32.492386] cx23885[0]: cx23885 based dvb card
> [ 32.492924] xc2028 2-0061: creating new instance
> [ 32.492926] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
> [ 32.492928] DVB: registering new adapter (cx23885[0])
> [ 32.492930] DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)...
> [ 32.493228] cx23885_dev_checkrevision() Hardware revision = 0xb0
> [ 32.493236] cx23885[0]/0: found at 0000:02:00.0, rev: 2, irq: 16,
> latency: 0, mmio: 0xfe800000
>
> But scanning, returns :
>
> [ 1381.214624] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
> [ 1382.220858] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
> [ 1382.260825] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
> [ 1383.267724] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
> [ 1383.276680] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
>
> I checked /lib/firmware/ but xc3028-v27.fw is not in the directory ?
>
> Must have messed it up somewhere! Any help appreciated.
>
> Thanks
> David
>
> ----- Original Message -----
> From: "Steven Toth" <stoth@linuxtv.org>
> To: "Luke Yelavich" <themuso@themuso.com>
> Cc: <linux-dvb@linuxtv.org>
> Sent: Wednesday, August 06, 2008 11:44 AM
> Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV
> DVB-T Dual Express
>
>
>
>>>>> I've tested with the HVR1500Q (xc5000 based) and I'm happy with the
>>>>> results. Can you both try the DViCO board?
>>>>>
>>>> It tests fine and I like how simpler things have got.
>>>>
>>> I pulled the above linked tree, and compiled the modules. It seems at the
>>> moment for the dual express, that I have to pass the parameter card=11 to
>>> the driver, for it to correctly find the card and make use of all
>>> adapters. Without any module parameters, dmsg complains that the card
>>> couldn't be identified, yet two adapters are shown. I have two of these
>>> cards.
>>>
>>> Hope this helps some.
>>>
>> .. And they're both the same model?
>>
>> If so, insert one at a time and run the 'lspci -vn' command, save the
>> output for each card.
>>
>> Post the output here.
>>
>> Assuming you load the driver with card=11, does each card work correctly
>> after that?
>>
>> - Steve
>>
>> _______________________________________________
>> 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
>
>
To obtain xc3028-v27.fw
see ~/v4l-dvb/linux/Documentation/video4linux/extract_xc3028.pl
Regards,
Timf
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-06 8:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 3:40 [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV DVB-T Dual Express stev391
2008-08-01 12:34 ` bumkunjo
2008-08-05 1:25 ` Steven Toth
[not found] ` <1217969890.6864.11.camel@bonnie>
2008-08-05 21:16 ` Steven Toth
2008-08-05 21:43 ` Anton Blanchard
2008-08-05 23:41 ` Luke Yelavich
2008-08-06 1:44 ` Steven Toth
2008-08-06 8:09 ` David Porter
2008-08-06 8:51 ` Tim Farrington [this message]
2008-08-07 3:31 ` David
2008-08-07 4:34 ` Tim Farrington
2008-08-07 6:41 ` David
2008-08-07 7:00 ` Tim Farrington
2008-08-07 7:10 ` David
2008-08-07 7:18 ` SUBHRANIL CHOUDHURY
2008-08-07 7:52 ` Tim Farrington
2008-08-07 8:47 ` David
2008-08-10 23:31 ` Luke Yelavich
2008-08-07 1:06 ` jochen s
-- strict thread matches above, loose matches on Subject: below --
2008-08-08 0:04 stev391
2008-08-07 10:58 stev391
2008-08-07 15:00 ` Steven Toth
2008-08-16 4:28 ` David
2008-08-05 11:52 stev391
2008-06-30 23:56 stev391
[not found] ` <20080731042433.GA21788@kryten>
2008-07-31 15:08 ` Steven Toth
2008-08-01 1:21 ` Anton Blanchard
2008-08-01 1:43 ` Steven Toth
2008-08-01 2:04 ` Steven Toth
2008-08-01 2:13 ` Anton Blanchard
2008-08-01 2:52 ` Steven Toth
2008-08-01 2:55 ` Anton Blanchard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48996623.4010703@iinet.net.au \
--to=timf@iinet.net.au \
--cc=dvb-t@iinet.com.au \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox