From: Michael Krufky <mkrufky@linuxtv.org>
To: Bonne Eggleston <b.eggleston@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Recommended repository for Dvico Dual Digital 4 rev1
Date: Wed, 20 Aug 2008 23:03:35 -0400 [thread overview]
Message-ID: <48ACDB07.8080801@linuxtv.org> (raw)
In-Reply-To: <d16b033e0808201942h56e9b370x778faa7098cf5d41@mail.gmail.com>
Bonne Eggleston wrote:
> On Thu, Aug 21, 2008 at 11:48 AM, Michael Krufky <mkrufky@linuxtv.org> wrote:
>
>> On Thu, Aug 21, 2008 at 11:10 AM, Bonne Eggleston
>> <b.eggleston@gmail.com>wrote:
>>
>>>> Hi all,
>>>> I have a working Dvico Dual Digital 4 rev1 using some older drivers
>>>> (from http://linuxtv.org/hg/~pascoe/xc-test/<http://linuxtv.org/hg/%7Epascoe/xc-test/>
>>>> ).
>>>> I'm looking to upgrade my kernel from 2.6.18 to 2.6.25 or 26 and
>>>> thought I should get the most up to date dvb driver too.
>>>> What's the current recommended driver and firmware for this card?
>>>>
>>>>
>>>>
>> Damien Morrissey wrote:
>>
>>> Be warned that there seems to be a funky thing with the firmware (in
>>> australia at least). I needed no less than three different firmware files to
>>> get my DVico Dual Digital 4 (rev1) to be recognised AND to successfully lock
>>> on a channel. Check for dmesg warnings. I am using mythbuntu 8.04.
>>>
>>>
>> Please be advised that the posting policy on this mailing list is to
>> post your reply BELOW the quote.
>>
>> It's irritating that I have to tell this to people repeatedly, and I'm
>> sure its even more irritating for others that have to constantly read my
>> complaints about it.
>>
>> Nothing against you -- please don't top-post in the future.
>>
>> Anyway, Damien.... Please try the latest driver in the v4l-dvb master
>> branch -- recent changesets have improved driver performance, and you
>> should not have the problems anymore that you have described, above.
>>
> So that's the mercurial repository here: http://linuxtv.org/hg/v4l-dvb ?
>
correct.
>
>> The AU-specific firmware images have been deprecated, in favor of a much
>> better driver that works regardless of location. Standard firmware is
>> not used, instead.
>>
> Do you mean standard firmware *is* used instead? Where do I get the
> standard firmware from? Is it just the dvb-usb-bluebird-01.fw from
> http://www.linuxtv.org/downloads/firmware/ ?
>
Use the same bluebird firmware you would have used before. Now, the
standard xc3028-v27.fw is used instead of the AU-specific one. My bad
-- I should have specified that earlier.
-Mike
_______________________________________________
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-21 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 1:10 [linux-dvb] Recommended repository for Dvico Dual Digital 4 rev1 Bonne Eggleston
2008-08-21 1:36 ` Michael Krufky
2008-08-21 1:44 ` Damien Morrissey
2008-08-21 1:48 ` Michael Krufky
2008-08-21 2:42 ` Bonne Eggleston
2008-08-21 3:03 ` Michael Krufky [this message]
[not found] ` <21aab41d0808220726x79486a7fp25bd79f081f2d965@mail.gmail.com>
2008-08-25 1:45 ` Bonne Eggleston
2008-08-26 7:53 ` Kemble Wagner
[not found] ` <ee0ad0230808201920p1bd21d1cpeb66c7c803c73333@mail.gmail.com>
2008-08-21 2:59 ` Michael Krufky
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=48ACDB07.8080801@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=b.eggleston@gmail.com \
--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