https://bugs.freedesktop.org/show_bug.cgi?id=109535
Matt Turner changed:
What|Removed |Added
Alias||mesa-19.0
--
You are receiving this mail
Quoting Mark Janes (2019-02-01 17:20:33)
> Eero Tamminen writes:
>
> > Hi,
> >
> > On 31.1.2019 1.37, Dylan Baker wrote:
> >> This email announces the mesa 19.0 release candidate 1. I'll keep this
> >> email
> >> fairly brief since I'm already running a little late on getting this done
> >> :)
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Dylan Baker changed:
What|Removed |Added
Depends on||109216
Referenced Bugs:
https://bugs.fr
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Dylan Baker changed:
What|Removed |Added
Depends on||109517
Referenced Bugs:
https://bugs.fr
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Dylan Baker changed:
What|Removed |Added
Depends on||109505
Referenced Bugs:
https://bugs.fr
https://bugs.freedesktop.org/show_bug.cgi?id=109535
Bug ID: 109535
Summary: [Tracker] Mesa 19.0 release tracker
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=109532
--- Comment #3 from Mark Janes ---
This test was broken in the dEQP suite recently for m32 i965 platforms by:
237916d03377a469e30dd36087738b069f83a19a
Author: xinglong.zhu
Commit: Patrick Shi
CommitDate: Sat Jan 5 12:46:03 2019 +
Jean has logged 3 versions of the same bug in Debian, as he wasn't sure
which package was causing the issues.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921114
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921145
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921004
None of the b
https://bugs.freedesktop.org/show_bug.cgi?id=109532
--- Comment #2 from Ilia Mirkin ---
Looks like this is happening in link_uniform_blocks. The type gets updated:
if (b->array != NULL &&
(b->type->without_array()->interface_packing ==
GLSL_INTERFACE_PACKING_PACKED)) {
The hardware does not natively support FIXED and DOUBLE formats. If
those are used in an indirect draw, they have to be converted. Our
conversion tries to be clever about only converting the data that's
needed. However for indirect, that won't work.
Given that DOUBLE or FIXED are highly unlikely t
On 3/2/19 7:21 am, Andres Gomez wrote:
On Sat, 2019-02-02 at 10:10 +1100, Timothy Arceri wrote:
On 2/2/19 5:05 am, Andres Gomez wrote:
Current implementation uses a complicated calculation which relies in
an implicit conversion to check the integral part of 2 division
results.
However, the c
https://bugs.freedesktop.org/show_bug.cgi?id=109532
--- Comment #1 from Timothy Arceri ---
I believe we split (maybe eliminate unused blocks?). Looks like the shader only
access blockB[1] and not blockB[0] so I assume this has something to do with
it. Probably not updating something correctly whe
On Sat, 2019-02-02 at 10:10 +1100, Timothy Arceri wrote:
> On 2/2/19 5:05 am, Andres Gomez wrote:
> > Current implementation uses a complicated calculation which relies in
> > an implicit conversion to check the integral part of 2 division
> > results.
> >
> > However, the calculation actually che
On Sat, Feb 2, 2019, 12:41 PM Eric Engestrom On Saturday, 2019-02-02 10:32:15 -0500, Marek Olšák wrote:
> > On Sat, Feb 2, 2019, 7:17 AM Eric Engestrom wrote:
> >
> > > On Friday, 2019-02-01 15:42:17 -0500, Marek Olšák wrote:
> > > > If there is no feedback soon, I'll push this.
> > >
> > > Have
On Saturday, 2019-02-02 10:32:15 -0500, Marek Olšák wrote:
> On Sat, Feb 2, 2019, 7:17 AM Eric Engestrom
> > On Friday, 2019-02-01 15:42:17 -0500, Marek Olšák wrote:
> > > If there is no feedback soon, I'll push this.
> >
> > Have you tested that xcb-randr < 1.12 works?
> > Probably shouldn't rem
On Sat, Feb 2, 2019 at 4:13 AM Jean-Dominique Frattini
wrote:
>
> Hello,
>
> I am on Debian Linux testing. And after an update (firmware-amd-graphics,
> xserver-xorg-video-amdgup and Mesa), my program often raises this error
> message:
>
> amdgpu: The CS has been cancelled because the context is
On Sat, Feb 2, 2019, 7:17 AM Eric Engestrom On Friday, 2019-02-01 15:42:17 -0500, Marek Olšák wrote:
> > If there is no feedback soon, I'll push this.
>
> Have you tested that xcb-randr < 1.12 works?
> Probably shouldn't remove a restriction unless you're sure it isn't
> needed :)
>
Is this a jok
On Friday, 2019-02-01 15:42:17 -0500, Marek Olšák wrote:
> If there is no feedback soon, I'll push this.
Have you tested that xcb-randr < 1.12 works?
Probably shouldn't remove a restriction unless you're sure it isn't
needed :)
>
> Marek
>
> On Wed, Jan 30, 2019 at 12:44 PM Erik Faye-Lund <
> e
Hi,
sorry I just saw that there is a similar correction is already in both
19.0 and master branches
but I missed it because I searched only in mesa-dev ML
Please Dylan, just check if the 3rd patch makes sense or not necessary at all.
Mauro
On Sat, Feb 2, 2019 at 11:30 AM Mauro Rossi wrote:
>
> P
Fixes the following build error:
external/mesa/src/mesa/drivers/dri/i965/brw_program.c:45:10:
fatal error: 'compiler/glsl/float64_glsl.h' file not found
#include "compiler/glsl/float64_glsl.h"
^~
1 error generated.
Include of src/compiler in builddir is added
With new glsl/float64_glsl.h include, required in i965 source
to correctly build Android and with automake, inc_compiler is
added in meson build includes.
It may not be necessary for meson, but it is formally correct
Signed-off-by: Mauro Rossi
Fixes: 7d7b308 ("automake: Fix path to generated sour
Porting of commit 7d7b308 ("automake: Fix path to generated source")
to Android build system
Fixes the following building error:
ninja: error:
'.../x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/float64_glsl.h',
needed by
'.../x86/obj/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/fl
Hello,
I am on Debian Linux testing. And after an update (firmware-amd-graphics,
xserver-xorg-video-amdgup and Mesa), my program often raises this error
message:
amdgpu: The CS has been cancelled because the context is lost.
When this message shows up (hundreds of lines are displaying in the con
https://bugs.freedesktop.org/show_bug.cgi?id=109532
Bug ID: 109532
Summary: ir_variable has maximum access out of bounds -- but
it's not out of bounds
Product: Mesa
Version: git
Hardware: Other
OS: All
Align with kernel commits:
5e0f5a58b167 ("drm/i915/cfl: Adding another PCI Device ID.")
03ca3cf8e9aa ("drm/i915/icl: Adding few more device IDs for Ice Lake")
Cc: José Roberto de Souza
Cc: Kenneth Graunke
Cc: Anuj Phogat
Signed-off-by: Rodrigo Vivi
---
include/pci_ids/i965_pci_ids.h | 5
Straight copy from the kernel file.
Add more PCI Device IDs for Coffee Lake, Ice Lake,
and Amber Lake. It also include a reorg on Whiskey Lake IDs.
Align with kernel commits:
5e0f5a58b167 ("drm/i915/cfl: Adding another PCI Device ID.")
03ca3cf8e9aa ("drm/i915/icl: Adding few more device IDs for
We used to pre-set a bunch of extra arguments to a texture instruction
in order to force the RA to allocate a register at the boundary of 4.
However with the levelZero optimization, which removes a LOD argument
when it's uniformly equal to zero, we undid that logic by removing an
extra argument. As
27 matches
Mail list logo
