Announcement

Collapse
No announcement yet.

Intel Next-Gen OSS Drivers Out!

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    That's unfortunate, but is there any downside to not having Macrovision code in the drivers (as mentioned in the link)?

    I'd rather not have Macrovision enabled.

    Comment


    • #17
      Originally posted by James View Post
      That's unfortunate, but is there any downside to not having Macrovision code in the drivers (as mentioned in the link)?

      I'd rather not have Macrovision enabled.
      Without it, you also don't get any hardware accelerated MPEG2/MPEG4 playback either- the technical info has to be "tied together" per the deals all these jokers made with the media companies back a while back. And if you've got control of the Macrovision pieces, you can turn them off, which the media companies don't want. It's all about their control of your use of the content in question- they don't want any "uncontrolled" use, period.

      To be sure, it's not a real loss, per se- but it would have been nice to say, have the headroom to display effortlessly as you're capturing a video feed (i.e. make a MythTV box just that little bit better...), but then we're still going to have to deal with another decade or so of obnoxious media company influence in this area.

      Comment


      • #18
        Originally posted by Svartalf View Post
        Without it, you also don't get any hardware accelerated MPEG2/MPEG4 playback either- the technical info has to be "tied together" per the deals all these jokers made with the media companies back a while back. And if you've got control of the Macrovision pieces, you can turn them off, which the media companies don't want. It's all about their control of your use of the content in question- they don't want any "uncontrolled" use, period.
        Well that and then there is the legal software patent restrictions that into the use of mpeg* decoding functions. With that Intel's hands are tied as much as anybody's elses out there. They very simply cannot call the shots on weither or not to release open source drivers on that, (or at least they are not willing to absorb the costs of buying licenses for every single OSS user that may want to use the code.)

        But personally I couldn't give a crap less. If their mpeg decoding support is that great it will be a simple matter of reverse engineering the binary for it. You couldn't do that in the U.S., but other countries it would be fine legally. Since it's userspace it should be pretty simple.

        They did that with OpenBSD driver's for Intel's newer wifi stuff. Intel released code for the wifi kernel portion, but stuck the binary portion in user space. So it was fine according to the Linux kernel developers. The OBSD developer setup Linux and wrote a program to intercept calls to that binary. that way he was able to figure out to write OBSD drivers without having to actually violate the license by examining the intel binary directly.

        But if it's like the VIA onboard 'mpeg2 accelerator' or whatever.. then the Free software stuff software-only decoders used less cpu time then their 'accelerated' drivers.

        Comment

        Working...
        X