DVB via USB - Revision history

Henk Poley: /* Introduction */

2012-12-03T10:13:43Z

Introduction

← Older revision		Revision as of 10:13, 3 December 2012
Line 11:		Line 11:
	==Introduction==		==Introduction==
	'''For all DVB USB devices you will need to load (if not compiled into the kernel):'''		'''For all DVB USB devices you will need to load (if not compiled into the kernel):'''
-	- i2c-core	+	* i2c-core
-	- crc32	+	* crc32
-	- firmware_class	+	* firmware_class
-	- dvb-core.ko	+	* dvb-core.ko
-	- dvb-pll.ko	+	* dvb-pll.ko
	and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.		and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.

Henk Poley at 10:12, 3 December 2012

2012-12-03T10:12:17Z

← Older revision		Revision as of 10:12, 3 December 2012
Line 1:		Line 1:
	For information about supported USB devices, see the appropriate device category: <BR>		For information about supported USB devices, see the appropriate device category: <BR>
-	* [[ATSC USB Devices]]	+	* [[ATSC USB Devices]]
-	* [[DVB-C USB Devices]]	+	* [[DVB-C USB Devices]]
-	* [[DVB-S USB Devices]]	+	* [[DVB-S USB Devices]]
-	* [[DVB-S2 USB Devices]]	+	* [[DVB-S2 USB Devices]]
-	* [[DVB-T USB Devices]]	+	* [[DVB-T USB Devices]]
-	* [[DVB-T2 USB Devices]]	+	* [[DVB-T2 USB Devices]]
	<BR>		<BR>

Henk Poley: /* Additional Technical Information */

2012-12-03T10:05:09Z

Additional Technical Information

← Older revision		Revision as of 10:05, 3 December 2012
Line 83:		Line 83:

	To be continued ...		To be continued ...
		+
		+
		+	== lsusb -t ==
		+
		+	=== Wrong ===
		+	With this setup you will have bandwidth problems with no appropriate warning whatsoever on any log file. Except that video will look horrible.
		+	<pre>
		+	/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M <-- USB1.1, slow, don't us
		+	/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M <-- one bus
		+	\|__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- 1st DVB device, shares bandwidth
		+	\|__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- 2nd DVB device, shares bandwidth
		+	</pre>
		+
		+	=== OK ===
		+	You can solve the above situation by adding a PCI-Express to USB3.0 card:
		+	<pre>
		+	/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
		+	/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M <-- one bus
		+	\|__ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- one DVB device
		+	/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M <-- USB1.1, slow, don't use
		+	/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M <-- one bus
		+	\|__ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <-- one DVB device
		+	</pre>
		+
		+	'''''Rule''': One device per bus''


	[[Category:Hardware\| ]]		[[Category:Hardware\| ]]

Whome: Added DVB-T2 USB as device category

2011-01-20T19:13:03Z

Added DVB-T2 USB as device category

← Older revision		Revision as of 19:13, 20 January 2011
Line 5:		Line 5:
	* [[DVB-S2 USB Devices]]		* [[DVB-S2 USB Devices]]
	* [[DVB-T USB Devices]]		* [[DVB-T USB Devices]]
		+	* [[DVB-T2 USB Devices]]
	<BR>		<BR>

Blastur: Removed dead firmware download link

2010-01-26T10:31:08Z

Removed dead firmware download link

← Older revision		Revision as of 10:31, 26 January 2010
Line 28:		Line 28:
	== Firmware ==		== Firmware ==

-	Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from [http://www.linuxtv.org/downloads/firmware~~/ here] or [http://www.thadathil.net/dvb/fw~~/ here].	+	Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from [http://www.linuxtv.org/downloads/firmware/ here].

	You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:		You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:

Howl: Deleted DVB-T category, this page refers to all type of DVB. Added ' ' as order filter to avoid ! character in category listing

2009-10-03T21:58:35Z

Deleted DVB-T category, this page refers to all type of DVB. Added ' ' as order filter to avoid ! character in category listing

← Older revision		Revision as of 21:58, 3 October 2009
Line 84:		Line 84:


-	~~[[Category:DVB-T\|!USB devices DVB-T]]~~	+	[[Category:Hardware\| ]]
-	[[Category:Hardware\|~~!USB devices DVB-T~~]]	+

Vision: Add a note regarding the need for checking for the presence of udev in some systems for being able to load the firmware.

2008-10-18T11:43:26Z

Add a note regarding the need for checking for the presence of udev in some systems for being able to load the firmware.

← Older revision		Revision as of 11:43, 18 October 2008
Line 50:		Line 50:

	In this case, I have success, because the firmware was loaded.		In this case, I have success, because the firmware was loaded.
		+
		+	Remember that on some system the firmware is loaded by udev, so if for some reason the firmware is not loaded you may check that
		+	udev is acutally running.
		+	To check you could for example issue the command:
		+	- $ ps -e \| grep udev
		+
		+	If the output is empty, then you have to restart the udev daemon. For example in a Debian based system you may try with:
		+	- $ sudo /etc/init.d/udev restart
		+
		+	then try again, removing and inserting the module again with modprobe.

	== Additional Technical Information ==		== Additional Technical Information ==

CityK: fixed links

2008-01-06T22:31:52Z

fixed links

← Older revision		Revision as of 22:31, 6 January 2008
Line 61:		Line 61:
	As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.		As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.

-	Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was [[~~I2C~~]]. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.	+	Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was [[I²C Protocol\|I²C]]. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.

	Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)		Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)

CityK: DVB USB moved to DVB via USB: name

2007-10-20T14:02:55Z

DVB USB moved to DVB via USB: name

← Older revision

Revision as of 14:02, 20 October 2007

CityK: minor fixes

2007-10-20T14:02:37Z

minor fixes

← Older revision		Revision as of 14:02, 20 October 2007
Line 51:		Line 51:
	In this case, I have success, because the firmware was loaded.		In this case, I have success, because the firmware was loaded.

-	== Additional ~~technical information~~ ==	+	== Additional Technical Information ==

	This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.		This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.

-	=== DVB-USB ~~devices host-controlled~~ ===	+	=== Host Controlled DVB USB Devices ===

	When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.		When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.
Line 65:		Line 65:
	Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)		Host-controlled devices are the ones based on DiBcom (dibusb, dib0700), Nebula (DigiTV), Hanftek and others. (see below)

-	=== DVB-USB ~~device firmware-controlled~~ ===	+	=== Firmware Controlled DVB USB Devices===

	Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the [[BOM]]. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.		Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the [[BOM]]. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.