Slashdot Mirror
HDTV Reception Now Available on Linux
-tji writes "A new company, www.pchdtv.com, has just released the first digital TV receiver card for Linux. Along with the Linux drivers, they have also modified xine to support HD playback and add XvMC support for MPEG2 hardware acceleration with some video cards. This has great potential for integration into PVR apps, like freevo and mythtv. There is also another project to reverse engineer drivers for the Teralogic TL880 based DTV cards. The one active developer has done a great job, but could use some help."
But does anyone know what the status of v4l is in the 2.6 series? I went from 2.4.21 to 2.6.0-test3 (and now test4) as the HPT370 controller is iffy on Linux with APIC (this is an Epox EP-D3VA)... 2.6.0 completely solved all the APIC and SMP issues, but now V4L's not quite there. :-)
Ahh, the bleeding edge...
Not every company is willing to open source all their software and make it free. If we want many of the commercial software companies to take Linux seriously, we have to convey the message that we find it acceptable to pay for some software that will run in Linux.
Until then, they will continue to develop only for OSes like Windows and MacOS.
I find that very acceptable. But you made a magic mistake.
driver!=software
I for one write just as OSS as proprietary (both for Linux). The only real need in being open is to be open to correct extent.
If drivers are proprietary and company goes to drain, your hardware goes with company too. Just look at older TV Tuners under XP. No drivers no fun. But if drivers are made as OSS someone might continue to support your hardware even then.
As far as I was talking about sotware needing to be open to the correct extent. Take two this as example.
Accounting software >> can be proprietary, the only thing that must be open are correctly documented tables and their relations.
Software for editing some type of file >> Make a complete specification of document type.
There are points that company must revise.
1. What will happen if they go down with their customers, I was there and to tell you the truth as a customer I didn't liked it. That's why I had to drag one machine running Win3.1 until a year ago, It was the only possibility to access documents that were made.
2. Let's take something more simple now. You're the one man band and you're administering servers on companies. You die in a car crash. Do customers have to break in to continue to work. Or would it be more simple to use an envelope, write password in and protect it to be used just in case.
As far as paying, my customers were paying me when I was making Win software, and they are paying me now. Where's the difference?
Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
First, for "Win-" hardware, like controllerless modems and printers, companies are afraid if their driver was open-source, it would be simple for their competitors to use, reducing their software development costs. Two solutions: one, the company could GPL it, so at least they'd get any improvements. Or (more likely), someone should make a GPL driver core, which could be attached to similar dumb hardware, even of different brands. Then, with open specs, it would be easy to bind the hardware to the core to the kernel, and the company may even find it cheaper to adapt the open version for all OSs. (Aside: would Microsoft sign drivers with GPL cores?)
The other problem is that companies fear open-source drivers won't honor the evil bit, for example, WiFi cards with hacked drivers operating on forbidden frequencies, or video cards not honoring MacroVision signals. For starters, it's almost as easy to hack binary drivers, so it's no protection. Another solution is to make the hardware only accept register sets signed by the manufacturer's private key. This was proposed for WiFi cards, is better protection anyway, and can be used by open-source projects.
Litigious bastards