Results 1 to 5 of 5

Thread: NVIDIA Proposes Extending RandR

  1. #1
    Join Date
    Jan 2007
    Posts
    15,136

    Default NVIDIA Proposes Extending RandR

    Phoronix: NVIDIA Proposes Extending RandR

    While NVIDIA's proprietary driver for their GeForce/Quadro hardware still lacks RandR 1.2+ support (that will hopefully change when RandR 1.4 is finally out), NVIDIA has proposed extending RandR to support over-scan compensation. This support isn't for their mainline NVIDIA binary driver but rather their TEGRA Linux driver...

    http://www.phoronix.com/vr.php?view=OTY4MQ

  2. #2
    Join Date
    Nov 2008
    Posts
    776

    Default

    The first two replies are interesting. Apparently, radeon and intel already solved this issue without extending randr.

    http://lists.x.org/archives/xorg-dev...ly/023897.html
    http://lists.x.org/archives/xorg-dev...ly/023899.html

    In other words: aaron wants to implement underscan, but doesn't know how to do it. He asks for help and throws a few ideas around (interestingly not including the ideas the other drivers used).

    The thread is very far from actually proposing an XRandR extension.

  3. #3
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    930

    Default

    At least we now know why the nvidia blob still lacks proper randr support...

  4. #4
    Join Date
    May 2010
    Posts
    126

    Default Standard under/overscan support... win

    This would be a great feature if it was supported across the board with xrandr. I have a computer on my tv as a media center, and xbmc can compensate for the overscan but most applications can't and desktop environments (gnome, kde) are very fond of screen edges. I thought it should be something that was in xrandr, but couldn't find any way to do it.

  5. #5
    Join Date
    Oct 2009
    Posts
    2,122

    Default

    While yes, the other drivers have managed to implement underscan support, the glitch is that radeon and intel have done it differently. What I mean by that is that the method is the same, but there is no standardization in the naming of the property to set.

    Further, in neither case is it actually apparent what the actual property names are. At least not by looking at the xrandr documentation.

    As much as I despise nvidia, Plattner has a point.... that it does, in some ways, make sense for xrandr to have a more standardized approach to setting underscan that can be implemented by all the drivers.

    That being said, underscan is obsolete and should be allowed to die. Most LCD TV's support native resolution or (in the very least) implement underscan themselves. For the odd TV that does NOT, strong words should be delivered to the manufacturer along the lines of "WTF you stupid douchebags??!?!?! Get with the program!!!".

    I wouldn't worry too much about implementing support for ancient TV's.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •