On Wed, Jan 20, 2016 at 02:46:39PM -0800, Bryce Harrington wrote:
> From: Bryce Harrington
>
> When doing practice runs of the script, we aren't going to be uploading
> anything, so don't treat it as a fatal error if the tarball is already
> uploaded, as this may hide potential subsequent issues
From: Bryce Harrington
Signed-off-by: Bryce Harrington
---
release.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/release.sh b/release.sh
index ef384de..0a1c607 100755
--- a/release.sh
+++ b/release.sh
@@ -595,7 +595,7 @@ process_module() {
if [ "x$FORCE" = "
From: Bryce Harrington
When doing practice runs of the script, we aren't going to be uploading
anything, so don't treat it as a fatal error if the tarball is already
uploaded, as this may hide potential subsequent issues that the user
should know about.
Signed-off-by: Bryce Harrington
---
rele
As of v4 of this extension, any GLES version number may be requested (to
enable GLES3 and later). To comply with this, simply remove the API
version checks and leave it to the DRI driver to validate. This happens
to also enable using GLES1 in direct contexts, so if that's the dire
situation you fin
On Wed, Jan 20, 2016 at 2:47 PM, Adam Jackson wrote:
> On Tue, 2016-01-19 at 10:06 -0500, Ilia Mirkin wrote:
>> dEQP tests request a specific version. The EXT spec has been updated to
>> allow other versions, so allow anything >= 2.0 to be requested.
>
> (Comic book guy voice) Actually...
>
>>
On Wed, 2016-01-20 at 14:53 -0500, Ilia Mirkin wrote:
> That said, if you believe the only thing that needs to be done to (on
> the X server side) support ES1 with GLX is to remove that return,
> more than happy to send another patch that always lets it succeed.
I think letting any ES version suc
On Tue, 2016-01-19 at 10:06 -0500, Ilia Mirkin wrote:
> dEQP tests request a specific version. The EXT spec has been updated to
> allow other versions, so allow anything >= 2.0 to be requested.
(Comic book guy voice) Actually...
> case GLX_CONTEXT_ES2_PROFILE_BIT_EXT:
The spec says:
>
On 20/01/16 03:57, Michel Dänzer wrote:
On 16.01.2016 02:03, Keith Packard wrote:
Michel Dänzer writes:
From: Michel Dänzer
When a window moves from one CRTC to another, present_window_to_crtc_msc
updates window_priv->msc_offset according to the delta between the
current MSC values of the o
