[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Confusing parameters for "xrand --setprovideroffloadsink"
From:       Qu Wenruo <quwenruo.btrfs () gmx ! com>
Date:       2018-12-25 8:09:55
Message-ID: 11add565-1d92-9e83-65aa-558ae71ec44e () gmx ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/mixed)]


Hi,

I'm trying to understand what the parameters of "xrand
--setprovideroffloadsink" means.

Google/Arch shows a lot of eGPU use cases, where user should just exec
"xrandr --setprovideroffloadsink 1 0", to make the secondary GPU to
output to the first one.

However the man page also shows:

  If  sink  is  0x0,  then provider is disconnected from its current
  render offload sink.

I checked the code of xrandr.c, set_name() will first try to
sscanf("0x%x"), and if hit pass it as @xid, while for normal "%d" it
passes the value to @idx, and finally use char*.

I'm wonder what's the difference between @xid and @idx and char* name.

My current guess is, with the listproviders output it would be:

Provider 0: id: 0x5a ... name:Radeon RX 580 Series @ pci:0000:26:00.0
         ^      ^^^^          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
         |       |                         |- name?
         |       |- @xid?
         @idx?

Personally it's pretty confusing at least.

Thanks,
Qu



["signature.asc" (application/pgp-signature)]
[Attachment #8 (text/plain)]

_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[prev in list] [next in list] [prev in thread] [next in thread]