LinuxMCE - User contributions [en]

QOrbiter Targets

2012-12-03T22:35:17Z

Buckle: /* Windows x86 */

[[category:QML]]
[[category:QOrbiter]]
[[Category: Programmer's Guide]]
This page is meant as an overview, what targets exist for the qOrbiter, and what kind of requirements each of the targets has.

= Linux =
Linux is the main platform qOrbiter is developed on.

Qt lib version = 4.8.3

== Relevant directories ==
qOrbiter_src/qml/desktop

= Android =
Android is the main target for smaller skins.

Qt lib version = 4.8.2 (necessitas)

== Relevant directories ==
qOrbiter_src/qml/android
qOrbiter_src/android

= Symbian =
Symbian could be target. We need developers for this.

Qt lib version = 4.8.x (latest 4.x should always be usable. Details on [http://qt-project.org/doc/qt-4.8/install-symbian-linux.html QtProject]

== Relevant directories ==
no specific QML created as of yet [[User:Posde|posde]]

= Windows x86 =
Windows x86 successfully builds with the MSVC compiler.

Unfortunately, there is a segfault that happens shortly after skin-loading takes place. The root cause of the segfault has not yet been determined.

Qt lib version = 4.8.x (latest 4.x should be usable)

== Relevant directories ==
qOrbiter_src/qml/desktop

= Windows RT =
Windows RT could be a target, but there are no devs for it atm.

In order to work on WinRT, QOrbiter will need to be made into a Windows Store app. There are a few dependency hurdles that will need to be cleared in order for that to happen.

*QT libs needs to be ported to WinRT.
**Status of that project can be found here: [http://qt-project.org/wiki/WinRT]
*DCE and other supporting LinuxMCE libs need to be ported to WinRT.
**Not all win32 apis are available from the Windows Store app sandbox. Threading and sockets come to mind. Significant re-write and/or shims may be necessary.

Qt lib version = QT5

= iOS =
iOS is an important target, but atm there is no release of a Qt lib that we can use for it.

= MacOSX =
MacOSX could be a target, but there is nothing available atm.

QOrbiter Targets

2012-12-03T22:19:24Z

Buckle: /* Windows RT */

[[category:QML]]
[[category:QOrbiter]]
[[Category: Programmer's Guide]]
This page is meant as an overview, what targets exist for the qOrbiter, and what kind of requirements each of the targets has.

= Linux =
Linux is the main platform qOrbiter is developed on.

Qt lib version = 4.8.3

== Relevant directories ==
qOrbiter_src/qml/desktop

= Android =
Android is the main target for smaller skins.

Qt lib version = 4.8.2 (necessitas)

== Relevant directories ==
qOrbiter_src/qml/android
qOrbiter_src/android

= Symbian =
Symbian could be target. We need developers for this.

Qt lib version = 4.8.x (latest 4.x should always be usable. Details on [http://qt-project.org/doc/qt-4.8/install-symbian-linux.html QtProject]

== Relevant directories ==
no specific QML created as of yet [[User:Posde|posde]]

= Windows x86 =
Windows x86 is being worked on, without many details.

Qt lib version = 4.8.x (latest 4.x should be usable)

== Relevant directories ==
qOrbiter_src/qml/desktop

= Windows RT =
Windows RT could be a target, but there are no devs for it atm.

In order to work on WinRT, QOrbiter will need to be made into a Windows Store app. There are a few dependency hurdles that will need to be cleared in order for that to happen.

*QT libs needs to be ported to WinRT.
**Status of that project can be found here: [http://qt-project.org/wiki/WinRT]
*DCE and other supporting LinuxMCE libs need to be ported to WinRT.
**Not all win32 apis are available from the Windows Store app sandbox. Threading and sockets come to mind. Significant re-write and/or shims may be necessary.

Qt lib version = QT5

= iOS =
iOS is an important target, but atm there is no release of a Qt lib that we can use for it.

= MacOSX =
MacOSX could be a target, but there is nothing available atm.

DViCO FusionHDTV7 Dual Express

2009-12-23T03:32:56Z

Buckle: removed v4l2-ctl output, as it is prolly from my other card.

[[Category: TV_Cards]]
[[Category: Video]]

==General==

* Dual tuners - record/watch multiple channels at once. XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC)

* PCI-Express x1

* Conexant CX23385

* Samsung S5H1441

* $139.99 USD + shipping (as of 12 JUN 2009) [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]

==PCI Device Info==

04:00.0 0400: '''14f1:8852''' (rev 04)
Subsystem: '''18ac:d618'''
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data <?>
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [200] Virtual Channel <?>
Kernel driver in use: cx23885
Kernel modules: cx23885

==Misc==
* Firmware version can vary based on what kernel you are running. If both versions are available in /lib/firmware then there should be no problem.
dvb-fe-xc5000-1.1.fw
dvb-fe-xc5000-1.6.114.fw

==Links==
* Product Page [http://www.fusionhdtv.co.kr/ENG/products/HDTV7DualExpress.aspx]
* Newegg [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]
* XC5000 Firmware [http://www.steventoth.net/linux/xc5000/]
* linuxtv wiki [http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV7_Dual_Express]
* [http://www.mythtv.org/pipermail/mythtv-users/2008-August/229796.html]

DViCO FusionHDTV7 Dual Express

2009-12-23T03:22:40Z

Buckle: Note about different firmware versions

[[Category: TV_Cards]]
[[Category: Video]]

==General==

* Dual tuners - record/watch multiple channels at once. XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC)

* PCI-Express x1

* Conexant CX23385

* Samsung S5H1441

* $139.99 USD + shipping (as of 12 JUN 2009) [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]

==PCI Device Info==

04:00.0 0400: '''14f1:8852''' (rev 04)
Subsystem: '''18ac:d618'''
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data <?>
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [200] Virtual Channel <?>
Kernel driver in use: cx23885
Kernel modules: cx23885

==v4l2-ctl -n==

<pre>
dcerouter:~# v4l2-ctl -n
ioctl: VIDIOC_ENUMINPUT
Input : 0
Name : Composite0
Type : 0x00000002
Audioset: 0x00000001
Tuner : 0x00000000
Standard: 0x0000000000FFBFFF ( PAL NTSC SECAM )
Status : 258

Input : 1
Name : Composite1
Type : 0x00000002
Audioset: 0x00000001
Tuner : 0x00000000
Standard: 0x0000000000FFBFFF ( PAL NTSC SECAM )
Status : 0
</pre>

==Misc==
* Firmware version can vary based on what kernel you are running. If both versions are available in /lib/firmware then there should be no problem.
dvb-fe-xc5000-1.1.fw
dvb-fe-xc5000-1.6.114.fw

==Links==
* Product Page [http://www.fusionhdtv.co.kr/ENG/products/HDTV7DualExpress.aspx]
* Newegg [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]
* XC5000 Firmware [http://www.steventoth.net/linux/xc5000/]
* linuxtv wiki [http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV7_Dual_Express]
* [http://www.mythtv.org/pipermail/mythtv-users/2008-August/229796.html]

DViCO FusionHDTV7 Dual Express

2009-12-23T03:16:07Z

Buckle:

[[Category: TV_Cards]]
[[Category: Video]]

==General==

* Dual tuners - record/watch multiple channels at once. XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC)

* PCI-Express x1

* Conexant CX23385

* Samsung S5H1441

* $139.99 USD + shipping (as of 12 JUN 2009) [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]

==PCI Device Info==

04:00.0 0400: '''14f1:8852''' (rev 04)
Subsystem: '''18ac:d618'''
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data <?>
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [200] Virtual Channel <?>
Kernel driver in use: cx23885
Kernel modules: cx23885

==v4l2-ctl -n==

<pre>
dcerouter:~# v4l2-ctl -n
ioctl: VIDIOC_ENUMINPUT
Input : 0
Name : Composite0
Type : 0x00000002
Audioset: 0x00000001
Tuner : 0x00000000
Standard: 0x0000000000FFBFFF ( PAL NTSC SECAM )
Status : 258

Input : 1
Name : Composite1
Type : 0x00000002
Audioset: 0x00000001
Tuner : 0x00000000
Standard: 0x0000000000FFBFFF ( PAL NTSC SECAM )
Status : 0
</pre>

==Links==
* Product Page [http://www.fusionhdtv.co.kr/ENG/products/HDTV7DualExpress.aspx]
* Newegg [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]
* XC5000 Firmware [http://www.steventoth.net/linux/xc5000/]
* linuxtv wiki [http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV7_Dual_Express]
* [http://www.mythtv.org/pipermail/mythtv-users/2008-August/229796.html]

Control lights or climate with a floorplan

2009-08-13T14:07:31Z

Buckle: /* How to set it up */ Removed JPEG as file type.

{| align="right"
| __TOC__
|}
[[Image:Floorplan.jpg|thumb|250px|Floorplan Wizard Page Admin Website]]
==How to set it up==

Create floorplans for your house using a paint program. Make them roughly square around 1,200 x 1,200 pixels--it can be smaller but then OrbiterGen will have to stretch them for high-res displays and they may not look as good. Save them as png. You can have as many floorplans as you want. For a big house you could create one floorplan that includes the whole house, called "Overview" on which you place only major objects, and then close-up floorplans like "North wing" for more detail. There are no limits or rules. Then in [[LinuxMCE Admin Website]] go to '''Wizard->Devices->[[Floorplans|Floorplan Wizard]]'''. Click "Add floorplan" and add all the floorplans using the 'browse' button to pick the images. Then use the 2 pull-downs on the floorplan wizard to pick a floorplan, and a type (Lighting, Climate, etc.). Lights, blinds and drapes appear on the Lighting floorplan. Heaters, air conditioners, pool, jacuzzi and sprinklers appear on the Climate floorplan. Drag and drop the devices to indicate their position on the floorplans. To remove a device from a floorplan, drag it back off the floorplan. Note that what icon appears to represent the device is chosen on the Wizard, Devices, Lights/Climate pages in the Floorplan Object Type pulldown. You will need Regen the orbiters UI on Wizard, Devices, Orbiters to see the floorplans

==How to use it==
Choose one of the floorplan buttons from any Orbiter. There are: Lighting, Media, Climate, Telecom and Security floorplans. With the standard UI and skin, these will be the five buttons on the left side of the Orbiter's main menu. When the floorplan appears you can select another floorplan, or view you want, like "Overview" and "North wing" in our example. You will see all the devices as you laid them out when you set it up. Touch any device to see a pop-up with the commands you can send the device, such as "On", "Off", "50%", etc.

You can touch other devices to select them too. Then touching a command, like On, will send that command to all the devices. If you touch the same device again you will toggle through the selections of all the "Device Groups" that device belongs to, and finally un-select the device. For example, let's assume you have a light "Front Porch". You create a Device Group in [[LinuxMCE Admin Website]] called "Outdoor devices" which includes all outdoor devices, like the pool and all outdoor lights. You create another device group called "Front yard Lights" that has just the lights in the front yard. This light, "Front Porch", is a member of both groups. So the first time you touch the "Front Porch" on the floorplan it will be selected alone. The second time all other lights in the group "Outdoor devices" will be selected. The third time all lights in the group "Front yard Lights". The fourth time nothing will be selected. This allows you to create groups containing many devices you normally control all at once so you don't need to select them one at a time on the floorplan.

==Programmer's guide==
==Additional Information==
* [[Lighting Scenarios]]
* [[Advanced Lighting Settings]]
* [[Have my lighting or climate settings follow me]]
* [[Control lights/climate using scenarios]]

[[Category: Automation]]
[[Category: Programmer's Guide]]
[[Category: Tutorials]]
[[Category: Lighting]]
[[Category: Climate]]

Floorplans

2009-08-13T14:06:44Z

Buckle: /* Recommended Floorplan Size */ Removed JPEG as file type.

[[Image:Floorplan.jpg|thumb|250px|Floorplan Wizard Page Admin Website]]On the main menu on your Orbiters are floorplans for Lighting, Media, Climate, Security and Telecom. These show the devices in your entire house at a glance and let you control them all individually, or as a group.
You can also have many different floorplans. For example, if you have a large house, it might be easier to break the floorplan into a "North" and "South". Or another floorplan for the grounds. The floorplans are simply bitmap graphics that you create. 
Choose the 'Add another floorplan' link to add a floorplan. You will need to give the floorplan a name, like "First Floor", "Second Floor", "Gardens", etc. Then you will specify where the bitmap file is on your local pc, or choose browse to find it. If you want to use some sample floorplans that LinuxMCE created, copy and paste the links at the bottom of this page. If you use LinuxMCE to create your floorplans, your floorplans will look similar to this and the interior colors, finishes and furnishings will match what you have in your home.
Then use the left pull-down to pick a floorplan, and the right pull-down to pick the type of device. If you choose "2nd Floor" and "Lighting", for example, the wizard will show the floorplan called "2nd Floor" and a list of all the lighting devices in your home. Then you can drag the device from the list on the left and drop it on the floorplan. Move devices using drag and drop. If you want to remove a device from the floorplan just drag it and drop it off the floorplan. Position whatever devices you want to appear on that floorplan, and do not worry about the rest. For example, you may want to put your outside lights on the "Gardens" floorplan, and your first floor lights on the "First floor" floorplan. However, LinuxMCE lets you position any device anywhere without restriction. If you do not put a device on a particular floorplan, then you will not be able to control that device from that floorplan's interactive map.
When you touch the "floorplan" button on the Orbiter (the buttons in the left column) you will see your floorplan with little icons for all the devices. Which icons appear are based on your selection on the device page. For example on the "Wizard/Devices/Lighting" page you can specify for each light if it's a chandelier, ceiling light, accent light, etc., and that will determine which icon is drawn on the floorplan. Refer to the [[Orbiter User's manual]] for instructions on using the floorplans.

==Floorplan Assistance==
You can request assistance from the community, or from the two companies listed below.
 For the UK contact Convergent Home Technologies
 For Germany contact DE Centersonic

==Recommended Floorplan Size==
*Make them roughly square around 1200 x 1200 px--it can be smaller but then OrbiterGen will have to stretch them for high-res displays and they may not look as good.
*Save as PNG.
*See [[Control_lights_or_climate_with_a_floorplan]]

[[Category: Admin Website]]

Floorplans

2009-08-12T20:50:09Z

Buckle:

[[Image:Floorplan.jpg|thumb|250px|Floorplan Wizard Page Admin Website]]On the main menu on your Orbiters are floorplans for Lighting, Media, Climate, Security and Telecom. These show the devices in your entire house at a glance and let you control them all individually, or as a group.
You can also have many different floorplans. For example, if you have a large house, it might be easier to break the floorplan into a "North" and "South". Or another floorplan for the grounds. The floorplans are simply bitmap graphics that you create. 
Choose the 'Add another floorplan' link to add a floorplan. You will need to give the floorplan a name, like "First Floor", "Second Floor", "Gardens", etc. Then you will specify where the bitmap file is on your local pc, or choose browse to find it. If you want to use some sample floorplans that LinuxMCE created, copy and paste the links at the bottom of this page. If you use LinuxMCE to create your floorplans, your floorplans will look similar to this and the interior colors, finishes and furnishings will match what you have in your home.
Then use the left pull-down to pick a floorplan, and the right pull-down to pick the type of device. If you choose "2nd Floor" and "Lighting", for example, the wizard will show the floorplan called "2nd Floor" and a list of all the lighting devices in your home. Then you can drag the device from the list on the left and drop it on the floorplan. Move devices using drag and drop. If you want to remove a device from the floorplan just drag it and drop it off the floorplan. Position whatever devices you want to appear on that floorplan, and do not worry about the rest. For example, you may want to put your outside lights on the "Gardens" floorplan, and your first floor lights on the "First floor" floorplan. However, LinuxMCE lets you position any device anywhere without restriction. If you do not put a device on a particular floorplan, then you will not be able to control that device from that floorplan's interactive map.
When you touch the "floorplan" button on the Orbiter (the buttons in the left column) you will see your floorplan with little icons for all the devices. Which icons appear are based on your selection on the device page. For example on the "Wizard/Devices/Lighting" page you can specify for each light if it's a chandelier, ceiling light, accent light, etc., and that will determine which icon is drawn on the floorplan. Refer to the [[Orbiter User's manual]] for instructions on using the floorplans.

==Floorplan Assistance==
You can request assistance from the community, or from the two companies listed below.
 For the UK contact Convergent Home Technologies
 For Germany contact DE Centersonic

==Recommended Floorplan Size==
*Make them roughly square around 1200 x 1200 px--it can be smaller but then OrbiterGen will have to stretch them for high-res displays and they may not look as good.
*Save as PNG(or maybe JPG).
*See [[Control_lights_or_climate_with_a_floorplan]]

[[Category: Admin Website]]

TV Card Comparison

2009-07-07T14:59:28Z

Buckle:

{{stub}}
[[Category: Hardware ]]
[[Category: Video Capture Boards]]
[[Category: TV Cards ]]

The purpose of this page is to sumarise the currently supported / tested TV cards. This is intended to allow a quick comparison for those who are not neccessarily familiar with all the available models.

Please get involved and update as appropriate!

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Model
! Make / Manufacturer
! Connection Type
! DVB-S
! DVB-S2
! DVB-T
! DVB-C
! Analog
! Composite
! 710
! 810
|-
| [[Hauppauge_WinTV_Nova-SE2|WinTV Nova-SE2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| Unknown
| Supported
|-
| [[Hauppauge_WinTV-Nova-HD-S2|WinTV Nova-HD-S2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| Working
| Unknown
|-
| [[Hauppauge_WinTV-PVR-150_MCE|WinTV PVR-150 MCE]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| Supported
| Supported
|-
| [[Hauppauge_WinTV-PVR-250|WinTV PVR-250]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| Unknown
| Unknown
|-
| Pinnacle PCTV 310i
| Pinnacle
| PCI
| No
| No
| Yes
| No
| Yes
| No
| Working
| Working
|-
| [[Kworld_KW-DVB-T_399U|KWorld U399]]
| KWorld
| USB
| No
| No
| Yes x2
| No
| No
| No
| Working
| In development
|-
| [[DViCO_FusionHDTV7_Dual_Express|FusionHDTV7 Dual Express]]
| DViCO
| PCI Express x1
| No
| No
| No (2x ATSC)
| No
| Yes NTSC
| Yes
| Unknown
| Unknown
|}

Statuses:
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Status
! Meaning
|-
| Unknown
| The status of this card with this version is not known to whoever added this card. If you know otherwise, '''PLEASE UPADTE!'''
|-
| Unsupported
| No work has yet been done integrating on this version
|-
| Working
| Works with this version, but requires manual configuration / driver updates etc.
|-
| In development
| As Working, but development work is in progress to add this card and make it PNP
|-
| Supported
| Works "Out of the box" so a good choice for newbies :-)
|}

TV Card Comparison

2009-07-07T14:56:40Z

Buckle:

{{stub}}
[[Category: Hardware ]]
[[Category: Video Capture Boards]]
[[Category: TV Cards ]]

The purpose of this page is to sumarise the currently supported / tested TV cards. This is intended to allow a quick comparison for those who are not neccessarily familiar with all the available models.

Please get involved and update as appropriate!

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Model
! Make / Manufacturer
! Connection Type
! DVB-S
! DVB-S2
! DVB-T
! DVB-C
! Analog
! Composite
! 710
! 810
|-
| [[Hauppauge_WinTV_Nova-SE2|WinTV Nova-SE2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| Unknown
| Supported
|-
| [[Hauppauge_WinTV-Nova-HD-S2|WinTV Nova-HD-S2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| Working
| Unknown
|-
| [[Hauppauge_WinTV-PVR-150_MCE|WinTV PVR-150 MCE]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| Supported
| Supported
|-
| [[Hauppauge_WinTV-PVR-250|WinTV PVR-250]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| Unknown
| Unknown
|-
| Pinnacle PCTV 310i
| Pinnacle
| PCI
| No
| No
| Yes
| No
| Yes
| No
| Working
| Working
|-
| [[Kworld_KW-DVB-T_399U|KWorld U399]]
| KWorld
| USB
| No
| No
| Yes x2
| No
| No
| No
| Working
| In development
|-
| [[DViCO_FusionHDTV7_Dual_Express|FusionHDTV7 Dual Express]]
| DViCO
| PCI Express x1
| ?
| ?
| ?
| ?
| ?
| ?
| Unknown
| Unknown
|}

Statuses:
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Status
! Meaning
|-
| Unknown
| The status of this card with this version is not known to whoever added this card. If you know otherwise, '''PLEASE UPADTE!'''
|-
| Unsupported
| No work has yet been done integrating on this version
|-
| Working
| Works with this version, but requires manual configuration / driver updates etc.
|-
| In development
| As Working, but development work is in progress to add this card and make it PNP
|-
| Supported
| Works "Out of the box" so a good choice for newbies :-)
|}

Talk:Mainboard Comparison

2009-07-07T14:13:56Z

Buckle: New page: * ZOTAC GF8200-C-E - I'm not sure what the audio chipset is at the moment. I'll have to update it later. Also, I listed this as a MD in 0810, but it could easily be used as a hybrid if l...

* ZOTAC GF8200-C-E - I'm not sure what the audio chipset is at the moment. I'll have to update it later. Also, I listed this as a MD in 0810, but it could easily be used as a hybrid if limited IO options isn't going to hold you back. - Buckle

DViCO FusionHDTV7 Dual Express

2009-06-12T22:43:21Z

Buckle:

[[Category: Hardware]]
[[Category: TV_Cards]]
[[Category: Video]]

==General==

* Dual tuners - record/watch multiple channels at once. XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC)

* PCI-Express x1

* Conexant CX23385

* Samsung S5H1441

* $139.99 USD + shipping (as of 12 JUN 2009) [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]

==PCI Device Info==

04:00.0 0400: '''14f1:8852''' (rev 04)
Subsystem: '''18ac:d618'''
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data <?>
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [200] Virtual Channel <?>
Kernel driver in use: cx23885
Kernel modules: cx23885

==Links==
* Product Page [http://www.fusionhdtv.co.kr/ENG/products/HDTV7DualExpress.aspx]
* Newegg [http://www.newegg.com/Product/Product.aspx?Item=N82E16815135001]
* XC5000 Firmware [http://www.steventoth.net/linux/xc5000/]
* linuxtv wiki [http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV7_Dual_Express]
* [http://www.mythtv.org/pipermail/mythtv-users/2008-August/229796.html]

DViCO FusionHDTV7 Dual Express

2009-06-12T22:18:35Z

Buckle: New page: ====DViCO FusionHDTV7 Dual Express==== <pre> Dual XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC) PCI-Express x1 Conexant CX23385 Samsung S5H1441 </pre> ==PCI Device Info== 04:00.0 0400:...

====DViCO FusionHDTV7 Dual Express====

<pre>
Dual XC5000 Silicon Tuner (ATSC/ClearQAM/NTSC)

PCI-Express x1

Conexant CX23385

Samsung S5H1441
</pre>

==PCI Device Info==

04:00.0 0400: '''14f1:8852''' (rev 04)
Subsystem: '''18ac:d618'''
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fe800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data <?>
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [200] Virtual Channel <?>
Kernel driver in use: cx23885
Kernel modules: cx23885