Talk:DVB-T USB Devices - Revision history

Fasdfasd at 22:29, 28 July 2010

2010-07-28T22:29:21Z

← Older revision		Revision as of 22:29, 28 July 2010
Line 12:		Line 12:

	---		---
		+	== Technaxx DVB S4 ==
		+	Can somebody help me with this stick? There's probably no topic with technaxx products. Yes, they are cheap stuff, but good enough on windows for a little soccer match. When I plug it into the PC, log says "af9015 detected, not supported". MythTV can't find the stick. Installed a propietary driver, which Xubuntu told me to install. Still not recognized. Again a problem with linux =\|
		+
	== Bloody Mess ==		== Bloody Mess ==
	Regarding the bloody mess... I am willing to put some work into reorganizing it but I would like to have some input before I start. Any suggestions about the format the page should have?		Regarding the bloody mess... I am willing to put some work into reorganizing it but I would like to have some input before I start. Any suggestions about the format the page should have?

Hlangos: /* Thinking beyond DVB-T */ more details

2009-12-01T22:29:38Z

Thinking beyond DVB-T: more details

← Older revision		Revision as of 22:29, 1 December 2009
Line 462:		Line 462:

	: Update: Been there, did that, looks ok.		: Update: Been there, did that, looks ok.
		+
		+	:: Actually I added ANALOG-PAL, ANALOG-NTSC, and ANALOG-SECAM, and RADIO-FM, and RADIO-AM, that will make it easier to filter for "ANALOG" or "RADIO".

	=== Separating Data ===		=== Separating Data ===

Hlangos: moved data template and added data splitting policy

2009-11-25T14:46:04Z

moved data template and added data splitting policy

← Older revision		Revision as of 14:46, 25 November 2009
Line 304:		Line 304:
	:: Lol. As Johannes said -- Template Voodoo!		:: Lol. As Johannes said -- Template Voodoo!

-	::: Yeap. Template Voodoo goes a long way. It helps to do get vertical slices (columns) out of the [[Template:~~DVB-T_USB_Devices_ListData~~\|table]]. Some examples are on [[HLPlayground2]]. To go all the way I would also need the Extensions ParserFunctions and StringFunctions. Those would allow to do the horizontal (row wise) slices that I mentioned above.	+	::: Yeap. Template Voodoo goes a long way. It helps to do get vertical slices (columns) out of the [[Template:USB_Device_Data\|table]]. Some examples are on [[HLPlayground2]]. To go all the way I would also need the Extensions ParserFunctions and StringFunctions. Those would allow to do the horizontal (row wise) slices that I mentioned above.

	==== proof of concept ====		==== proof of concept ====
Line 332:		Line 332:
	There are some devices order by their modulator chip and other ones only by their complete Vendor plus Model name. Now that there is a consistent way to have the information thanks to [[User:Hlangos\|Hlangos]] I think that the best order for this page could be first vendor section and then the USB DVB-T models for the vendor, it could be more easy for the users that don't know anything about the chips of his/her product to find if it's supported or not. --[[User:Howl\|howl]] 18:49, 27 September 2009 (UTC)		There are some devices order by their modulator chip and other ones only by their complete Vendor plus Model name. Now that there is a consistent way to have the information thanks to [[User:Hlangos\|Hlangos]] I think that the best order for this page could be first vendor section and then the USB DVB-T models for the vendor, it could be more easy for the users that don't know anything about the chips of his/her product to find if it's supported or not. --[[User:Howl\|howl]] 18:49, 27 September 2009 (UTC)

-	: Agreed. Order by "vendor + model" should be the default. Unfortunately this [http://en.wikipedia.org/wiki/Help:Sorting#Sorting_tables_by_default can't be done by default]. So we'll have to reorganize the [[Template:~~DVB-T_USB_Devices_ListData~~\|data]]. I'd like to leave that sorting until all the data on this article has been ported over.	+	: Agreed. Order by "vendor + model" should be the default. Unfortunately this [http://en.wikipedia.org/wiki/Help:Sorting#Sorting_tables_by_default can't be done by default]. So we'll have to reorganize the [[Template:USB_Device_Data\|data]]. I'd like to leave that sorting until all the data on this article has been ported over.
	: One advantage of having it organized as it is right now (by driver), is the relative ease with which one can add devices that are already in the driver but still missing in the data here. I already did that for the af9005 and af9015 driver and it wasn't all that painful. Just head over to the [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/media/dvb/dvb-usb;hb=HEAD linux kernel git repository] and take a look at the drivers to see whats currently supported. If you feel extra nice, take a look at the driver's history to find out when support for a certain device was added. I've just found out (well, googled) a way to find the kernel version that a certain commit was added to. Just go to the ''commitdiff'' than on the ''raw'' link. Now you'll see an ''X-Git-Tag:'' header with the relevant information. (The manual way is to have a look at the commit date and then compare it with the [http://www.eu.kernel.org/pub/linux/kernel/v2.6/ timestamps of kernel ChangeLog files] and hope for the best :-) ) --[[User:Hlangos\|Hlangos]] 15:55, 29 September 2009 (UTC)		: One advantage of having it organized as it is right now (by driver), is the relative ease with which one can add devices that are already in the driver but still missing in the data here. I already did that for the af9005 and af9015 driver and it wasn't all that painful. Just head over to the [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/media/dvb/dvb-usb;hb=HEAD linux kernel git repository] and take a look at the drivers to see whats currently supported. If you feel extra nice, take a look at the driver's history to find out when support for a certain device was added. I've just found out (well, googled) a way to find the kernel version that a certain commit was added to. Just go to the ''commitdiff'' than on the ''raw'' link. Now you'll see an ''X-Git-Tag:'' header with the relevant information. (The manual way is to have a look at the commit date and then compare it with the [http://www.eu.kernel.org/pub/linux/kernel/v2.6/ timestamps of kernel ChangeLog files] and hope for the best :-) ) --[[User:Hlangos\|Hlangos]] 15:55, 29 September 2009 (UTC)

Line 341:		Line 341:
	Great! BTW, what do you think of the ''e'' links in the last column of the low detail table that I included in the [[Afatech AF9015]] article. I am not yet happy with the space that it wastes. Maybe I'll try to shrink it down a bit or merge it into one of the other columns. --[[User:Hlangos\|Hlangos]] 10:05, 1 October 2009 (UTC)		Great! BTW, what do you think of the ''e'' links in the last column of the low detail table that I included in the [[Afatech AF9015]] article. I am not yet happy with the space that it wastes. Maybe I'll try to shrink it down a bit or merge it into one of the other columns. --[[User:Hlangos\|Hlangos]] 10:05, 1 October 2009 (UTC)

-	: Yesterday I was thinking about changing the e with a little typical block+pencil icon. I not sure about merging it with another column because the edit will be for the whole row of a given device affecting the edit to all the columns. Another possibility could be an approach like the DVB-T USB page, but with a link relative to the AF9015 section in this case [http://www.linuxtv.org/wiki/index.php?title=Template:~~DVB-T_USB_Devices_ListData~~&action=edit&section=10]. With the whole edit approach there is a problem, could not be the same solution for all the tables, for example, a table with DVB-T USB devices for the same vendor, there is no way to link to edit only the pertinent devices, or if when finish the devices porting if the order is changed to manufacturer first, the problem will be when trying to provide edit link for whole devices of a chipset. --[[User:Howl\|howl]] 12:50, 1 October 2009 (UTC)	+	: Yesterday I was thinking about changing the e with a little typical block+pencil icon. I not sure about merging it with another column because the edit will be for the whole row of a given device affecting the edit to all the columns. Another possibility could be an approach like the DVB-T USB page, but with a link relative to the AF9015 section in this case [http://www.linuxtv.org/wiki/index.php?title=Template:USB_Device_Data&action=edit&section=10]. With the whole edit approach there is a problem, could not be the same solution for all the tables, for example, a table with DVB-T USB devices for the same vendor, there is no way to link to edit only the pertinent devices, or if when finish the devices porting if the order is changed to manufacturer first, the problem will be when trying to provide edit link for whole devices of a chipset. --[[User:Howl\|howl]] 12:50, 1 October 2009 (UTC)

	:: <ul><li> Changing the "e" to an icon would be great! Go for it! I would have done it but I was to lazy to hunt for an icon. I guess the kde and gnome projects both have lots of useful icons that we are allowed to use. And you are right about the problems that merging would mean in regard to usability.</li><li> I tried to implement a direct edit link like the one you included up there. The problem is that those links are always "numbered" and if somebody adds or removes a device, the links will break. That was the reason for making one subsection per device in the data page, and part of the reason to add the "did" field. Subsections can be linked to by name and making this name part of the device record made it possible to use the name in templates that render the table rows.</li><li> I don't think we need the capability to edit a group of devices that badly. I can live without it. In cases where you need to edit a whole set of devices you usually do "search and replace" type of edits and those are a pain in the browser anyway. (I copy the whole page content from the wiki's edit window over to a descent text editor, make my changes there and paste the result back into the wiki's edit window. Than I do a quick "Show changes" to make sure I only made the changes that I wanted, and thats it.)</li></ul>		:: <ul><li> Changing the "e" to an icon would be great! Go for it! I would have done it but I was to lazy to hunt for an icon. I guess the kde and gnome projects both have lots of useful icons that we are allowed to use. And you are right about the problems that merging would mean in regard to usability.</li><li> I tried to implement a direct edit link like the one you included up there. The problem is that those links are always "numbered" and if somebody adds or removes a device, the links will break. That was the reason for making one subsection per device in the data page, and part of the reason to add the "did" field. Subsections can be linked to by name and making this name part of the device record made it possible to use the name in templates that render the table rows.</li><li> I don't think we need the capability to edit a group of devices that badly. I can live without it. In cases where you need to edit a whole set of devices you usually do "search and replace" type of edits and those are a pain in the browser anyway. (I copy the whole page content from the wiki's edit window over to a descent text editor, make my changes there and paste the result back into the wiki's edit window. Than I do a quick "Show changes" to make sure I only made the changes that I wanted, and thats it.)</li></ul>
	:: Cheers --[[User:Hlangos\|Hlangos]] 16:28, 1 October 2009 (UTC)		:: Cheers --[[User:Hlangos\|Hlangos]] 16:28, 1 October 2009 (UTC)
	:: Its Looking good --[[User:CityK\|CityK]] 04:09, 2 October 2009 (UTC)		:: Its Looking good --[[User:CityK\|CityK]] 04:09, 2 October 2009 (UTC)
-	::: Trying to make the wiki image title to work but it doesn't <code><nowiki>[[Image:Edit-16x16.png\|link=Template:~~DVB-T~~ USB ~~Devices ListData~~#{{{did\|}}}\|Edit Entry]]</nowiki></code> this code works in the wikipedia's wikimedia, but here the title shown is the url instead "Edit Entry". Tomorrow I will try to find something about it, one solution could be hardcode it in html, but, I prefer to avoid it. --[[User:Howl\|howl]] 00:37, 2 October 2009 (UTC)	+	::: Trying to make the wiki image title to work but it doesn't <code><nowiki>[[Image:Edit-16x16.png\|link=Template:USB Device Data#{{{did\|}}}\|Edit Entry]]</nowiki></code> this code works in the wikipedia's wikimedia, but here the title shown is the url instead "Edit Entry". Tomorrow I will try to find something about it, one solution could be hardcode it in html, but, I prefer to avoid it. --[[User:Howl\|howl]] 00:37, 2 October 2009 (UTC)
-	:::: I tried this <code><nowiki>[[Image:Edit-16x16.png\|link=Template:~~DVB-T~~ USB ~~Devices ListData~~#{{{did\|}}}\|alt=Edit Entry]]</nowiki></code> [[Image:Edit-16x16.png\|link=Template:~~DVB-T~~ USB ~~Devices ListData~~#{{{did\|}}}\|alt=Edit Entry]]	+	:::: I tried this <code><nowiki>[[Image:Edit-16x16.png\|link=Template:USB Device Data#{{{did\|}}}\|alt=Edit Entry]]</nowiki></code> [[Image:Edit-16x16.png\|link=Template:USB Device Data#{{{did\|}}}\|alt=Edit Entry]]
	:::: But it doesn't work ( at least not in firefox ) maybe you'll have to do some html as I had done before ... [http://meta.wikimedia.org/wiki/Help:Link#.22Hover_box.22_on_links]		:::: But it doesn't work ( at least not in firefox ) maybe you'll have to do some html as I had done before ... [http://meta.wikimedia.org/wiki/Help:Link#.22Hover_box.22_on_links]
	::::: Could be a MediaWiki issue in this version? Edit links of images as core feature of MediaWiki has been introduced in 1.14. Don't know which version uses wikipedia but the sintaxis works well there. I have tried to use span but it works with text and not with images, also I have tried a css trick specified in MediaWiki to make links with images in 1.14 pre but the only possible caption with the css method is the same url. --[[User:Howl\|howl]] 13:56, 3 October 2009 (UTC)		::::: Could be a MediaWiki issue in this version? Edit links of images as core feature of MediaWiki has been introduced in 1.14. Don't know which version uses wikipedia but the sintaxis works well there. I have tried to use span but it works with text and not with images, also I have tried a css trick specified in MediaWiki to make links with images in 1.14 pre but the only possible caption with the css method is the same url. --[[User:Howl\|howl]] 13:56, 3 October 2009 (UTC)
Line 443:		Line 443:


-	You can also call it without any filter so that it returns all rows. So the non filtering templates ~~now~~ replaced ~~by those~~.	+	You can also call it without any filter so that it returns all rows. So the non filtering templates were replaced.

	This is another step towards one big table with all the device data ... if mediawiki can handle it :-)		This is another step towards one big table with all the device data ... if mediawiki can handle it :-)
Line 460:		Line 460:
	"MediaFLO".		"MediaFLO".
	Even "fm" and "am" radio could be included in this list.		Even "fm" and "am" radio could be included in this list.
		+
		+	: Update: Been there, did that, looks ok.
		+
		+	=== Separating Data ===
		+
		+	Having all data on all devices in one place may be nice but currently it slows down the editing process.
		+
		+	I decided to split device data along the lines of ''hostinterface''.
		+
		+	It would have been possible to split along the supported broadcasting standard to e.g. have one table that holds all ATSC devices, one for all the DVB-T devices and so on, but there are lots of multi standard devices that would have been hard to classify while there is hardly any device that offers more than one host interface. (The PCI cards that internally have USB host controllers and onboard USB DVB-T devices will be classified as PCI devices since their USB interface is not exposed to the machine's hardware).

Hlangos: /* Adding supported devices from kernel sources */ started second pass

2009-11-11T14:51:46Z

Adding supported devices from kernel sources: started second pass

← Older revision		Revision as of 14:51, 11 November 2009
Line 363:		Line 363:
	\| a800.c \|\| {{Yes}} \|\| {{Yes}}		\| a800.c \|\| {{Yes}} \|\| {{Yes}}
	\|-		\|-
-	\| af9005.c \|\| {{Yes}} \|\| {{No}}	+	\| af9005.c \|\| {{Yes}} \|\| {{Yes}}
	\|-		\|-
-	\| af9015.c \|\| {{Yes}} (one DVB-T PCI device?) \|\| {{No}}	+	\| af9015.c \|\| {{Yes}} (one DVB-T PCI device?) \|\| {{Yes}} added one PCI32 device
	\|-		\|-
	\| anysee.c \|\| {{Yes}} (also DVB-C DVB-S) \|\| {{No}}		\| anysee.c \|\| {{Yes}} (also DVB-C DVB-S) \|\| {{No}}

Hlangos: /* Adding supported devices from kernel sources */ foo

2009-11-11T14:32:53Z

Adding supported devices from kernel sources: foo

← Older revision		Revision as of 14:32, 11 November 2009
Line 359:		Line 359:

	{\| border="1"		{\| border="1"
-	! Filename !! Checked !! ~~Double checked~~	+	! Filename !! Checked !! Second check
	\|-		\|-
-	\| a800.c \|\| {{Yes}} \|\| {{No}}	+	\| a800.c \|\| {{Yes}} \|\| {{Yes}}
	\|-		\|-
	\| af9005.c \|\| {{Yes}} \|\| {{No}}		\| af9005.c \|\| {{Yes}} \|\| {{No}}
Line 377:		Line 377:
	\| cxusb.c \|\| {{Yes}} 12 DVB-T (1 DMB-TH seems to be [[DMB-T/H_USB_Devices\|listed already]] as MagicPro) \|\| {{No}}		\| cxusb.c \|\| {{Yes}} 12 DVB-T (1 DMB-TH seems to be [[DMB-T/H_USB_Devices\|listed already]] as MagicPro) \|\| {{No}}
	\|-		\|-
-	\| dib0700_devices.c \|\| {{Yes}} (also added one PCI and two ATSC devices) \|\| {{No}}	+	\| dib0700_devices.c \|\| {{Yes}} (also added one PCI and two ATSC devices) \|\| {{Yes}}
	\|-		\|-
	\| dibusb-mb.c \|\| {{Yes}} phew .. almost 30 devices \|\| {{No}}		\| dibusb-mb.c \|\| {{Yes}} phew .. almost 30 devices \|\| {{No}}

Hlangos: /* The next step / renamed to / Thinking beyond DVB-T */

2009-11-11T14:15:29Z

/* The next step */ renamed to - Thinking beyond DVB-T

← Older revision		Revision as of 14:15, 11 November 2009
Line 448:		Line 448:
	(The device page for USB DVB-T devices is already over 100kb but apart from slightly longer loading times, it seems to hold.)		(The device page for USB DVB-T devices is already over 100kb but apart from slightly longer loading times, it seems to hold.)

-	=== ~~The next step~~ ===	+	=== Thinking beyond DVB-T ===

	I already think about adding another field, called "supported broadcast standards" to unify the		I already think about adding another field, called "supported broadcast standards" to unify the

Hlangos: doing away with separate row and row/select templates

2009-11-05T18:39:45Z

doing away with separate row and row/select templates

← Older revision		Revision as of 18:39, 5 November 2009
Line 442:		Line 442:
	So you can create tables that list all ''hostinterface'':''USB1.1'' devices that use the ''demodulator'' ''af9005'' and where made by the ''vendor'' ''TerraTec''.		So you can create tables that list all ''hostinterface'':''USB1.1'' devices that use the ''demodulator'' ''af9005'' and where made by the ''vendor'' ''TerraTec''.

-	You can also call it without any filter so that it returns all rows. So the non filtering templates ~~can be deleted~~ ...	+
		+	You can also call it without any filter so that it returns all rows. So the non filtering templates now replaced by those.
		+
		+	This is another step towards one big table with all the device data ... if mediawiki can handle it :-)
		+	(The device page for USB DVB-T devices is already over 100kb but apart from slightly longer loading times, it seems to hold.)

	=== The next step ===		=== The next step ===

Hlangos: doing away with separate row and row/select templates

2009-11-05T18:34:56Z

doing away with separate row and row/select templates

← Older revision		Revision as of 18:34, 5 November 2009
Line 343:		Line 343:
	: Yesterday I was thinking about changing the e with a little typical block+pencil icon. I not sure about merging it with another column because the edit will be for the whole row of a given device affecting the edit to all the columns. Another possibility could be an approach like the DVB-T USB page, but with a link relative to the AF9015 section in this case [http://www.linuxtv.org/wiki/index.php?title=Template:DVB-T_USB_Devices_ListData&action=edit&section=10]. With the whole edit approach there is a problem, could not be the same solution for all the tables, for example, a table with DVB-T USB devices for the same vendor, there is no way to link to edit only the pertinent devices, or if when finish the devices porting if the order is changed to manufacturer first, the problem will be when trying to provide edit link for whole devices of a chipset. --[[User:Howl\|howl]] 12:50, 1 October 2009 (UTC)		: Yesterday I was thinking about changing the e with a little typical block+pencil icon. I not sure about merging it with another column because the edit will be for the whole row of a given device affecting the edit to all the columns. Another possibility could be an approach like the DVB-T USB page, but with a link relative to the AF9015 section in this case [http://www.linuxtv.org/wiki/index.php?title=Template:DVB-T_USB_Devices_ListData&action=edit&section=10]. With the whole edit approach there is a problem, could not be the same solution for all the tables, for example, a table with DVB-T USB devices for the same vendor, there is no way to link to edit only the pertinent devices, or if when finish the devices porting if the order is changed to manufacturer first, the problem will be when trying to provide edit link for whole devices of a chipset. --[[User:Howl\|howl]] 12:50, 1 October 2009 (UTC)

-	:: <ul><li> Changing the "e" to an icon would be great! Go for it! I would have done it but I was to lazy to hunt for an icon. I guess the kde and gnome projects both have lots of useful icons that we are allowed to use~~. Just make sure you edit both templates: [[Template:DVB-T_USB_Devices_List_Low/Row]] and [[Template:DVB-T_USB_Devices_List_Low/Row/Select]]~~. And you are right about the problems that merging would mean in regard to usability.</li><li> I tried to implement a direct edit link like the one you included up there. The problem is that those links are always "numbered" and if somebody adds or removes a device, the links will break. That was the reason for making one subsection per device in the data page, and part of the reason to add the "did" field. Subsections can be linked to by name and making this name part of the device record made it possible to use the name in templates that render the table rows.</li><li> I don't think we need the capability to edit a group of devices that badly. I can live without it. In cases where you need to edit a whole set of devices you usually do "search and replace" type of edits and those are a pain in the browser anyway. (I copy the whole page content from the wiki's edit window over to a descent text editor, make my changes there and paste the result back into the wiki's edit window. Than I do a quick "Show changes" to make sure I only made the changes that I wanted, and thats it.)</li></ul>	+	:: <ul><li> Changing the "e" to an icon would be great! Go for it! I would have done it but I was to lazy to hunt for an icon. I guess the kde and gnome projects both have lots of useful icons that we are allowed to use. And you are right about the problems that merging would mean in regard to usability.</li><li> I tried to implement a direct edit link like the one you included up there. The problem is that those links are always "numbered" and if somebody adds or removes a device, the links will break. That was the reason for making one subsection per device in the data page, and part of the reason to add the "did" field. Subsections can be linked to by name and making this name part of the device record made it possible to use the name in templates that render the table rows.</li><li> I don't think we need the capability to edit a group of devices that badly. I can live without it. In cases where you need to edit a whole set of devices you usually do "search and replace" type of edits and those are a pain in the browser anyway. (I copy the whole page content from the wiki's edit window over to a descent text editor, make my changes there and paste the result back into the wiki's edit window. Than I do a quick "Show changes" to make sure I only made the changes that I wanted, and thats it.)</li></ul>
	:: Cheers --[[User:Hlangos\|Hlangos]] 16:28, 1 October 2009 (UTC)		:: Cheers --[[User:Hlangos\|Hlangos]] 16:28, 1 October 2009 (UTC)
	:: Its Looking good --[[User:CityK\|CityK]] 04:09, 2 October 2009 (UTC)		:: Its Looking good --[[User:CityK\|CityK]] 04:09, 2 October 2009 (UTC)

Hlangos: /* The next step */ new ideas towards a unified device database

2009-11-05T15:31:25Z

The next step: new ideas towards a unified device database

← Older revision		Revision as of 15:31, 5 November 2009
Line 426:		Line 426:
	I guess I'll better put just one big mid-detail table in here and clean up the rest of the mess as time permits.		I guess I'll better put just one big mid-detail table in here and clean up the rest of the mess as time permits.

-	=== ~~The next step~~ ===	+	=== Thinking beyond USB devices ===

-	I ~~think about renaming~~ the "type" field into "hostinterface" ~~very soon so that~~ it may cover	+	I have renamed the "type" field into "hostinterface" it may now cover
	not just "USB1.1" and "USB2.0"		not just "USB1.1" and "USB2.0"
	but also "ISA" "PCI32" "PCI64" "PCI-X" "PCIe" "PCMCIA/PCCARD" "CardBus" "ExpressCard" "IEEE1394"		but also "ISA" "PCI32" "PCI64" "PCI-X" "PCIe" "PCMCIA/PCCARD" "CardBus" "ExpressCard" "IEEE1394"
Line 435:		Line 435:
	I tried to err on the conservative side, so devices that are labled as USB2.0 may also work on USB1.1 if they have a PID filter and		I tried to err on the conservative side, so devices that are labled as USB2.0 may also work on USB1.1 if they have a PID filter and
	there is support for it in the driver/firmware.		there is support for it in the driver/firmware.
		+
		+	==== Tinkering with multi selection ====
		+
		+	I've now created a row rendering template that takes zero or more (currently up to four) attribute-value pairs to do AND-based filtering on.
		+
		+	So you can create tables that list all ''hostinterface'':''USB1.1'' devices that use the ''demodulator'' ''af9005'' and where made by the ''vendor'' ''TerraTec''.
		+
		+	You can also call it without any filter so that it returns all rows. So the non filtering templates can be deleted ...
		+
		+	=== The next step ===

	I already think about adding another field, called "supported broadcast standards" to unify the		I already think about adding another field, called "supported broadcast standards" to unify the

Hlangos: /* Adding supported devices from kernel sources */ more comments and further plans

2009-10-28T17:00:40Z

Adding supported devices from kernel sources: more comments and further plans

← Older revision		Revision as of 17:00, 28 October 2009
Line 356:		Line 356:
	In order to complete the list of supported devices I've gone through some of the [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/media/dvb/dvb-usb dvb-usb kernel drivers].		In order to complete the list of supported devices I've gone through some of the [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/media/dvb/dvb-usb dvb-usb kernel drivers].

-	Here's a reduced list of files that need to be checked:	+	Here's a reduced list of files that need to be checked and double checked (to include the stuff learned during the first round and maybe to either create similar articles for the non-"DVB-T USB" devices supported by those drivers) :

	{\| border="1"		{\| border="1"
-	! Filename !! Checked	+	! Filename !! Checked !! Double checked
	\|-		\|-
-	\| a800.c \|\| {{Yes}}	+	\| a800.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| af9005.c \|\| {{Yes}}	+	\| af9005.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| af9015.c \|\| {{Yes}} (one DVB-T PCI device?)	+	\| af9015.c \|\| {{Yes}} (one DVB-T PCI device?) \|\| {{No}}
	\|-		\|-
-	\| anysee.c \|\| {{Yes}} (also DVB-C DVB-S)	+	\| anysee.c \|\| {{Yes}} (also DVB-C DVB-S) \|\| {{No}}
	\|-		\|-
-	\| au6610.c \|\| {{Yes}}	+	\| au6610.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| ce6230.c \|\| {{Yes}}	+	\| ce6230.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| cinergyT2-core.c \|\| {{Yes}}	+	\| cinergyT2-core.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| cxusb.c \|\| {{Yes}} 12 DVB-T (1 DMB-TH seems to be [[DMB-T/H_USB_Devices\|listed already]] as MagicPro)	+	\| cxusb.c \|\| {{Yes}} 12 DVB-T (1 DMB-TH seems to be [[DMB-T/H_USB_Devices\|listed already]] as MagicPro) \|\| {{No}}
	\|-		\|-
-	\| dib0700_devices.c \|\| {{Yes}} (also added one PCI and two ATSC devices)	+	\| dib0700_devices.c \|\| {{Yes}} (also added one PCI and two ATSC devices) \|\| {{No}}
	\|-		\|-
-	\| dibusb-mb.c \|\| {{Yes}} phew .. almost 30 devices	+	\| dibusb-mb.c \|\| {{Yes}} phew .. almost 30 devices \|\| {{No}}
	\|-		\|-
-	\| dibusb-mc.c \|\| {{Yes}}	+	\| dibusb-mc.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| digitv.c \|\| {{Yes}}	+	\| digitv.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| dtt200u.c \|\| {{Yes}}	+	\| dtt200u.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| dtv5100.c \|\| {{Yes}}	+	\| dtv5100.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| dw2102.c \|\| {{Yes}} DVB-S DVB-C	+	\| dw2102.c \|\| {{Yes}} DVB-S DVB-C \|\| {{No}}
	\|-		\|-
-	\| friio.c \|\| {{Yes}} ISDB	+	\| friio.c \|\| {{Yes}} ISDB \|\| {{No}}
	\|-		\|-
-	\| gl861.c \|\| {{Yes}}	+	\| gl861.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| gp8psk.c \|\| {{Yes}} DVB-S	+	\| gp8psk.c \|\| {{Yes}} DVB-S \|\| {{No}}
	\|-		\|-
-	\| m920x.c \|\| {{Yes}}	+	\| m920x.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| nova-t-usb2.c \|\| {{Yes}}	+	\| nova-t-usb2.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| opera1.c \|\| {{Yes}} DVB-S	+	\| opera1.c \|\| {{Yes}} DVB-S \|\| {{No}}
	\|-		\|-
-	\| ttusb2.c \|\| {{Yes}} DVB-S	+	\| ttusb2.c \|\| {{Yes}} DVB-S \|\| {{No}}
	\|-		\|-
-	\| umt-010.c \|\| {{Yes}}	+	\| umt-010.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
-	\| vp702x.c \|\| {{Yes}} DVB-S	+	\| vp702x.c \|\| {{Yes}} DVB-S \|\| {{No}}
	\|-		\|-
-	\| vp7045.c \|\| {{Yes}}	+	\| vp7045.c \|\| {{Yes}} \|\| {{No}}
	\|-		\|-
	\|}		\|}
Line 417:		Line 417:
	If somebody feels like helping out, please mark the file above as "work in progress" to avoid duplicate work.		If somebody feels like helping out, please mark the file above as "work in progress" to avoid duplicate work.

-	~~I guess I picked the low hanging fruit. The drivers left contain a lot of different devices each, but reading those~~ files ~~and translating them~~ into entries in the device database is quite easy.	+	Translating source files into entries in the device database is quite easy.

	Just look for ''.devices'' and ''.name'' in the source file and then look above for ''.frontend_attach'' and ''.tuner_attach'' for further information on the hardware.		Just look for ''.devices'' and ''.name'' in the source file and then look above for ''.frontend_attach'' and ''.tuner_attach'' for further information on the hardware.
Line 424:		Line 424:

	Next task will be to merge the date on this page with the database and removal of those devices from this page.		Next task will be to merge the date on this page with the database and removal of those devices from this page.
-	~~As soon as that is done~~ I'll put just one big mid-detail table in here and clean up the rest of the mess.	+	I guess I'll better put just one big mid-detail table in here and clean up the rest of the mess as time permits.
		+
		+	=== The next step ===
		+
		+	I think about renaming the "type" field into "hostinterface" very soon so that it may cover
		+	not just "USB1.1" and "USB2.0"
		+	but also "ISA" "PCI32" "PCI64" "PCI-X" "PCIe" "PCMCIA/PCCARD" "CardBus" "ExpressCard" "IEEE1394"
		+
		+	The information about which device is "USB1.1" or "USB2.0"-only and which device does both is probably wrong in 80% of the cases.
		+	I tried to err on the conservative side, so devices that are labled as USB2.0 may also work on USB1.1 if they have a PID filter and
		+	there is support for it in the driver/firmware.
		+
		+	I already think about adding another field, called "supported broadcast standards" to unify the
		+	structure a little further.
		+	Possible values would be the analog encodings "PAL" "NTSC" "SECAM" as well as digital encodings
		+	"DVB-T" "DVB-C" "DVB-C2" "DVB-S" "DVB-S2" "DVB-H" "DVB-SH"
		+	"ATSC" "ATSC-M/H"
		+	"ISDB-S" "ISDB-T" "1seg" "ISDB-C" "SBTVD/ISDB-Tb"
		+	"DMB-T/H" "ADTB-T" "CMMB" "DMB-T"
		+	"T-DMB" "S-DMB"
		+	"MediaFLO".
		+	Even "fm" and "am" radio could be included in this list.

Talk:DVB-T USB Devices - Revision history

Fasdfasd at 22:29, 28 July 2010

Hlangos: /* Thinking beyond DVB-T */ more details

Hlangos: moved data template and added data splitting policy

Hlangos: /* Adding supported devices from kernel sources */ started second pass

Hlangos: /* Adding supported devices from kernel sources */ foo

Hlangos: /* The next step */ renamed to /* Thinking beyond DVB-T */

Hlangos: doing away with separate row and row/select templates

Hlangos: doing away with separate row and row/select templates

Hlangos: /* The next step */ new ideas towards a unified device database

Hlangos: /* Adding supported devices from kernel sources */ more comments and further plans

Hlangos: /* The next step / renamed to / Thinking beyond DVB-T */