Tapani Pälli kirjoitti 11.4.2024 klo 6.05:
On 11.4.2024 1.15, Brian Paul wrote:
On 4/10/24 13:53, Timo Aaltonen wrote:
Brian Paul kirjoitti 6.4.2024 klo 1.05:
I'm trying to build the Intel Vulkan driver. First time in a few
months. I'm having build problems related to clc. I&#
Brian Paul kirjoitti 6.4.2024 klo 1.05:
I'm trying to build the Intel Vulkan driver. First time in a few
months. I'm having build problems related to clc. I'm on Ubuntu 22.04
[...]
[1347/3181] Generating src/intel/vulkan/...om command (wrapped by meson
to set env)
FAILED:
src/intel/vulkan
Hi, it's been a month without a new rc, when do we get one?
Dylan Baker kirjoitti 18.8.2022 klo 21.47:
Hi list,
I didn't get this out yesterday, but here's mesa 22.2.0-rc3. We've got a
huge number of fixes for turnip, a good number of fixes for
gallium/nine, as well as a bit of this and that
Dylan Baker kirjoitti 7.12.2021 klo 1.51:
Since classic is gone, I thought I'd lay out my thinking for Amber.
I'm assuming that we'll branch Amber from the 21.3 branch, after that
reaches normal EOL. That gives us the benefit of developing on top of a
known good state for classic drivers, and s
On 19.8.2021 20.06, Dylan Baker wrote:
Hi list,
I'd like to announce the availability of Mesa 21.2.1. This is the first
bug fix release in the mesa 21.2 series. This is a day late, as I was
tracking down some CI failures, which turned out to be fixed tests that
just needed aditional backports fo
On 21.4.2021 21.25, Dylan Baker wrote:
Hi list,
Mesa 21.0.3 is now available. This features quite a few backports done
by helpful mesa devlopers, so a big thank you to all of them. We've got
a bunch of stuff here, from haiku, to core mesa, radeonsi, lavapipe,
nir, radv, anv, freedreno and turnip
On 1.2.2019 13.08, Emil Velikov wrote:
> Hi Carsten,
>
> On 2019/01/31, Carsten Haitzler wrote:
>> On Wed, 30 Jan 2019 18:33:35 + Emil Velikov
>> said:
>>
>> You might want to hold off on this. My bugfix was actually patched out by
>> partly
>> removing some of it. The void ptr math should
On 18.12.2018 7.52, Stuart Young wrote:
> Hi Dylan,
>
> Can't speak on Timo's behalf, but looking at the build logs for 18.3.0
> (which is patched with these patches), it built fine on ppc64el (Little
> Endian PPC64), but hurd is having issues, tho it looks like it's not
> directly related to the
On 4.12.2018 23.52, Dylan Baker wrote:
> This little series is aimed at fixing problems reported by fedora and debian
> when using meson, there's a couple of patches in here for fixing ppc64
> detection
> (tested without llvm), and a couple for gnu hurd (not tested).
>
> Dylan Baker (5):
> meso
On 3.12.2018 20.54, Dylan Baker wrote:
> Quoting Timo Aaltonen (2018-12-03 10:36:12)
>> On 3.12.2018 20.25, Emil Velikov wrote:
>>> On Mon, 3 Dec 2018 at 17:49, Dylan Baker wrote:
>>>>
>>>> Quoting Emil Velikov (2018-12-03 07:54:38)
>>>>&g
On 3.12.2018 20.25, Emil Velikov wrote:
> On Mon, 3 Dec 2018 at 17:49, Dylan Baker wrote:
>>
>> Quoting Emil Velikov (2018-12-03 07:54:38)
>>> Hi all,
>>>
>>> On Thu, 29 Nov 2018 at 17:44, Emil Velikov wrote:
Hi all,
I can see why people may opt to not use or maintain the auto
On 29.11.2018 20.22, Matt Turner wrote:
> On Thu, Nov 29, 2018 at 9:47 AM Emil Velikov wrote:
>> In Mesa, we have different parts not used by different teams. As such
>> we tend to remove stuff when nobody is around to maintain it anymore.
>
> We drop things for that reason, but also when somethi
On 27.11.2018 19.42, Eero Tamminen wrote:
> Hi,
>
> On 27.11.2018 19.05, Matt Turner wrote:
>> On Tue, Nov 27, 2018 at 1:13 AM Timo Aaltonen
>> wrote:
>>> On 17.11.2018 6.04, Dylan Baker wrote:
>>>> Quoting Dylan Baker (2018-09-17 09:44:07)
>>>
On 27.11.2018 19.05, Matt Turner wrote:
> On Tue, Nov 27, 2018 at 1:13 AM Timo Aaltonen wrote:
>>
>> On 17.11.2018 6.04, Dylan Baker wrote:
>>> Quoting Dylan Baker (2018-09-17 09:44:07)
>>>> I feel like for !windows meson is in good enough shape at this point
On 27.11.2018 12.20, Erik Faye-Lund wrote:
> On Tue, 2018-11-27 at 11:13 +0200, Timo Aaltonen wrote:
>> On 17.11.2018 6.04, Dylan Baker wrote:
>>> Quoting Dylan Baker (2018-09-17 09:44:07)
>>>> I feel like for !windows meson is in good enough shape at this
>>&g
On 17.11.2018 6.04, Dylan Baker wrote:
> Quoting Dylan Baker (2018-09-17 09:44:07)
>> I feel like for !windows meson is in good enough shape at this point that we
>> can start having the discussion about deleting the autotools build. So, is
>> there
>> anything left that autotools can do that meso
Vugt
> Signed-off-by: Thomas Hellstrom
Tested-by: Timo Aaltonen
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On 24.10.2017 19:06, Chris Wilson wrote:
> Through the use of mocs, we can define the cache usage for any surface
> used by the GPU. In particular, we can request that L3 cache be
> allocated for either a read/write miss so that subsequent reads can be
> fetched from cache rather than memory. A con
e makefile, the only change that would affect a
> non-libglvnd build is for the client extension string in eglQueryString.
Ping? Surely these can land in master by now? Fedora ships them, and
they work fine on Debian too, so:
Tested-by: Timo Aaltonen
--
t
_
On 13.01.2017 07:40, Emil Velikov wrote:
> On 12 January 2017 at 10:29, Timo Aaltonen wrote:
>> On 11.01.2017 15:01, Emil Velikov wrote:
>>> On 6 December 2016 at 14:55, Marek Olšák wrote:
>>>> Hi,
>>>>
>>>> I'd like to announce that t
On 11.01.2017 15:01, Emil Velikov wrote:
> On 6 December 2016 at 14:55, Marek Olšák wrote:
>> Hi,
>>
>> I'd like to announce that this release doesn't fix the worst GPU
>> hangs/freezes it has. I'm talking about all Gallium drivers here.
>> There was a bug recently discovered in shared code that l
On 05.01.2017 23:29, Kyle Brenneman wrote:
> ---
> src/egl/generate/eglFunctionList.py | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/src/egl/generate/eglFunctionList.py
> b/src/egl/generate/eglFunctionList.py
> index b19b5f7..80cb834 100644
> --- a/src/egl/genera
On 29.09.2016 18:10, Jason Ekstrand wrote:
> On Sep 28, 2016 11:44 PM, "Timo Aaltonen" <mailto:tjaal...@ubuntu.com>> wrote:
>>
>> On 28.09.2016 21:53, Marek Olšák wrote:
>> > Hi,
>> >
>> > It's been almost 4 months since the 12.0
On 28.09.2016 21:53, Marek Olšák wrote:
> Hi,
>
> It's been almost 4 months since the 12.0 branch was created, and soon
> it will have been 3 months since Mesa 12.0 was released.
>
> Is there any reason we haven't created the stable branch yet?
>
> Ideally, we would time the release so that it's
On 21.06.2016 02:17, Vedran Miletić wrote:
> setLangDefaults() now requires PreprocessorOptions as an argument.
> ---
> src/gallium/state_trackers/clover/llvm/invocation.cpp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/gallium/state_trackers/clover/llvm/invocation.
On 01.09.2016 19:47, Emil Velikov wrote:
> On 1 September 2016 at 17:34, Timo Aaltonen wrote:
>> On 01.09.2016 17:25, Emil Velikov wrote:
>>> Hello list,
>>>
>>> The candidate for the Mesa 12.0.2 is now available.
>>
>> Forgot to push the tag
On 01.09.2016 17:25, Emil Velikov wrote:
> Hello list,
>
> The candidate for the Mesa 12.0.2 is now available.
Forgot to push the tag?
--
t
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-
hen run on a desktop
Skylake, so
Tested-by: Timo Aaltonen
--
t
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
= vgrf(glsl_type::uint_type);
> + fs_reg payload = fs_reg(GRF, alloc.allocate(1));
>
> /* We have to use a message header on Skylake to get SIMD4x2 mode.
>* Reserve space for the register.
Yup, tested on both master and with s/alloc.allocate/virtual_grf_alloc/
on
On 08.04.2014 00:31, Timo Aaltonen wrote:
> On 12.03.2014 10:43, Kenneth Graunke wrote:
>> arekm reported that using Chrome with GPU acceleration enabled on GM45
>> triggered the hw_ctx != NULL assertion in brw_get_graphics_reset_status.
>>
>> We definitely do
Yep, fixed!
Tested-by: Timo Aaltonen
On 10.04.2014 08:54, Kenneth Graunke wrote:
> The _Xmin/_Xmax/_Ymin/_Ymax values need to be guarded by _NEW_SCISSOR.
>
> Fixes Piglit's scissor-many, and rendering in GNOME Shell.
> Hopefully fixes similar issues with Unity and Chrome
On 12.03.2014 10:43, Kenneth Graunke wrote:
> arekm reported that using Chrome with GPU acceleration enabled on GM45
> triggered the hw_ctx != NULL assertion in brw_get_graphics_reset_status.
>
> We definitely do not want to advertise reset notification support on
> Gen4-5 systems, since it needs
32 matches
Mail list logo
