From: "David" <dvb-t@iinet.com.au>
To: "Tim Farrington" <timf@iinet.net.au>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV DVB-T Dual Express
Date: Thu, 7 Aug 2008 18:47:57 +1000 [thread overview]
Message-ID: <37109BA97D5848A396220552404AD028@mce> (raw)
In-Reply-To: 489AA9AF.2060803@iinet.net.au
----- Original Message -----
From: "Tim Farrington" <timf@iinet.net.au>
To: "David" <dvb-t@iinet.com.au>
Cc: <linux-dvb@linuxtv.org>; <stoth@linuxtv.org>;
<patrick.claven@manildra.com.au>
Sent: Thursday, August 07, 2008 5:52 PM
Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV
DVB-T Dual Express
>
> The point is that the developers are trying to incorporate Chris's work
> into the
> main v4l-dvb driver.
>
> Chris's original firmware requirements were:
> dvb-usb-bluebird-01.fw xc3028-dvico-au-01.fw dvb-usb-bluebird-02.fw
>
> whereas now it needs:
> xc3028-v27.fw
>
> It seems that the "new" firmware doesn't work as of yet for Australia, for
> this device.
>
> IIRC, Chris had an "offset" for Australia.
>
> Regards,
> Timf
>
Just a thought....
There has been a lot of information posted on the lead up to announcement of
initial support for the card.
The information that I used to build the drivers was gleaned from a number
of these and was a bit fragmented.
If anyone has been successful in getting the card to work with the new
drivers, a brief step by step, how to would be greatly appreciated.
Regards
David
_______________________________________________
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-07 8:48 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
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 [this message]
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=37109BA97D5848A396220552404AD028@mce \
--to=dvb-t@iinet.com.au \
--cc=linux-dvb@linuxtv.org \
--cc=timf@iinet.net.au \
/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