From: CRicky <cricky@dbmail.com>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Bad firmware download link for TDA10046
Date: Sun, 02 Nov 2008 20:30:27 +0100 [thread overview]
Message-ID: <490DFFD3.3030806@dbmail.com> (raw)
Hi,
I have a pinnacle PCTV PCI 310i, and after installing new linux, I
wanted to download firmware TDA10045 and TDA10046. For the first, no
issue, zip is donwloaded, and file is correctly extracted, but for
TDA10046, I get a HTTP 404 error.
It seems that they changed the link to the file. So I have checked and
found the new one:
http://www.technotrend.de/Dokumente/87/software/219/TT_PCI_2.19h_28_11_2006.zip
(seen from http://www.technotrend.de/2755/Downloads.html)
So, in the get_dvb_firmware script, I have replaced (for TDA10046
subroutine), the bad following link by the one I indicated above:
my $url = "http://technotrend-online.com/download/software/219/$sourcefile";
=>
my $url = "http://technotrend.de/Dokumente/87/software/219/$sourcefile";
Sorry, I did not get it from CVS, so I did not make any patch.
Best regards,
CRicky.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
reply other threads:[~2008-11-02 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=490DFFD3.3030806@dbmail.com \
--to=cricky@dbmail.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