Announcement

Collapse
No announcement yet.

The Linux 3.13 Kernel Is Already Super Exciting

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

  • #11
    Originally posted by Ericg View Post
    This post is gonna come off kinda arrogant, and I really don't mean it to, Alex. All the respect meant.

    To me one of the three things is here...

    Either:

    1) You're mistaken about not having set the variable forever ago and you actually did.
    2) You really didn't set the variable... in which case I'm now questioning whether radeon VDPAU+UVD actually DOES work like you think it does, and as well as you think it does...
    or
    3) Nvidia silently updated VDPAU a long time ago, no one ever saw it, no one at Nvidia ever said anything, and the documentation never got updated.

    I don't know, I'm neither a kernel or a VDPAU dev, I just know what I'm reading from fairly reputable sources.
    My vdpauinfo:
    Code:
     djdoo@linux-13kf:~> vdpauinfo
    display: :0   screen: 0
    API version: 1
    Information string: G3DVL VDPAU Driver Shared Library version 1.0
    
    Video surface:
    
    name   width height types
    -------------------------------------------
    420    16384 16384  NV12 YV12 
    422    16384 16384  UYVY YUYV 
    444    16384 16384  Y8U8V8A8 V8U8Y8A8 
    
    Decoder capabilities:
    
    name               level macbs width height
    -------------------------------------------
    MPEG1                 0  9216  2048  1152
    MPEG2_SIMPLE          3  9216  2048  1152
    MPEG2_MAIN            3  9216  2048  1152
    H264_BASELINE        41  9216  2048  1152
    H264_MAIN            41  9216  2048  1152
    H264_HIGH            41  9216  2048  1152
    VC1_SIMPLE            1  9216  2048  1152
    VC1_MAIN              2  9216  2048  1152
    VC1_ADVANCED          4  9216  2048  1152
    
    Output surface:
    
    name              width height nat types
    ----------------------------------------------------
    B8G8R8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R8G8B8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    R10G10B10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    B10G10R10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 
    
    Bitmap surface:
    
    name              width height
    ------------------------------
    B8G8R8A8         16384 16384
    R8G8B8A8         16384 16384
    R10G10B10A2      16384 16384
    B10G10R10A2      16384 16384
    A8               16384 16384
    
    Video mixer:
    
    feature name                    sup
    ------------------------------------
    DEINTERLACE_TEMPORAL             -
    DEINTERLACE_TEMPORAL_SPATIAL     -
    INVERSE_TELECINE                 -
    NOISE_REDUCTION                  y
    SHARPNESS                        y
    LUMA_KEY                         -
    HIGH QUALITY SCALING - L1        -
    HIGH QUALITY SCALING - L2        -
    HIGH QUALITY SCALING - L3        -
    HIGH QUALITY SCALING - L4        -
    HIGH QUALITY SCALING - L5        -
    HIGH QUALITY SCALING - L6        -
    HIGH QUALITY SCALING - L7        -
    HIGH QUALITY SCALING - L8        -
    HIGH QUALITY SCALING - L9        -
    
    parameter name                  sup      min      max
    -----------------------------------------------------
    VIDEO_SURFACE_WIDTH              y        48     2048
    VIDEO_SURFACE_HEIGHT             y        48     1152
    CHROMA_TYPE                      y  
    LAYERS                           y         0        4
    
    attribute name                  sup      min      max
    -----------------------------------------------------
    BACKGROUND_COLOR                 y  
    CSC_MATRIX                       y  
    NOISE_REDUCTION_LEVEL            y      0.00     1.00
    SHARPNESS_LEVEL                  y     -1.00     1.00
    LUMA_KEY_MIN_LUMA                y  
    LUMA_KEY_MAX_LUMA                y
    opensuse 12.3 kernel 3.12 final Mesa 10 and libvdpau-r600 package installed

    Comment


    • #12
      Originally posted by djdoo View Post
      opensuse 12.3 kernel 3.12 final Mesa 10 and libvdpau-r600 package installed
      Whats the output of

      echo $VDPAU_DRIVER ?

      or check /etc/profile.d to see if there's anything that automatically sets VDPAU_DRIVER to be r600 once you've installed the "libvdpau-r600" package
      All opinions are my own not those of my employer if you know who they are.

      Comment


      • #13
        Just to make it clear, is PowerXPress making it into 3.13?

        Comment


        • #14
          Originally posted by Ericg View Post
          Whats the output of

          echo $VDPAU_DRIVER ?

          or check /etc/profile.d to see if there's anything that automatically sets VDPAU_DRIVER to be r600 once you've installed the "libvdpau-r600" package
          echo output nothing, /etc/profile nothing

          Comment


          • #15
            Just to make it clear that i'm not on a like witch-hunt, Djdoo & Alex, I'm not saying with some like iron grip of surety that you guys -are wrong.- But SOMETHING is wrong, maybe its you guys, maybe its Fedora / Arch / Gentoo / Nvidia's docs (First two being my distros of choice, and Gentoo being in there because I referenced their wiki), but someone, somewhere, changed something and didn't update the docs, or DIDN'T do something they should have.

            And I'm now really curious to figure out what exactly DID happen with this, and would LOVE to find out.
            All opinions are my own not those of my employer if you know who they are.

            Comment


            • #16
              Originally posted by djdoo View Post
              echo output nothing, /etc/profile nothing
              output of:

              Code:
              sudo updatedb
              locate libvdpau_
              ?
              All opinions are my own not those of my employer if you know who they are.

              Comment


              • #17
                You do realise that the Nvdia docs you and the Gentoo wiki are refering to are from 2010? So there you have your answer. Now can stop your witchhunt

                Comment


                • #18
                  Originally posted by AnonymousCoward View Post
                  You do realise that the Nvdia docs you and the Gentoo wiki are refering to are from 2010? So there you have your answer. Now can stop your witchhunt
                  The Radeon section of the Gentoo wiki would've been updated when 3.11 came out a couple months ago.

                  Arch also updated THEIR wiki and also mention setting the VDPAU_DRIVER environment variable for r600: https://wiki.archlinux.org/index.php...o_acceleration

                  Also, here, Nvidia Docs from earlier this year: ftp://download.nvidia.com/XFree86/Li...DME/README.txt

                  Control-F: "VDPAU_DRIVER"

                  The VDPAU wrapper library is responsible for determining which vendor-specific
                  driver to load for a given X11 display/screen. At present, it hard-codes
                  "nvidia" as the driver. The environment variable VDPAU_DRIVER may be set to
                  override this default. The actual library loaded will be
                  libvdpau_${VDPAU_DRIVER}.so. Setting VDPAU_DRIVER to "trace" is not advised.
                  Same message they included in the version from before.
                  All opinions are my own not those of my employer if you know who they are.

                  Comment


                  • #19
                    Only thing I can find that MAYBE would handle 'automatically' moving to a non-Nvidia VDPAU driver is: http://cgit.freedesktop.org/~aplattn...b09e6b3dcd981d

                    But thats in his personal git tree, and im not sure it ever got merged mainline. Also, if it was supported by the other drivers and setting VDPAU_DRIVER was a non-issue, why wouldn't the documentation say so?
                    All opinions are my own not those of my employer if you know who they are.

                    Comment


                    • #20
                      Originally posted by Ericg View Post
                      Only thing I can find that MAYBE would handle 'automatically' moving to a non-Nvidia VDPAU driver is: http://cgit.freedesktop.org/~aplattn...b09e6b3dcd981d

                      But thats in his personal git tree, and im not sure it ever got merged mainline.
                      It is in the mainline tree. And both ati and nouveau drivers correctly report their "second DRI2 name", which is used by libvdpau for selecting hardware-specific driver. Intel's X driver reports only one name, thus libvdpau falls back to default value (nvidia) if VDPAU_DRIVER is not set.

                      There is a patch (http://lists.freedesktop.org/archive...st/031872.html) that can help avoid of VDPAU_DRIVER. But as you can see, no one was interested in merging it.

                      Comment

                      Working...
                      X