On Wed, 2019-12-04 at 01:48 -0500, Marek Olšák wrote:
> On Wed., Dec. 4, 2019, 01:20 Tapani Pälli,
> wrote:
> > Hi;
> >
> > On 12/4/19 2:39 AM, Marek Olšák wrote:
> > > Hi,
> > >
> > > Here are 2 proposals to simplify and better optimize the GL-
> > >Gallium
> > > translation.
> > >
> > > 1)
On Thu, 2019-10-17 at 22:24 -0400, Ilia Mirkin wrote:
> In the meanwhile (unless you plan on taking up Jason's suggestion),
> might I recommend some assert's for the unhandled cases so that there
> are no surprises?
Good idea. I sent a MR for it here:
On Fri, 2019-10-18 at 08:57 -0400, Ilia Mirkin wrote:
> On Fri, Oct 18, 2019 at 8:51 AM Erik Faye-Lund
> wrote:
> > On Thu, 2019-10-17 at 22:24 -0400, Ilia Mirkin wrote:
> > > In the meanwhile (unless you plan on taking up Jason's
> > > suggestion),
> &g
; > > On Fri, Oct 18, 2019 at 9:07 AM Ilia Mirkin > > > wrote:
> > > > On Fri, Oct 18, 2019 at 9:04 AM Erik Faye-Lund
> > > > wrote:
> > > > >
> > > > > On Fri, 2019-10-18 at 08:57 -0400, Ilia Mirkin wrote:
> > > >
n Fri, Oct 18, 2019 at 4:08 PM Marek Olšák wrote:
> > On Fri, Oct 18, 2019 at 9:07 AM Ilia Mirkin
> > wrote:
> > > On Fri, Oct 18, 2019 at 9:04 AM Erik Faye-Lund
> > > wrote:
> > > >
> > > > On Fri, 2019-10-18 at 08:57 -0400, Ilia Mir
On Thu, 2019-10-17 at 20:55 -0500, Jason Ekstrand wrote:
> On Thu, Oct 17, 2019 at 10:39 AM Erik Faye-Lund <
> erik.faye-l...@collabora.com> wrote:
> > This is discussed in the merge request thread. Zink currently only
> > support vertex and fragment shaders, so it's the
This is discussed in the merge request thread. Zink currently only support
vertex and fragment shaders, so it's the only place this can occur. If someone
wants to enable this for drivers that supports geometry or tesselation shaders,
they would need to extend this code first. Unless I beat them
On Fri, 2020-02-28 at 13:37 +1000, Dave Airlie wrote:
> On Fri, 28 Feb 2020 at 07:27, Daniel Vetter
> wrote:
> > Hi all,
> >
> > You might have read the short take in the X.org board meeting
> > minutes
> > already, here's the long version.
> >
> > The good news: gitlab.fd.o has become very
On Fri, 2020-02-28 at 11:40 +0200, Lionel Landwerlin wrote:
> On 28/02/2020 11:28, Erik Faye-Lund wrote:
> > On Fri, 2020-02-28 at 13:37 +1000, Dave Airlie wrote:
> > > On Fri, 28 Feb 2020 at 07:27, Daniel Vetter <
> > > daniel.vet...@ffwll.ch>
> > > w
On Fri, 2020-02-28 at 10:43 +, Daniel Stone wrote:
> On Fri, 28 Feb 2020 at 10:06, Erik Faye-Lund
> wrote:
> > On Fri, 2020-02-28 at 11:40 +0200, Lionel Landwerlin wrote:
> > > Yeah, changes on vulkan drivers or backend compilers should be
> > > fairly
> &g
On Fri, 2020-02-28 at 10:47 +0100, Daniel Vetter wrote:
> On Fri, Feb 28, 2020 at 10:29 AM Erik Faye-Lund
> wrote:
> > On Fri, 2020-02-28 at 13:37 +1000, Dave Airlie wrote:
> > > On Fri, 28 Feb 2020 at 07:27, Daniel Vetter <
> > > daniel.vet...@ffwl
Seems like you missed zink
On February 5, 2020 9:36:26 PM GMT+01:00, James Jones
wrote:
>Rather than hard-code a list of all the format
>modifiers supported by any gallium driver in
>the dri state tracker, add a screen proc that
>queries the number of auxiliary planes required
>for a given
b274b4dd9426205066 as denominated
> .pick_status.json: Mark
> 9fea90ad5170dd64376d22a14ac88c392813c96c as denominated
> bin/gen_release_notes.py: fix commit list command
> .pick_status.json: Update to
> 0103f02acb10dcdea23461ba214307a6827a7772
> gitlab-ci: updat
While working on the NIR to DXIL conversion code for D3D12, I've
noticed that we're not exactly doing the best we could here.
First some background:
NIR currently has a few instructions that does kinda the same:
1. nir_op_ufind_msb: Finds the index of the most significant bit,
counting from the
On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote:
> On 05/07/2020 04:33 AM, Erik Faye-Lund wrote:
> > Hey Brian
> >
> > TLDR; are you OK with me moving forward with the rework of
> > mesa3d.org?
>
> Yes...
>
Cool! We've now set up a repo here:
https://gi
On Wed, 2020-05-13 at 06:43 -0600, Brian Paul wrote:
> On 05/13/2020 03:13 AM, Erik Faye-Lund wrote:
> > On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote:
> > > On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote:
> > > > On 05/07/2020 04:33 AM, Erik Faye-L
On Tue, 2020-05-12 at 15:11 +0200, Erik Faye-Lund wrote:
> On Tue, 2020-05-12 at 06:42 -0600, Brian Paul wrote:
> > On 05/12/2020 04:17 AM, Erik Faye-Lund wrote:
> > > On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote:
> > > > On 05/07/2020 04:33 AM, Erik Faye-L
Hey Brian
TLDR; are you OK with me moving forward with the rework of mesa3d.org?
As you hopefully are aware of, I've been working on a new website for
mesa3d.org, split into a "marketing"-frontpage and a documentation
page.
You can read more about the structure and details here if you haven't
On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote:
> On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote:
> > On 05/07/2020 04:33 AM, Erik Faye-Lund wrote:
> > > Hey Brian
> > >
> > > TLDR; are you OK with me moving forward with the rework of
> > &g
ions are
> conformant. That page full of logos makes me concerned that we're
> going to risk getting into trouble. Khronos marketing cares A LOT
> about logos.
As I wrote in the e-mail, I've already clarified the logo-usage with
Khronos. They are happy with it as-is.
> On Thu, M
On Thu, 2020-05-07 at 16:18 +0200, Eric Engestrom wrote:
> On Thursday, 2020-05-07 16:07:00 +0200, Erik Faye-Lund wrote:
> > On Thu, 2020-05-07 at 09:05 -0500, Jason Ekstrand wrote:
> > > Looks shiny but
> > >
> > > We need to be very careful here. One
On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote:
> On 05/07/2020 04:33 AM, Erik Faye-Lund wrote:
> > Hey Brian
> >
> > TLDR; are you OK with me moving forward with the rework of
> > mesa3d.org?
>
> Yes...
Awesome, thanks!
> > As you hopefully a
On Thu, 2020-05-07 at 16:49 +0200, Eric Engestrom wrote:
> On Thursday, 2020-05-07 16:26:19 +0200, Erik Faye-Lund wrote:
> > On Thu, 2020-05-07 at 16:18 +0200, Eric Engestrom wrote:
> > > On Thursday, 2020-05-07 16:07:00 +0200, Erik Faye-Lund wrote:
> > > > On Thu, 20
On Wed, 2020-05-13 at 15:00 +0200, Erik Faye-Lund wrote:
> On Wed, 2020-05-13 at 06:43 -0600, Brian Paul wrote:
> > On 05/13/2020 03:13 AM, Erik Faye-Lund wrote:
> > > On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote:
> > > > On Thu, 2020-05-07 at
On Mon, 2020-08-03 at 12:48 -0500, Jason Ekstrand wrote:
> On Mon, Aug 3, 2020 at 12:42 PM Erik Faye-Lund
> wrote:
> > On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote:
> > > All,
> > >
> > > I'm sure by now you've all seen the articles, LKML mail
On Mon, 2020-08-03 at 10:30 -0500, Jason Ekstrand wrote:
> All,
>
> I'm sure by now you've all seen the articles, LKML mails, and other
> chatter around inclusive language in software. While mesa doesn't
> provide a whole lot of documentation (hah!), we do have a website, a
> code-base, and a
I second the request :-)
Jul 31, 2020 16:15:05 Mike Blumenkrantz :
> Hi,
>
> I'd like to request marge access for the piglit and mesa gitlab projects.
> I've been contributing a number of patches here (primarily to zink/gallium),
> and this would be useful in my continued work.
>
> Regards,
> > On Sun, 2020-06-14 at 18:22 +0200, Dieter Nützel wrote:
> > > GREAT work!
> > >
> > > Now, it's working with Konqueror (20.04.1 / Frameworks 5.70.0) -
> > even
> > > if
> > > without 'hovered animation'... ;-)
> > >
> > &
... ;-)
> >
> > Greetings,
> > Dieter
> >
> > Am 14.06.2020 17:25, schrieb Daniel Stone:
> > > Hi,
> > >
> > > On Fri, 29 May 2020 at 10:08, Erik Faye-Lund
> > > wrote:
> > > > In the light of the explanation above, do you stil
AFAIK, anisitropic filtering is almost uselessly underspecified, so
pretty much anything should pass the CTS tests.
But visual quality does affect applications, so we should probably aim
for something reasonable.
On Thu, 2021-01-07 at 19:41 +1000, Dave Airlie wrote:
> On Thu, 7 Jan 2021 at
On Thu, 2020-11-19 at 10:36 -0800, Dylan Baker wrote:
>
> Erik Faye-Lund (3):
> softpipe: correct signature of get_compiler_options
> mesa/main: add missing include in glformats.h
> zink: more accurately track supported blits
>
I just want to point out th
On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
>
> I proposed an MR a while back that changed the only occurrence of the
> UK English spelling "optimisation" fo
On Tue, 2021-03-16 at 10:06 +, Daniel Stone wrote:
> On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand
> wrote:
> > Three comments:
> >
> > 1. +1
> > 2. Khronos has generally standardized on American English in their
> > specs so I guess that provides some sort of prior art or something.
> >
of the forks in the road we follow
trying to clean things up ;)
On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> TLDR; I'm proposing to standardize on US English in our public-facing
> documentation.
>
> I proposed an MR a while back that changed the only occurrence of the
TLDR; I'm proposing to standardize on US English in our public-facing
documentation.
I proposed an MR a while back that changed the only occurrence of the
UK English spelling "optimisation" for the US English spelling
"optimization", which is already used 34 times in the docs. I've done
similar
On Mon, 2021-03-15 at 10:54 -0700, Ian Romanick wrote:
>
> If anyone doesn't feel comfortable speaking out publicly about this,
> please feel free to contact Erik or me privately.
Just thought I'd mention; I've gotten a vote against the proposal
through other channels. Because I haven't gotten
On Fri, 2021-03-26 at 18:22 +0100, Erik Faye-Lund wrote:
> On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote:
> > TLDR; I'm proposing to standardize on US English in our public-
> > facing
> > documentation.
> >
> > I proposed an MR a while back
support in Zink is happening slowly, driven by those who need
it.
--
Erik Faye-Lund
Principal Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United
Kingdom
Registered in England & Wales, no. 5513718
Airlie (1):
glad: regenerate glad files from glad upstream
Eric Engestrom (1):
gitlab-ci: add cmake & autotools builds
Erik Faye-Lund (128):
wglgears: do not include unistd.h on MSVC
wglgears: change window-title
wglgears: make usage and error-handling similar to glxg
OK, so I think enough time has passed. I have heard a few voices in
support, and no voices against, so my plan is to go ahead and merge
this early next week (probably Monday), if I don't hear anyone speak up
soon.
On Wed, 2022-05-04 at 18:38 +0200, Erik Faye-Lund wrote:
> Because we've lan
://gitlab.freedesktop.org/mesa/demos/-/merge_requests/74
If I don't hear any objections in a few weeks, I plan on merging that
change.
On Fri, 2022-05-13 at 11:14 +0200, Erik Faye-Lund wrote:
> OK, so I think enough time has passed. I have heard a few voices in
> support, and no voices against,
Thoughts? Objections?
--
Erik Faye-Lund
Principal Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United
Kingdom
Registered in England & Wales, no. 5513718
ith Erik, we've
> > decided that
> > zink will no longer require any rb/ab/etb tags to be applied to
> > patches in
> > MRs.
> > Following in Turnip's footsteps, any MR that receives sufficient
> > reviewage
> > in gitlab comments can be merged directly wit
Hi, and welcome to the community!
In case you're not already familiar, we have #dri-devel on OFTC, as
mentioned here: https://docs.mesa3d.org/lists.html#irc
This is where most day-to-day communication happens, as well as on our
project on gitlab.fdo.
There's also some technical docs on
is always not-null.
Erik Faye-Lund (97):
meson: disable annoying msvc-warnings
meson: suppress a few msvc warnings
meson: suppress more annoying warnings
wglutil.c: clean up size-wrangling
glinfo_common.c: add int-casts
glinfo_common.c: do not shadow variable i
of this seems to warrant a new major release, so here we are.
There's also a bunch of bugs fixed, many related to the still-quite-new
Meson build system. So this seems like a good time to upgrade!
On Wed, 2023-03-22 at 16:12 +0100, Erik Faye-Lund wrote:
> Alexandros Frantzis (1):
> egl: Add t
On Wed, 2024-06-19 at 10:33 -0400, Mike Blumenkrantz wrote:
> In looking at the gallium tree, I'm wondering if it isn't time for a
> second amber branch to prune some of the drivers that cause pain when
> doing big tree updates:
>
> * nv30
> * r300
> * r600
> * lima
> * virgl
> * tegra
> * ???
>
701 - 747 of 747 matches
Mail list logo
