Hi!
I received a donation on Mesamatrix with this message with it:
> Please fix long-standing bug, not allowing to properly
> recognize my Bonaire XT card with glxinfo tool; for now,
> it reports Bonaire. See my WineHQ bug: #38921
Bonaire cards don't speak to me much, but if someone is welling t
2017-09-14 19:19 GMT-04:00 Bas Nieuwenhuizen :
> Also you can implement 0% of the feature list and still be vulkan 1.0
> compliant ;)
>
Oh... is that so?
Thanks for all your answers, I apparently didn't understand what "being
Vulkan 1.0" meant ;)
So if I understand well, every time there's a new
Le 14 sept. 2017 6:11 PM, "Bas Nieuwenhuizen" a
écrit :
For vulkan, because 1.0 is the initial version, there are no
extensions to implement to get to that version, so having an
extensions list would be nonsensical.
I don't think it is nonsensical, say the nouveau devs starts to work on a
Vulka
at 09:12, Jordan Justen
>> wrote:
>> >> On 2017-09-14 15:36:10, Romain Failliot wrote:
>> >>> Le 14 sept. 2017 6:11 PM, "Bas Nieuwenhuizen" <
>> b...@basnieuwenhuizen.nl> a
>> >>> écrit :
>> >>>
>
Hi!
I'm working on exposing the vulkan information recently added in
features.txt in mesamatrix.net, but there is no extension list under
"Vulkan 1.0 - all DONE: anv, radv"
There is a couple of command lines in the commit message though:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=fe3d2559d
Hi!
I'd like to know which information I should extract from this vk.xml file
so that we can track the progress of ANV and RADV Vulkan drivers.
Thanks!
--
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.f
for a while. I'm not sure whether or not it's needed but it wouldn't hurt.
>
> On Sun, Feb 12, 2017 at 6:48 PM, Romain Failliot <
> romain.faill...@foolstep.com> wrote:
>
>> Hi!
>>
>> I regularly receive questions about having Mesamatrix trackin
Hi!
I regularly receive questions about having Mesamatrix tracking the state of
Vulkan API for ANV and RADV.
I don't think there is a file in mesa repo that state the progression of
Vulkan on each driver. So if you're interested, I could generate a base
file (xml?) extracting the tag from the of
2017-01-23 22:58 GMT-05:00 Timothy Arceri :
> > What is your workaround?
>
> I don't have one. I don't get a chance to actually play games much so
> the card is very unused at this point. The bigger issue I'm having is
> Wayland is unusable with my 4K monitor/RX480 and since F25 boots to
> Wayland
2017-01-23 12:43 GMT-05:00 Romain Failliot :
> What is your workaround? For me it is to get back to 2516x1440, it seems
> to solve the problem, or at least I've never seen a glitch when in this
> resolution.
>
s/2516/2560/
--
Romain
2017-01-23 0:06 GMT-05:00 Timothy Arceri :
> I can confirm a similar problem. I have the same card and also got a 4K
> monitor recently. For me I was running a game in windowed mode (F1 2015
> I think) for a very short amount of time and had some flickering, after
> I closed the game gnome continu
Hi!
2017-01-02 15:10 GMT-05:00 Marek Olšák :
> Does dmesg or Xorg.0.log show anything?
>
I don't know if it's really relevant, but here are my `dmesg` and
`journalctl -b _COMM=gdm-x-session` ('xorg' files) before and after a
session of Dota.
I got two glitches and quit Dota right away. The main
2017-01-03 10:47 GMT-05:00 Rob Clark :
> Hmm, well I guess in future, git-format-patch and attach that to bz..
> but no worries this time, I went ahead and pushed it w/ --author as
> Jan suggested
Thanks!
I'm sorry, I misunderstood, I thought you preferred the patch to be in
the mailing list (but
2017-01-01 16:15 GMT-05:00 Rob Clark :
> well, I was trying to not loose authorship/etc from the patch
> (although tbh I've lost track of who the original author was)..
> http://www.mesa3d.org/devinfo.html#submitting has some suggestions.
I went there, I don't think it's a git problem. I think it'
Hi!
I've recently bought a 4K display and an RX 480, but I've got some
troubles with Dota when using high settings. I've created a thread on
Phoronix forum (because maybe other people have the same problem...):
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-lin
, softpipe, swr)
GL_ARB_gpu_shader5DONE (i965/gen7+)
- 'precise' qualifier DONE
--
2.10.1 (Apple Git-78)
2016-12-31 12:26 GMT-05:00 Romain Failliot :
> I'll try to do the git patch!
>
> I know featu
I'll try to do the git patch!
I know features.txt isn't the official support source and it is more
for the devs to follow on their work, so it's really up to up if you
want to add freedreno in features.txt. I simply don't have a device
for each driver, that's why I'm parsing features.txt in mesama
Hi!
There's a patch by Rob Clark that sits in bugzilla for while now:
https://bugs.freedesktop.org/show_bug.cgi?id=95460
I've just updated it to HEAD. It would be nice to merge it, especially
since there hasn't been much changes in features.txt for a while.
Cheers!
--
Romain "Creak" Failliot
_
to handle this
game with medium video options.
In the meantime I'll play more and try to get more screenshots of these
kind of situations.
Thanks!
2016-09-23 18:21 GMT-04:00 Romain Failliot :
> Thanks Marek, I'll test that!
>
> In the meantime, firstly I fixed an important b
f buffers moved)
> - num-bytes-moved (TTM overhead as the number of bytes moved)
> - num-compilations (compiler invocations)
>
> There are also a bunch of useful things like various VRAM and GTT
> usage stats, GPU-load, etc.
>
> Marek
>
> On Tue, Sep 20, 2016 at 1:25 AM, Ro
2016-09-19 18:40 GMT-04:00 Marek Olšák :
> Do you mean the PC is frozen for 2 minutes or just occasional hiccups
> for 2 minutes?
Occasional hiccups for 2 minutes. The game works well, I wander around
and, from time to time, it freezes for a random duration between 2
seconds and 2 minutes (on aver
2016-09-15 16:27 GMT-04:00 Marek Olšák :
> Update your gcc I guess? Sorry, I don't know much about LLVM build
> requirements. It works with gcc 5.4.0.
I'm using a pretty recent gcc, and the 64-bit compilation works like a
charm, it's only the 32-bit compilation that has trouble.
Anyway, I've been
2016-09-13 13:53 GMT-04:00 Marek Olšák :
> LLVM 32-bit:
>
> mkdir -p build32
> cd build32
> cmake .. -G Ninja -DCMAKE_INSTALL_PREFIX=/usr/llvm/i386-linux-gnu
> -DLLVM_TARGETS_TO_BUILD="X86;AMDGPU" -DLLVM_ENABLE_ASSERTIONS=ON
> -DCMAKE_BUILD_TYPE=RelWithDebInfo
> -DLLVM_BUILD_LLVM_
ers=radeonsi,r600,swrast --with-dri-drivers= \
> --with-egl-platforms=x11,drm --enable-gles1 --enable-gles2
>
> make -j4
> sudo make install
>
> You'll probably want to delete /usr/lib/$dir/*mesa*/*. That's Ubuntu's
> invention that will prevent you from using
2016-09-13 12:41 GMT-04:00 Marek Olšák :
>
> BTW, If you update LLVM to a newer version, you also have to re-build
> Mesa, because the LLVM version used by Mesa is determined while Mesa
> is being built.
>
> Also, the chance to rage-quit while building LLVM+Mesa is pretty high
> if you've never don
Thanks all for your answers!
2016-09-13 5:15 GMT-04:00 Marek Olšák :
> Yeah you need LLVM 3.9 not just for this game, but also for many other
> games to work correctly. It's due to the fact that some games require
> GL 4.3, which is only supported with LLVM 3.9. Some games don't even
> report an e
Hi!
I've just bought myself an RX 480 (because of the open source drivers).
I have Fedora 24 with GNOME 3.20, linux 4.7.2, mesa 12.0.2, llvm 3.8.0.
I tested Alien: Isolation (that I couldn't even launch with my old HD
6870), but there is a texture bug, see by yourself:
https://youtu.be/zTZpWU9srL
Can now compile with -Werror.
Fixed -Wunused-variable, -Wunused-but-set-variable, -Wmaybe-uninitialized
and -Wunused-function.
To prevent warnings for variables only used in asserts, I void them right
after the call to assert().
---
src/compiler/spirv/vtn_variables.c | 1 +
src/galli
Hi Emil!
Actually this patch is less about mesamatrix and more about cleaning
the file (IMO).
By replacing "all drivers" with the actual list of drivers, I've
noticed that it was easier to see which drivers are actually completed
or not.
I also think this will be problematic when new drivers are
At some place, "all drivers" wasn't useful anymore, the "all DONE" list
already had all the currently supported drivers.
Also, the syntax "all drivers" isn't future proof, if a new drivers
comes up (we never know) it will be considered done although by default
it might not be.
Finally, expanding
Thanks!
I'll send a better formatted email when I'll get home.
2016-04-13 3:11 GMT-04:00 Michel Dänzer :
> On 13.04.2016 12:23, Romain Failliot wrote:
> > Forget the previous email, apparently I'm still a git padawan...
> > This, is the new patch rebased on mast
Forget the previous email, apparently I'm still a git padawan...
This, is the new patch rebased on master.
At some place, "all drivers" wasn't useful anymore, the "all DONE" list
already had all the currently supported drivers.
Also, the syntax "all drivers" isn't future proof, if a new drivers
c
New patch based on the latest commits.
At some place, "all drivers" wasn't useful anymore, the "all DONE" list
already had all the currently supported drivers.
Also, the syntax "all drivers" isn't future proof, if a new drivers
comes up (we never know) it will be considered done although by defau
At some place, "all drivers" wasn't useful anymore, the "all DONE" list
already had all the currently supported drivers.
Also, the syntax "all drivers" isn't future proof, if a new drivers
comes up (we never know) it will be considered done although by default
it might not be.
Finally, expanding
> My take is (and always has been) that the point of GL3.txt is to coordinate
> amongst developers, so clarity is paramount.
I completely understand and I'm sure we can do both. The problem here is
simply that we're mixing dev comments and feature statuses.
I'm working on a way to simply edit GL3
Hi!
Two extensions have been recently flagged "DONE (core only)".
>From what we understood [1], it means that it's done in mesa, but drivers
need to implement it.
So, first: is that it?
And, second: if it is, could we change for the syntax made for it: "DONE
()"?
I'll be happy to do the patch as
I sent a v2 of the patches with your proposition Nicolai.
I think I don't have the rights to push patches, so it would be great
if you could do it.
2016-03-15 16:14 GMT-04:00 Romain Failliot :
> This fixes some exceptions I have to deal with in mesamatrix.net.
> The
The "Status" column was misaligned in some GL sections.
This is a lot of diffs, but it's only spaces in the end.
---
docs/GL3.txt | 278 +--
1 file changed, 139 insertions(+), 139 deletions(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 1
This fixes some exceptions I have to deal with in mesamatrix.net.
The extensions GL_ARB_texture_buffer_object had a comment between "DONE"
and the brackets.
And the extension GL_KHR_robustness (in GL 4.5 and GLES 3.1) was using
"90% done" instead of "in progress". The "90% done" is still here
thoug
For older extensions, there is an explanation first and the extension
name in brackets, like that:
Clamping controls (GL_ARB_color_buffer_float)
I inverted that so we have the extension first and then the explanation
in brackets, like that:
GL_ARB_color_buffer_float (Clamping controls)
It
Added a small guide on how to read and edit GL3.txt.
I think this would help as much the devs as the users reading this file.
---
docs/GL3.txt | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index ee7faca..1ed5c1a 100644
--
Hmm... I thought that was what it meant.
I can add a new status like "paused" for instance.
2016-03-14 22:40 GMT-04:00 Ilia Mirkin :
> "In progress" would seem to imply someone is working on it, which, AFAIK, is
> not the case.
>
> On Mar 14, 2016 7:35 PM, "
For older extensions, there is an explanation first and the extension
name in brackets, like that:
Clamping controls (GL_ARB_color_buffer_float)
I inverted that so we have the extension first and then the explanation
in brackets, like that:
GL_ARB_color_buffer_float (Clamping controls)
It
This fixes some exceptions I have to deal with in mesamatrix.net.
The extensions GL_ARB_texture_buffer_object had a comment between "DONE"
and the brackets.
And the extension GL_KHR_robustness (in GL 4.5 and GLES 3.1) was using
"90% done" instead of "in progress". The "90% done" is still here
thoug
The "Status" column was misaligned in some GL sections.
This is a lot of diffs, but it's only spaces in the end.
---
docs/GL3.txt | 278 +--
1 file changed, 139 insertions(+), 139 deletions(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 1
Added a small guide on how to read and edit GL3.txt.
I think this would help as much the devs as the users reading this file.
---
docs/GL3.txt | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index ee7faca..1ed5c1a 100644
--
Hi!
With the recent commits, I'm having some trouble parsing the GL3.txt
text file for mesamatrix.net.
With these set of 4 patches, I'm proposing to rationalize this file a
little bit. Rest assure, the content is still exactly the same.
Cheers!
Romain Failliot (4):
docs: howto t
Thanks for the explanations, I'll resend these patch the right way.
2016-03-14 10:01 GMT-04:00 Nicolai Hähnle :
> Hi Romain,
>
> On 13.03.2016 16:50, Romain Failliot wrote:
>>
>> Hi!
>>
>> With the recent commits, I'm having some trouble parsing
Hi!
With the recent commits, I'm having some trouble parsing the GL3.txt
text file for mesamatrix.net.
With these set of 4 patches, I'm proposing to rationalize a little bit
this file. The content is exactly the same.
(Note: I'm not really used to propose patches, so if this format is
wrong, I'll
2015-10-01 3:33 GMT+02:00 Ian Romanick :
> The two lines that just have () are only supported on i965, nvc0, and
> radeonsi. It's not really that clear.
>
Yep, this part I understood, once you understand it's hierarchical,
everything becomes clearer ;)
Also, a guy on GitHub helped me to underst
Le 29 sept. 2015 7:22 PM, "Ilia Mirkin" a écrit :
> R600/R700 will never support ARB_gpu_shader5. Evergreen and NI
> families (also driven by the r600g driver) will gain support for it in
> due time.
Aaaah I think I understand my misunderstanding: the R600 drivers (in
GL3.txt) gather several driv
29 17:51 GMT+02:00 Albert Freeman :
> On 29 September 2015 at 14:48, Romain Failliot
> wrote:
> > What I don't understand is that all the lines starting with a "-" seems
> to
> > be part of the GL_ARB_gpu_shader5 extension. See the line here:
> > http://cgit.f
shader5 is unsupported by R600, but everything in its sublist is
supported. You see why it is confusing?
Le 29 sept. 2015 8:06 AM, "Marek Olšák" a écrit :
> FMA isn't required really. R600 is mainly missing GS streams, which
> are complete on the mailing somewhere I think.
>
&g
Hi!
I'm diving into the unsupported extensions list and I'm wondering how is it
possible that GL_ARB_gpu_shader5 is unsupported for R600, but some of the
"sub-extensions" like "Dynamically uniform sampler array indices" are
supported nonetheless.
That makes me wonder if "not done" sub-extensions,
mesamatrix has taken). For NVIDIA, I filled
> the list in myself, for radeon, I think GlennK provided it. I asked
> the intel guys a while back, but they didn't seem interested in
> providing the info for their HW (and I didn't push for it).
>
> Hope this helps,
>
> -il
Hi!
First, I wanted to thank you for the incredible work you've done to
achieve OpenGL 4.1. The number of visitors exploded on mesamatrix,
while the average was around 100 visits per day, I had more than 2500
visits just for the day of the news! This simple fact shows how much
this news was expect
Cool! Thanks a lot!
Le 27 nov. 2014 12:05, "Roland Scheidegger" a écrit :
> Sorry for that. Someone (== me) didn't realize he needs to push it :-).
> Done that now.
>
> Roland
>
>
> Am 27.11.2014 um 01:53 schrieb Romain Failliot:
> > Hi!
> >
idegger :
>
> Am 02.11.2014 um 18:35 schrieb Romain Failliot:
>> Hi!
>>
>> Sorry if I'm doing this wrong, first time here. I've tried git
>> send-mail, but I don't have an SMTP server so it wasn't working. Here is
>> the simple commit (and th
> I appreciate the work you've done to make the GL3.txt file much more
> readable.
> To improve it even more I would like to be able to click on the
> extensions names and see the whole text of the extension from the
> registry on opengl.org. I think it would help to understand why
> something isn'
Hi!
Sorry if I'm doing this wrong, first time here. I've tried git send-mail,
but I don't have an SMTP server so it wasn't working. Here is the simple
commit (and the patch attached):
Set llvmpipe and softpipe note only for MSAA.
Right now, in mesamatrix.net, the footnote is set so that it seems
On Fri, Sep 5, 2014 at 4:57 PM, Romain Failliot
> wrote:
> > Hi guys!
> >
> > Little recap on my project. I don't know if've been there recently but
> there
> > has been some nice changes (thanks for the llvmpipe and softpipe cleanup
> by
> > the wa
Hi guys!
Little recap on my project. I don't know if've been there recently but
there has been some nice changes (thanks for the llvmpipe and softpipe
cleanup by the way).
http://creak.foolstep.com/mesamatrix/
I'm wondering if something could be done for the r300 status. I think it
will definitel
gt;
> Am 25.08.2014 07:56, schrieb Kenneth Graunke:
> > On Monday, August 25, 2014 12:05:07 AM Romain Failliot wrote:
> >> Some folks helped me and a lot of detection bug have been fixed!
> >>
> >> I have a question though (for my own culture): what's with
:00 Marek Olšák :
>
> It's not correct. For example, transform feedback shouldn't be listed for
> r300.
>
> Marek
>
> On Sat, Aug 23, 2014 at 11:59 PM, Romain Failliot
> wrote:
> > Hi!
> >
> > I made a PHP script to have a bet
> Cool. You may also be interested in
> http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html which
> takes a more pragmatic approach of just using whatever is reported by
> glxinfo for various hardware for released mesa versions.
>
That is impressive!
> Seems reasonable. You're just talki
Hi!
I made a PHP script to have a better representation of the OpenGL
compliance of Mesa:
http://creak.foolstep.com/mesamatrix/
But I'm not sure about the signification of some lines.
When there is a "DONE", with no parenthesis after, does it means it's done
for all the drivers?
And when there i
For my problem with the nouveau driver burning up my card, I'll take
the simplest solution: get an ATI card (nVidia should have opened up
their specs!).
2011/9/27 Eric Anholt :
> I'd definitely recommend working on a texturing format extension for
> your hardware as a great way to get started in M
2011/10/6 Ian Romanick :
> You will have to *completely* uninstall the NVIDIA closed-source driver in
> order to use the Mesa driver. NVIDIA installs their own kernel module and
> their own libGL, so it is impossible for both to live on the same system.
Well, last time I checked (2 months ago), n
2011/10/6 Heath Feather :
> Try seeing which libraries you're picking up , here my LD_LIBRARY_PATH
> was set to /home/hfeather/work/downloads/Mesa-7.0.1/lib64/
Thanks!
Actually I don't have a lib64 directory, but just lib.
What did you do to build for 64 bits?
BTW I've got F15 64bits.
___
2011/10/6 Julian Adams :
> It's possible that the instructions will only switch you over to your
> locally built version version of Mesa if you are already running a shipped
> Mesa as your driver. It looks like you're running the Nvidia blob. Perhaps
> you need to switch to Mesa/Nouveau first?
Wel
2011/9/27 Romain Failliot :
> I'll get my hand in the code now.
> Be right back as soon as I can run my own mesa code :)
Sorry for the delay, I lost my internet connection for a week...
So I started compiling mesa thanks to the site Benjamin Bellec gave to
me http://forums.fe
Hi Eric,
I tried to email you to have more information about the VS5 task (dead
code elimination), but your email address on your page
(http://dri.freedesktop.org/wiki/EricAnholt) was wrong :/
> I'd definitely recommend working on a texturing format extension for
> your hardware as a great way to
Great !! I'll read this right away!
Thanks!
2011/9/26 Benjamin Bellec :
> Le 26/09/2011 20:25, Romain Failliot a écrit :
>> At first, it would be questions like how to run my own compiled mesa drivers?
>> I should handle getting the code, compiling it and editing it.
>>
Hi Tom, hi Christian,
2011/9/26 Tom Stellard
> Glad you're interested. We can always use more help. I think the
> best way to get started is to find something to work on that is
> interesting to you. So, I have two questions: What hardware do you
> have, and why do you want to contribute to M
Hi all!
I'm an experienced programmer, but I've never touched the mesa code.
I desperately want to help, but for that, I need a "mentor" to teach me the
basics about the project, the good practices and eventually drive me through
the bugs and features.
I'd be glad to begin with a simple, but long
75 matches
Mail list logo
