Bug 1295909 - xorg: Glamor driver for virgil
Summary: xorg: Glamor driver for virgil
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-server
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dave Airlie
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-05 18:38 UTC by Ademar Reis
Modified: 2018-04-10 11:50 UTC (History)
6 users (show)

Fixed In Version: xorg-x11-server-1.19.3-11.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 11:48:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0736 0 None None None 2018-04-10 11:50:05 UTC

Description Ademar Reis 2016-01-05 18:38:46 UTC 
We're working to have virtio-gpu (Virgil) fully functional in RHEL 7.3 and for that we need Glamor drivers in Xorg

http://www.freedesktop.org/wiki/Software/Glamor/

I'm not sure what's the minimum version that can be considered stable, this needs to be investigated.
Comment 2 Dave Airlie 2016-02-19 04:47:51 UTC 
Move to xorg-x11-server since any changes needed to support virgl will need to be done there to the -modesetting driver/glamor combo.
Comment 4 Adam Jackson 2017-09-07 17:16:42 UTC 
xserver has had glamor enabled for quite a while, certainly was present already in 7.4. If there are additional fixes needed for virgl in particular please reopen this bug.
Comment 9 errata-xmlrpc 2018-04-10 11:48:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0736
Note You need to log in before you can comment on or make changes to this bug.