From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Michael Hunold <hunold@linuxtv.org>
Cc: torvalds@osdl.org, akpm@osdl.org,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/9] Update the DVB subsystem docs
Date: Mon, 23 Feb 2004 17:23:45 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402231708440.4872@chaos> (raw)
In-Reply-To: <10775702813893@convergence.de>
On Mon, 23 Feb 2004, Michael Hunold wrote:
> +
> +Getting the card going
> +
> + To power up the card, load the following modules in the
> + following order:
> +
> + * insmod dvb-core.o
> + * modprobe bttv.o
> + * insmod bt878.o
> + * insmod dvb-bt8xx.o
> + * insmod sp887x.o
> +
> + The current version of the frontend module sp887x.o, contains
> + no firmware drivers?, so the first time you open it with a DVB
> + utility the driver will try to download some initial firmware
> + to the card. You will need to download this firmware from the
> + web, or copy it from an installation of the Windows drivers
> + that probably came with your card, before you can use it.
> +
> + The default Linux filesystem location for this firmware is
> + /usr/lib/hotplug/firmware/sc_main.mc .
What does this have to do with the kernel? Isn't this for some
utility that starts Aver/TV? Surely the kernel doesn't read files.
I run this same TV card in W$ and the W$ program loads firmware
and starts the card. Who's process context gets stolen to read
these files from within the kernel?
> +
> + The Windows drivers for the Avermedia DVB-T can be obtained
> + from: http://babyurl.com/H3U970 and you can get an application
> + to extract the firmware from:
> + http://www.kyz.uklinux.net/cabextract.php.
> + _________________________________________________________
Truly bizarre, weird........
> +Known Limitations
> +
Truly bizarre, weird........
> @@ -20,7 +20,7 @@
> extracted from the Windows driver (Sc_main.mc).
> - tda1004x: firmware is loaded from path specified in
> DVB_TDA1004X_FIRMWARE_FILE kernel config
WTF? The __kernel__ doesn't read files. User mode programs
use the kernel to read files for them, on their behalf.
> - variable (default /etc/dvb/tda1004x.bin); the
> + variable (default /usr/lib/hotplug/firmware/tda1004x.bin); the
> firmware binary must be extracted from the windows
> driver
Truly bizarre, weird........ It's not April 1st yet!
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-23 22:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:04 [PATCH 0/9] LinuxTV.org DVB update Michael Hunold
2004-02-23 21:04 ` [PATCH 1/9] Update the DVB subsystem docs Michael Hunold
2004-02-23 21:04 ` [PATCH 2/9] Update saa7146 driver core Michael Hunold
2004-02-23 21:04 ` [PATCH 3/9] Minor DVB Skystar2 updates Michael Hunold
2004-02-23 21:04 ` [PATCH 4/9] DVB core update Michael Hunold
2004-02-23 21:04 ` [PATCH 5/9] Misc. DVB frontend updates Michael Hunold
2004-02-23 21:05 ` [PATCH 6/9] stv0299 DVB frontend update Michael Hunold
2004-02-23 21:05 ` [PATCH 7/9] tda1004x " Michael Hunold
2004-02-23 21:05 ` [PATCH 8/9] av7110 DVB driver update Michael Hunold
2004-02-23 21:05 ` [PATCH 9/9] TTUSB-Budget " Michael Hunold
2004-02-23 21:18 ` [PATCH 7/9] tda1004x DVB frontend update Christoph Hellwig
2004-02-23 22:47 ` Michael Hunold
2004-02-23 22:54 ` Christoph Hellwig
2004-02-23 23:01 ` Michael Hunold
2004-02-23 22:09 ` Andrew Morton
2004-02-23 22:52 ` Michael Hunold
2004-02-23 23:11 ` Andrew Morton
2004-02-23 23:15 ` Ralph Metzler
2004-02-24 11:34 ` Marcel Holtmann
2004-02-23 22:23 ` Richard B. Johnson [this message]
2004-02-23 22:57 ` [PATCH 1/9] Update the DVB subsystem docs Michael Hunold
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=Pine.LNX.4.53.0402231708440.4872@chaos \
--to=root@chaos.analogic.com \
--cc=akpm@osdl.org \
--cc=hunold@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®