Re: RFC: New libxcvt library

2021-03-26 Thread Keith Packard
Olivier Fourdan  writes:

> Can we consider moving “libxcvt” to the xorg/lib namespace in gitlab?

Seems like a good plan to me; I've had several requests to add CVT
support to xrandr and haven't done so because it would have involved
pulling in a ton of code or creating a library like this :-)

-- 
-keith


signature.asc
Description: PGP signature
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel


RFC: New libxcvt library

2021-03-26 Thread Olivier Fourdan
Hi all,

Currently. the Xorg Xserver has its own implementation of the VESA CVT
standard timing modelines generator in `hw/xfree86/modes/xf86cvt.c`.

That code is placed in its own source file alone because it is also being
used by the `cvt` utility.

Because it's part of the Xorg DDX, Xwayland, which is another DDX also has
a copy of the same code in `hw/xwayland/xwayland-cvt.c`.

Now with Xwayland being a standalone package, mutter which uses the cvt
utility at build time still needs to install `cvt` from Xorg to generate
the modes used in Wayland.

Some time ago, discussing with Jonas Adahl on irc, we thought it would be a
good idea to have that code and utility part of its own standalone project,
to avoid the code duplication and possibly ease contributions.

That was https://gitlab.freedesktop.org/xorg/xserver/-/issues/1142

So I went ahead and did just that, called it “libxcvt” and placed in
https://gitlab.freedesktop.org/ofourdan/libxcvt

I also made a merge request to use that code in the Xserver:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/637

Can we consider moving “libxcvt” to the xorg/lib namespace in gitlab?

Cheers
Olivier
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel


XRandR Verify Active Rate

2021-03-26 Thread re.mcclue
A XRRScreenResources contains multiple XRRModeInfo and RROutput (which with 
XRRGetOutputInfo() effectively means XRROutputInfo). Therefore, a screen can 
have many outputs which in turn, can have many modes. The rate is a property of 
the mode. Because of this many-to-many relationship, how can I determine what 
the active rate is?
In other words:

XRRScreenResources *res = XRRGetScreenResources(display, default_root_window);
  for (int i = 0; i < res->nmode; ++i) {
XRRModeInfo *mode_info = >modes[i];
// How do you verify this is the active rate?
double rate = (double)mode_info->dotClock / ((double)mode_info->hTotal * 
(double)mode_info->vTotal));
  }

Sent with [ProtonMail](https://protonmail.com) Secure Email.___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel