Announcement

Collapse
No announcement yet.

Linux DRM Adds Quirk For Dealing With Valve's Index VR Headset

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

  • Linux DRM Adds Quirk For Dealing With Valve's Index VR Headset

    Phoronix: Linux DRM Adds Quirk For Dealing With Valve's Index VR Headset

    With Valve's Index VR headset slated to ship starting in July, this premium $999 USD headset has now been quirk'ed to properly behave under Linux...

    http://www.phoronix.com/scan.php?pag...-Desktop-Quirk

  • #2
    It's kinda silly for each VR headset to need to have its product ID in the kernel for the kernel to not to treat it as a display.

    Comment


    • #3
      Originally posted by Britoid View Post
      It's kinda silly for each VR headset to need to have its product ID in the kernel for the kernel to not to treat it as a display.
      My thoughts exactly.

      Comment


      • #4
        Originally posted by Britoid View Post
        It's kinda silly for each VR headset to need to have its product ID in the kernel for the kernel to not to treat it as a display.
        Not a big deal though. It's just few constants...

        What non-silly solution would you propose, and especially be willing to implement?

        Comment


        • #5
          Originally posted by kravemir View Post

          Not a big deal though. It's just few constants...

          What non-silly solution would you propose, and especially be willing to implement?
          A method for the EDID to tell the display manager that it's not a display.

          Comment


          • #6
            I thought it was a udev rule, not a kernel code

            Comment


            • #7
              Anyone know why there are so many? 17, including 16 in a contiguous block, compared with 16 for all other VR headsets combined.

              I guess it is for future products and maybe past prototypes and Valve are the only VR vendor to really commit to this OS. Perhaps the two screens are presented individually rather than as one so need separate EDIDs but I don't think any other headset has done that.
              Last edited by anth; 07 May 2019, 05:56 PM.

              Comment


              • #8
                Originally posted by Britoid View Post
                It's kinda silly for each VR headset to need to have its product ID in the kernel for the kernel to not to treat it as a display.
                Yeah, there should be some standard EDID-type query you can do to see what class of display it is.

                Comment


                • #9
                  Originally posted by kravemir View Post
                  and especially be willing to implement?
                  Presumably, the classification bits would need to be part of some the DisplayPort (in this case) or HDMI standard.

                  Comment


                  • #10
                    Originally posted by kravemir View Post

                    Not a big deal though. It's just few constants...
                    It actually is a pretty big deal though, this means that you would need a very new Linux kernel while feature-wise it has been supported for multiple versions.

                    When more VR headsets gets released in the future it will be even more silly if for example you need the latest kernel while feature-wise it's been supported for 3 years.

                    Comment

                    Working...
                    X