summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorKlaus Schmidinger <vdr@tvdr.de>2011-12-04 12:45:26 +0100
committerKlaus Schmidinger <vdr@tvdr.de>2011-12-04 12:45:26 +0100
commita49ce434f6152a4431b0dd717f4070dc0da401ef (patch)
treebb1329cf29c377e8424fc1e538ed25110f095c93 /INSTALL
parenta964269fe9080463cc87aba7b454b6b06b7f8677 (diff)
downloadvdr-a49ce434f6152a4431b0dd717f4070dc0da401ef.tar.gz
vdr-a49ce434f6152a4431b0dd717f4070dc0da401ef.tar.bz2
Implemented "Device Bonding"
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL11
1 files changed, 11 insertions, 0 deletions
diff --git a/INSTALL b/INSTALL
index ea04f1c9..96ebebb7 100644
--- a/INSTALL
+++ b/INSTALL
@@ -392,6 +392,17 @@ according to EN50494 (aka "Unicable(TM)", "OLT(TM)", "SatCR", "Single Cable
Distribution", "Channel Stacking System" or "Single Cable Interface") uses
the file "scr.conf" to specify which SCR channels use which user band frequency.
+If DVB-S devices need to be connected to the same satellite cable, but no
+"Satellite Channel Routing" is available, they can be set to be "bonded" in
+the Setup/LNB menu. Bonded devices can only be tuned to the same polarization
+and frequency band, which reduces the number of potentially receivable channels.
+
+Note that it doesn't make sense to use "Satellite Channel Routing" and
+"Device Bonding" at the same time with the same devices. If you use either
+of these methods, it is necessary that your devices are always created in the
+same sequence when the drivers are loaded. You may need to configure some
+proper "udev" rules to make sure this happens.
+
Running VDR with DVB-C (cable) or DVB-T (terrestrial):
------------------------------------------------------