summaryrefslogtreecommitdiff
path: root/linux/Documentation/dvb
diff options
context:
space:
mode:
authorMichael Hunold <devnull@localhost>2004-05-12 12:46:58 +0000
committerMichael Hunold <devnull@localhost>2004-05-12 12:46:58 +0000
commite4fa3c987a43338bc0dcb2ed4b01d61abe2b26ab (patch)
treebda04206ce65e461f6be142380a49292b738f505 /linux/Documentation/dvb
parent03d3518e326d236180969bc1bc84023f8ed0c280 (diff)
downloadmediapointer-dvb-s2-e4fa3c987a43338bc0dcb2ed4b01d61abe2b26ab.tar.gz
mediapointer-dvb-s2-e4fa3c987a43338bc0dcb2ed4b01d61abe2b26ab.tar.bz2
- reflect latest changes for frontend firmware loading
Diffstat (limited to 'linux/Documentation/dvb')
-rw-r--r--linux/Documentation/dvb/firmware.txt44
1 files changed, 31 insertions, 13 deletions
diff --git a/linux/Documentation/dvb/firmware.txt b/linux/Documentation/dvb/firmware.txt
index 0991c0c1f..4c7f3d49c 100644
--- a/linux/Documentation/dvb/firmware.txt
+++ b/linux/Documentation/dvb/firmware.txt
@@ -12,17 +12,16 @@ Currently the drivers still use various different methods
to load their firmwares, so here's just a short list of the
current state:
-- dvb-ttpci: driver uses firmware hotplug interface
+Drivers using the firmware hotplug interface:
+- dvb-ttpci
+- tda1004x:
+
+Proprietary solutions which need to be converted:
- ttusb-budget: firmware is compiled in (dvb-ttusb-dspbootcode.h)
- sp887x: firmware is compiled in (sp887x_firm.h)
- alps_tdlb7: firmware is loaded from path specified by
"mcfile" module parameter; the binary must be
extracted from the Windows driver (Sc_main.mc).
-- tda1004x: firmware is loaded from path specified in
- DVB_TDA1004X_FIRMWARE_FILE kernel config
- variable (default /usr/lib/hotplug/firmware/tda1004x.bin); the
- firmware binary must be extracted from the windows
- driver
- ttusb-dec: see "ttusb-dec.txt" for details
1) Automatic firmware loading
@@ -45,7 +44,6 @@ conflicts we propose the following naming scheme:
latest firmware compatible with the driver).
2) Manually loading the firmware into a driver
- (currently only the dvb-ttpci / av7110 driver supports this)
Step a) Mount sysfs-filesystem.
@@ -73,9 +71,9 @@ you want to upload the firmware by hand, however, this might be too fast.
> echo "180" > /sys/class/firmware/timeout
-Step c) Getting a usable firmware file for the dvb-ttpci driver/av7110 card.
+Step c) Getting a usable firmware file
-You can download the firmware files from
+- For the dvb-ttpci driver/av7110 card you can download the firmware files from
http://linuxtv.org/download/dvb/
Please note that in case of the dvb-ttpci driver this is *not* the "Root"
@@ -88,12 +86,23 @@ See dvb-kerrnel/scripts/ in http://linuxtv.org/cvs/.
> wget http://www.linuxtv.org/download/dvb/dvb-ttpci-01.fw
gets you the version 01 of the firmware fot the ttpci driver.
-Step d) Loading the dvb-ttpci driver and loading the firmware
+- The tda1004x driver needs a copy of the DLL "ttlcdacc.dll" from the Haupauge or Technotrend
+windows driver. Currently the DLL from v2.15a of the technotrend driver is supported. Other versions can
+added reasonably painlessly.
+
+Windows driver URL: http://www.technotrend.de/
+
+> wget http://www.technotrend.de/new/215/TTweb_215a_budget_20_05_2003.zip
+> unzip -j TTweb_215a_budget_20_05_2003.zip Software/Oem/PCI/App/ttlcdacc.dll
+
+Step d) Loading the driver and uploading the firmware manually
"modprobe" will take care that every needed module will be loaded
-automatically (except the frontend driver)
+automatically
> modprobe dvb-ttpci
+or
+> modprobe tda1004x
The "modprobe" process will hang until
a) you upload the firmware or
@@ -107,14 +116,23 @@ total 0
drwxr-xr-x 2 root root 0 Jul 29 11:00 0000:03:05.0
-rw-r--r-- 1 root root 0 Jul 29 10:41 timeout
-"0000:03:05.0" is the id for my dvb-c card. It depends on the pci slot,
-so it changes if you plug the card to different slots.
+"0000:03:05.0" is the id of the device that needs an firmware upload.
+
+In this example, this is the pci id of my dvb-c card. It depends on the pci slot,
+so it changes if you plug the card to different slots. For the tda1004x,
+the id will be an artifical number consisting on the i2c bus the device is on.
You can upload the firmware like that:
> export DEVDIR=/sys/class/firmware/0000\:03\:05.0
> echo 1 > $DEVDIR/loading
+
+For the dvb-ttpci card:
> cat dvb-ttpci-01.fw > $DEVDIR/data
+
+For the tda1004x frontend:
+> cat ttlcdacc.dll > $DEVDIR/data
+
> echo 0 > $DEVDIR/loading
That's it. The driver should be up and running now.