From: CityK <CityK@rogers.com>
To: LinuxDVB Mailing List <linux-dvb@linuxtv.org>
Subject: [linux-dvb] get_dvb_firmware perl script and the present Xceive firmware extraction scripts
Date: Thu, 07 Feb 2008 11:25:19 -0500 [thread overview]
Message-ID: <47AB30EF.7020209@rogers.com> (raw)
Just a thought about some possible "consolidation / elimination of
fragmentation / consistency " meant to benefit the end user. How about
adding to the get_dvb_firmware script (
http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/dvb/get_dvb_firmware
) a section for:
a) XC5000 firmware
- add a download of the firmware ... "wget
http://www.steventoth.net/linux/xc5000/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip"
- and actually add/merge Steve's forty_some_line XC5000 firmware
extraction script, "extract.sh" ( presently found here:
http://www.steventoth.net/linux/xc5000/ )
b) XC2028/3208 firmware
- add a download of the firmware ... "wget
http://www.steventoth.net/linux/xc5000/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip"
- then add a call to Mauro's XC2028/3208 extraction script,
"extract_xc3028.pl" (found here:
http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux/extract_xc3028.pl
) for the actual extraction ... all seamless, and behind the scenes).
That way, DVB users would only need know/worry about the one script -->
get_dvb_firmware i.e.:
# path/get_dvb_firmware xc5000
# path/get_dvb_firmware xc3028
Any licensing/distribution point of restriction I'm overlooking?
Nothing mentioned on stoth's site to suggest otherwise.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
reply other threads:[~2008-02-07 16:25 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=47AB30EF.7020209@rogers.com \
--to=cityk@rogers.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