This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| johnmarkgurney:hdtv [2011/03/27 17:08] – JuergenLock | johnmarkgurney:hdtv [2021/03/28 07:53] (current) – Third time's a charm. Use preview this time. KubilayKocak |
|---|
| |
| * PCI Devices: | * PCI Devices: |
| * [[http://www.dvico.com/|DViCO]] FusionHDTV5 Lite and [[http://www.fusionhdtv.co.kr/eng/Products/RTLite.aspx|FusionHDTV5 RT Lite]] -- [[HDTV/DViCOFusionHDTV5Lite|Support Information]] | * [[http://www.dvico.com/|DViCO]] FusionHDTV5 Lite and FusionHDTV5 RT Lite (''%%fusionhdtv.co.kr/eng/Products/RTLite.aspx%%'') -- [[JohnMarkGurney/HDTV/DViCOFusionHDTV5Lite|Support Information]] |
| * Ethernet Devices: | * Ethernet Devices: |
| * [[http://www.silicondust.com/|SiliconDust]] [[http://www.silicondust.com/products/hdhomerun|HDHomeRun]] (as of libhdhomerun_20081002, no special options are required to build) | * [[http://www.silicondust.com/|SiliconDust]] [[http://www.silicondust.com/products/hdhomerun|HDHomeRun]] (as of libhdhomerun_20081002, no special options are required to build) |
| ===== Support in Progress ===== | ===== Support in Progress ===== |
| |
| * ATI [[http://ati.amd.com/products/hdtvwonder/index.html|HDTV Wonder]] -- [[HDTV/ATIHDTVWonder|Support Information]] | * ATI [[http://ati.amd.com/products/hdtvwonder/index.html|HDTV Wonder]] -- [[JohnMarkGurney/HDTV/ATIHDTVWonder|Support Information]] |
| |
| ===== Future Work ===== | ===== Future Work ===== |
| |
| Though it would seem that doing tuning and initalization in userland would prevent supporting the V4L API, that isn't the case. We could create a device that passes it's kernel calls to a userland program. That program then would be linked against the userland API, doing the necessary work. The userland daemon would not even have to do extra copies, as it could either obtain mappings to the original processes pages like w/ shared memory. | Though it would seem that doing tuning and initalization in userland would prevent supporting the V4L API, that isn't the case. We could create a device that passes it's kernel calls to a userland program. That program then would be linked against the userland API, doing the necessary work. The userland daemon would not even have to do extra copies, as it could either obtain mappings to the original processes pages like w/ shared memory. |
| | |
| | ---- |
| | |
| | {{tag>InactiveProject}} |
| |