[Mesa-dev] Mesamatrix donator message

[Romain Failliot]

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 to fix this
bug, I'll be glad to give him/her the 25$ as a bounty ;)

Cheers,
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Vulkan extensions

[Romain Failliot]

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 1.0.yy version of Vulkan,
it means that there's a new set of "extensions" (I don't know the
appropriate erm) added to the previous version 1.0.xx, but it's not
mandatory to implement them to be compatible with the 1.0 API.
If the Vulkan API changes one day, it will be Vulkan 2.0?
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Vulkan extensions

[Romain Failliot]

I could, but for now I'll stick to what features.txt tells me, it's easier
and more doable considering the time I can invest in mesamatrix.

But I think, in the future, users might be interested in knowing which of
the extensions are implemented in each driver. Especially since it doesn't
seem that Vulkan 2.0 will arrive anytime soon, just knowing that anv and
radv are Vulkan 1.0 compliant might not be enough as new (optional)
extensions are announced every two months or so.

2017-09-17 6:37 GMT-04:00 Mike Lothian <m...@fireburn.co.uk>:

> Maybe you could use the hardware feature list and have an extra option of
> unsupported, for the hardware that cannot do that feature and not include
> that in the percentages
>
> On Fri, 15 Sep 2017, 12:19 am Bas Nieuwenhuizen <b...@basnieuwenhuizen.nl>
> wrote:
>
>> On Fri, Sep 15, 2017 at 1:18 AM, Dave Airlie <airl...@gmail.com> wrote:
>> > On 15 September 2017 at 09:12, Jordan Justen <jordan.l.jus...@intel.com>
>> 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 :
>> >>>
>> >>> > 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
>> >>> Vulkan 1.0 driver and they'd like to show their progress in
>> features.txt. I
>> >>> think it would be interesting for them to have the list of extensions
>> to
>> >>> implement to be Vulkan 1.0 compliant, so they could flag which
>> extensions
>> >>> are done, in progress or not started.
>> >>
>> >> That would be fine, except I don't think the 1.0 features are bucketed
>> >> into a set of 'extensions'. Right? I thought 1.0 was the baseline, and
>> >> extensions were built upon that.
>> >>
>> >
>> > I think Romain missed Bas's point. There is no extension list to get to
>> 1.0.
>> > 1.0 is step one. The closest thing is probably the device features list,
>> > and even that you don't expect any device to fill all of it, so what
>> 100% is
>> > differs for every device.
>>
>> Also you can implement 0% of the feature list and still be vulkan 1.0
>> compliant ;)
>>
>> - Bas
>> >
>> > Dave.
>> ___
>> mesa-dev mailing list
>> mesa-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Vulkan extensions

[Romain Failliot]

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
Vulkan 1.0 driver and they'd like to show their progress in features.txt. I
think it would be interesting for them to have the list of extensions to
implement to be Vulkan 1.0 compliant, so they could flag which extensions
are done, in progress or not started.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Vulkan extensions

[Romain Failliot]

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=fe3d2559d941f8f69dbdb369221af69a9974d017

I could generate the list locally, but if a new driver comes in (nvidia for
instance), or if new extensions are added to Vulkan 1.0.xx, this will start
to be hard to maintain.

Is it possible to do the same as for OpenGL and list all the vulkan
extensions directly in features.txt?

Thanks,
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] How about vk_features.txt?

[Romain Failliot]

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.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] How about vk_features.txt?

[Romain Failliot]

I won't have time for the next 2 weeks, but after that I'll propose a file
formatted in a way that is both easy to parse and easy to edit by a human.

2017-02-12 21:58 GMT-05:00 Jason Ekstrand <ja...@jlekstrand.net>:

> I'm certainly not opposed.  I've considered adding such a tracking file
> 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 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 official API (
>> https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/
>> spec/vk.xml#L4117) and maybe the  tag as well, if you want.
>> Then you could simply add the status of each "feature" for RADV and ANV.
>>
>> I'm open to discussion if you think it's a good idea. I don't know
>> exactly what you would need to simplify the task as much as possible. But I
>> think we could use our experience on features.txt to build something both
>> more structured and easier to read (for a human and a machine)
>>
>> Cheers!
>>
>> --
>> Romain "Creak" Failliot
>>
>> ___
>> mesa-dev mailing list
>> mesa-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>
>>
>


-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] How about vk_features.txt?

[Romain Failliot]

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 official API (
https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml#L4117)
and maybe the  tag as well, if you want. Then you could simply
add the status of each "feature" for RADV and ANV.

I'm open to discussion if you think it's a good idea. I don't know exactly
what you would need to simplify the task as much as possible. But I think
we could use our experience on features.txt to build something both more
structured and easier to read (for a human and a machine)

Cheers!

-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

[Romain Failliot]

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 login its causing problems. On the 4.8 Kernel I can at least
> make out the login screen to select x.org and login, on the 4.9 kernel
> it doesn't even boot that far. Again I haven't really had time to look
> into the issue further then knowing it happens.
>

Wayland works for me on Fedora 25 with or without the Copr repo. Pretty
well if it wasn't for Firefox and Steam.

Keep us updated if you find time to try it again.

-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

[Romain Failliot]

2017-01-23 12:43 GMT-05:00 Romain Failliot <romain.faill...@foolstep.com>:

> 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 "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

[Romain Failliot]

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 continued flickering periodically until I
> rebooted.
>
> I'm also running Fedora 25 but was running stock Mesa (13.0) at the
> time and stock llvm (3.8) and 4.8 Kernel.
>
> I haven't bothered trying to reproduce at this stage.
>

Always glad to know you're not alone ;)

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.

-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

[Romain Failliot]

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 diff I see is between
the xorg log, but I don't know if it means anything.

Please see the attached tarball.

Thanks!


log.tar.bz2
Description: BZip2 compressed data
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Patch for freedreno features

[Romain Failliot]

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 I did use git format-patch, so... 1 out of 2 :D
)
Next time I'll do as you said! (and actually I do prefer bz over emails)

-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Patch for freedreno features

[Romain Failliot]

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's the
default setup of sendmail that in't good (maybe it's not configured,
or it only allows internal emails, idk).
And I'm not that good at changing sendmail settings.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [AMD] Screen flickering with 4K and RX 480, would be glad to help debugging

[Romain Failliot]

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-linux/921416-screen-flickering-with-an-rx-480-dota-2-4k-full-settings

The idea is not to have support (I know this mailing list isn't for
that), but to try to find the source of the problem. Maybe it's a
hardware problem (that's on my side), but maybe it's a driver problem.

I'd be glad to give you any logs, outputs, info you ask.
For instance, is there a log somewhere where we can see that the
display actually tried to change it's resolution?

Thanks!

-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Patch for freedreno features

[Romain Failliot]

, swr)
   GL_ARB_draw_indirect  DONE
(i965/gen7+, llvmpipe, 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 <romain.faill...@foolstep.com>:
> 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 mesamatrix.
>
> brb with a patch!
>
> Thanks!
>
> 2016-12-31 12:08 GMT-05:00 Rob Clark <robdcl...@gmail.com>:
>> hey, I don't suppose you could send a git patch?  I can push (although
>> tbh glxinfo is the authoritative source when it comes to which
>> extensions are supported on which generations of adreno)
>>
>> BR,
>> -R



-- 
Romain "Creak" Failliot
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Patch for freedreno features

[Romain Failliot]

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 mesamatrix.

brb with a patch!

Thanks!

2016-12-31 12:08 GMT-05:00 Rob Clark :
> hey, I don't suppose you could send a git patch?  I can push (although
> tbh glxinfo is the authoritative source when it comes to which
> extensions are supported on which generations of adreno)
>
> BR,
> -R
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Patch for freedreno features

[Romain Failliot]

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
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

So I've activated a bunch of stuff:
GALLIUM_HUD="num-compilations,num-bytes-moved,num-evictions;fps,cpu;draw-calls,VRAM-usage"
and had one small freeze of around 2s.
Here is the screenshot (look at the fps drop and the concurrent num bytes
moved and num evictions):

https://framapic.org/GSwpilewir6u/BehgZbtf7axl.png

I'm not sure what these two properties mean... does it speak to you? Do you
think I should show any another property?
BTW I saw that I was pushing my GPU a bit too much as I was around 20 fps,
maybe that's the problem. I thought that the RX 480 was able 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 <romain.faill...@foolstep.com>:

> Thanks Marek, I'll test that!
>
> In the meantime, firstly I fixed an important bug in Mesamatrix so now the
> matrix is more accurate, and I also just found the problem with Dota 2: it
> is not because of the new drivers but because of a change I did in the
> video options, I don't remember having done that but it was apparently in
> borderless window mode which GNOME doesn't handle very well apparently.
>
> Now that this is solved, I'll try to understand what's happening with
> Alien: Isolation.
>
> Thanks!
>
> 2016-09-21 7:36 GMT-04:00 Marek Olšák <mar...@gmail.com>:
>
>> You can use the GALLIUM_HUD environment variable to find out the cause
>> of those hiccups. Just set it before running steam. Type
>> "GALLIUM_HUD=help glxgears" - that should print the available options.
>>
>> From the top of my head, the useful graphs are:
>> - num-evictions (TTM overhead as the number of 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, Romain Failliot
>> <romain.faill...@foolstep.com> wrote:
>> > 2016-09-19 18:40 GMT-04:00 Marek Olšák <mar...@gmail.com>:
>> >> 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 average I'd say it's 30 seconds) and then
>> > the game continues like nothing happened (the sound still works during
>> > the freeze though).
>> >
>> > I played yesterday for instance and I had 10 minutes without any
>> > freeze and then 2 freezes in less than a minute. It's really random,
>> > but it seems to be related to the new places I visit, once I had one
>> > or more freezes in an area, I won't have the freeze a freeze in this
>> > area anymore. That's why I think it could be linked to shader
>> > compilation.
>>
>
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

Thanks Marek, I'll test that!

In the meantime, firstly I fixed an important bug in Mesamatrix so now the
matrix is more accurate, and I also just found the problem with Dota 2: it
is not because of the new drivers but because of a change I did in the
video options, I don't remember having done that but it was apparently in
borderless window mode which GNOME doesn't handle very well apparently.

Now that this is solved, I'll try to understand what's happening with
Alien: Isolation.

Thanks!

2016-09-21 7:36 GMT-04:00 Marek Olšák <mar...@gmail.com>:

> You can use the GALLIUM_HUD environment variable to find out the cause
> of those hiccups. Just set it before running steam. Type
> "GALLIUM_HUD=help glxgears" - that should print the available options.
>
> From the top of my head, the useful graphs are:
> - num-evictions (TTM overhead as the number of 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, Romain Failliot
> <romain.faill...@foolstep.com> wrote:
> > 2016-09-19 18:40 GMT-04:00 Marek Olšák <mar...@gmail.com>:
> >> 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 average I'd say it's 30 seconds) and then
> > the game continues like nothing happened (the sound still works during
> > the freeze though).
> >
> > I played yesterday for instance and I had 10 minutes without any
> > freeze and then 2 freezes in less than a minute. It's really random,
> > but it seems to be related to the new places I visit, once I had one
> > or more freezes in an area, I won't have the freeze a freeze in this
> > area anymore. That's why I think it could be linked to shader
> > compilation.
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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 average I'd say it's 30 seconds) and then
the game continues like nothing happened (the sound still works during
the freeze though).

I played yesterday for instance and I had 10 minutes without any
freeze and then 2 freezes in less than a minute. It's really random,
but it seems to be related to the new places I visit, once I had one
or more freezes in an area, I won't have the freeze a freeze in this
area anymore. That's why I think it could be linked to shader
compilation.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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 advised to use a pre-build rep:
https://copr.fedorainfracloud.org/coprs/mystro256/polaris-gfx/

And it works pretty well now! I do have a bug with the game
(i.e.Alien: Isolation) though: my PC hangs for up to 2 minutes. From
my experience, it seems to be because of the shaders compilation, but
I'm not 100% sure. Is it a known bug? Is it a problem from the game or
from the drivers?

Thanks!
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON \
>   -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer" \
>   -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer" \
>   -DLLVM_BUILD_32_BITS=ON

I have a problem with the 32-bit compilation of llvm.

I get this error:

-- Target triple: x86_64-unknown-linux-gnu
-- Native target architecture is X86
-- Threads enabled.
-- Doxygen disabled.
-- Sphinx disabled.
-- Go bindings disabled.
-- Could NOT find OCaml (missing:  OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- Could NOT find OCaml (missing:  OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- OCaml bindings disabled.
-- Building with -fPIC
-- Building 32 bits executables and libraries.
CMake Error at cmake/modules/HandleLLVMOptions.cmake:469 (message):
  LLVM requires C++11 support but the '-std=c++11' flag isn't supported.
Call Stack (most recent call first):
  CMakeLists.txt:473 (include)


-- Configuring incomplete, errors occurred!

I don't know why my LLVM doesn't handle C++11... Any idea?
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

Thanks a lot! I'll try that tonight!

I have a 64-bit distrib, I don't think so but do I need to compile the 32-bit
version of llvm as well (is it because Steam is using 32-bit libraries?).

2016-09-13 13:53 GMT-04:00 Marek Olšák <mar...@gmail.com>:
> LLVM 64-bit:
>
> mkdir -p build
> cd build
> cmake .. -G Ninja -DCMAKE_INSTALL_PREFIX=/usr/llvm/x86_64-linux-gnu
> -DLLVM_TARGETS_TO_BUILD="X86;AMDGPU" -DLLVM_ENABLE_ASSERTIONS=O
>   -DCMAKE_BUILD_TYPE=RelWithDebInfo
> -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON \
>   -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer" \
>   -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer".
> ninja
> sudo ninja install
>
>
> 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_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON \
>   -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer" \
>   -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g -DNDEBUG
> -fno-omit-frame-pointer" \
>   -DLLVM_BUILD_32_BITS=ON
> ninja
> sudo ninja install
> # then add /usr/llvm/x86_64-linux-gnu and /usr/llvm/i386-linux-gnu to
> ld.conf
>
>
> Mesa configure helper script, it will overwrite the /usr/lib/ files on
> Ubuntu (run as-is for 64-bit, or use "-32" for 32-bit):
>
> if test x$1 = x-32; then
> dir=i386-linux-gnu
> build=i686-linux-gnu
> export CFLAGS="-m32 -O2 -g"
> export CXXFLAGS="$CFLAGS"
> export LDFLAGS="-L/usr/lib/$dir"
> export PKG_CONFIG_PATH="/usr/lib/$dir/pkgconfig"
> else
> dir=x86_64-linux-gnu
> build=$dir
> fi
>
> ./autogen.sh \
>  --build=$build --prefix=/usr --libdir=/usr/lib/$dir
> --with-llvm-prefix=/usr/llvm/$dir \
>  --enable-glx-tls --enable-texture-float --enable-debug --enable-vdpau \
>  --disable-xvmc --disable-va --enable-nine --with-sha1=libnettle \
>  --with-gallium-drivers=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 installed libGL and libEGL.
>
> It's all kind of a mess, but I don't know of a better way.
>
> Marek
>
>
>
> On Tue, Sep 13, 2016 at 7:33 PM, Romain Failliot
> <romain.faill...@foolstep.com> wrote:
>> 2016-09-13 12:41 GMT-04:00 Marek Olšák <mar...@gmail.com>:
>>>
>>> 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 done it before.
>>
>> I see, is there a tutorial somewhere maybe on how to do that?
>> I know how to compile projects, that's not a problem. It's more about the
>> little details to make everything work once it's compiled.
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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 done it before.

I see, is there a tutorial somewhere maybe on how to do that?
I know how to compile projects, that's not a problem. It's more about the
little details to make everything work once it's compiled.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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 error when they don't get GL 4.3, they just run broken.
> (like Alien Isolation)

As I can see, LLVM 3.9 is quite young (September 2nd, 2016), that's
why Fedora 24 still doesn't have it in their stable package (and it's not
even in test in Bodhi). I'll try to compile my own LLVM as Edward advised.

> > Also I tried Dota 2 (which was working on my old HD 6870) and there the
> > textures are perfect, but the top bar is always visible and it creates an
> > offset in the input (notice that the bottom of the screen is cropped):
> > https://framapic.org/6vMPXK5y1tWu/hRcANfUysTdD.png
>
> This is unrelated to the graphics driver. The driver has no control
> over what the window manager does.

I also tend to think it's on the window manager side, but it worked 20
minutes before and the only thing I changed is the GPU (and thus the gpu
drivers), that's why I thought it may have a link with the drivers more than
the WM. But maybe GNOME is using different GL extensions depending
on what the graphics card can do.

-- 
Romain

> >
>
> Marek
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Romain Failliot]

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/zTZpWU9srL4

Also I tried Dota 2 (which was working on my old HD 6870) and there the
textures are perfect, but the top bar is always visible and it creates an
offset in the input (notice that the bottom of the screen is cropped):
https://framapic.org/6vMPXK5y1tWu/hRcANfUysTdD.png

Is there something I could do to help you?

Thanks,
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH] Fix warnings.

[Romain Failliot]

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/gallium/drivers/softpipe/sp_state_shader.c | 2 ++
 src/gallium/drivers/svga/svga_swtnl_draw.c | 1 +
 src/gallium/drivers/svga/svga_tgsi_insn.c  | 1 +
 src/mesa/drivers/dri/i965/brw_eu_emit.c| 1 +
 src/mesa/drivers/dri/i965/gen8_draw_upload.c   | 2 ++
 src/mesa/state_tracker/st_glsl_to_nir.cpp  | 7 ---
 7 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/src/compiler/spirv/vtn_variables.c 
b/src/compiler/spirv/vtn_variables.c
index 812ac62..0e8aa05 100644
--- a/src/compiler/spirv/vtn_variables.c
+++ b/src/compiler/spirv/vtn_variables.c
@@ -938,6 +938,7 @@ var_decoration_cb(struct vtn_builder *b, struct vtn_value 
*val, int member,
  location += VARYING_SLOT_VAR0;
   } else {
  assert(!"Location must be on input or output variable");
+ is_vertex_input = false;
   }
 
   if (nir_var) {
diff --git a/src/gallium/drivers/softpipe/sp_state_shader.c 
b/src/gallium/drivers/softpipe/sp_state_shader.c
index 38673d8..1f0a50c 100644
--- a/src/gallium/drivers/softpipe/sp_state_shader.c
+++ b/src/gallium/drivers/softpipe/sp_state_shader.c
@@ -424,6 +424,8 @@ softpipe_delete_compute_state(struct pipe_context *pipe,
struct sp_compute_shader *state = (struct sp_compute_shader *)cs;
 
assert(softpipe->cs != state);
+   (void) softpipe;
+
tgsi_free_tokens(state->tokens);
FREE(state);
 }
diff --git a/src/gallium/drivers/svga/svga_swtnl_draw.c 
b/src/gallium/drivers/svga/svga_swtnl_draw.c
index 67d1fae..8ed54dc 100644
--- a/src/gallium/drivers/svga/svga_swtnl_draw.c
+++ b/src/gallium/drivers/svga/svga_swtnl_draw.c
@@ -112,6 +112,7 @@ svga_swtnl_draw_vbo(struct svga_context *svga,
 
/* Ensure the draw module didn't touch this */
assert(old_num_vertex_buffers == svga->curr.num_vertex_buffers);
+   (void) old_num_vertex_buffers;
 
/*
 * unmap vertex/index buffers
diff --git a/src/gallium/drivers/svga/svga_tgsi_insn.c 
b/src/gallium/drivers/svga/svga_tgsi_insn.c
index a7fa6a2..0e20013 100644
--- a/src/gallium/drivers/svga/svga_tgsi_insn.c
+++ b/src/gallium/drivers/svga/svga_tgsi_insn.c
@@ -669,6 +669,7 @@ submit_op4(struct svga_shader_emitter *emit,
 * in one slot at least:
 */
assert(type1 == SVGA3DREG_SAMPLER);
+   (void) type1;
 
if (type0 == SVGA3DREG_CONST &&
((type3 == SVGA3DREG_CONST && src0.base.num != src3.base.num) ||
diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c 
b/src/mesa/drivers/dri/i965/brw_eu_emit.c
index 1c2ccb4..6baf0b8 100644
--- a/src/mesa/drivers/dri/i965/brw_eu_emit.c
+++ b/src/mesa/drivers/dri/i965/brw_eu_emit.c
@@ -2252,6 +2252,7 @@ gen7_block_read_scratch(struct brw_codegen *p,
const struct brw_device_info *devinfo = p->devinfo;
brw_inst *insn = next_insn(p, BRW_OPCODE_SEND);
assert(brw_inst_pred_control(devinfo, insn) == BRW_PREDICATE_NONE);
+   (void) devinfo;
 
brw_set_dest(p, insn, retype(dest, BRW_REGISTER_TYPE_UW));
 
diff --git a/src/mesa/drivers/dri/i965/gen8_draw_upload.c 
b/src/mesa/drivers/dri/i965/gen8_draw_upload.c
index 5b3f673..7c592fa 100644
--- a/src/mesa/drivers/dri/i965/gen8_draw_upload.c
+++ b/src/mesa/drivers/dri/i965/gen8_draw_upload.c
@@ -34,6 +34,7 @@
 #include "intel_batchbuffer.h"
 #include "intel_buffer_objects.h"
 
+#ifndef NDEBUG
 static bool
 is_passthru_format(uint32_t format)
 {
@@ -47,6 +48,7 @@ is_passthru_format(uint32_t format)
   return false;
}
 }
+#endif /* !NDEBUG */
 
 static void
 gen8_emit_vertices(struct brw_context *brw)
diff --git a/src/mesa/state_tracker/st_glsl_to_nir.cpp 
b/src/mesa/state_tracker/st_glsl_to_nir.cpp
index 98c075f..4b5f6b4 100644
--- a/src/mesa/state_tracker/st_glsl_to_nir.cpp
+++ b/src/mesa/state_tracker/st_glsl_to_nir.cpp
@@ -168,10 +168,11 @@ st_nir_assign_uniform_locations(struct gl_program *prog,
  continue;
 
   if (uniform->type->is_sampler()) {
- unsigned val;
- bool found = shader_program->UniformHash->get(val, uniform->name);
+ unsigned val = 0;
+ if (!shader_program->UniformHash->get(val, uniform->name)) {
+ assert(0);
+ }
  loc = shaderidx++;
- assert(found);
  /* this ensure that nir_lower_samplers looks at the correct
   * shader_program->UniformStorage[location]:
   */
-- 
2.5.5

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [PATCH v3] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

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 added. I've
heard about OpenSWR recently that is apparently an alternative to
llvmpipe, I guess this driver could be added in this file, doesn't it?
Here, the "all drivers" lines will activate GL extensions for this new
driver whether it's true or not.

I completely understand that this file is mainly meant for the devs.
But from what I've seen, even the devs themselves aren't sure about
the meaning of some lines in this file (I remember previous emails
where I asked the difference between "DONE" and "DONE ()" and not
everyone agreed on the signification ;)). So, to me, structuring this
file is not just for mesamatrix but also for the global understanding
of everyone.

I hope I'll be of more help in the future. Right now it's GL3.txt and
mesamatrix, later it might be drivers optimizations ;)

Cheers!

2016-04-14 10:18 GMT-04:00 Emil Velikov :
> Hi Romain,
>
> While I appreciate the effort put in mesamatrix, I feel that things
> are steering towards the wrong direction here.
>
> That is, the file is (was?) meant to coordinate between developers on
> who's doing what, thus adding/changing policies in order to make it
> easier to be read/parsed by a PHP/other script feels ... strange.
> Afaics the current format does produce reasonable results, right ?
>
> At the end of the day feel free to do as you wish, although I would
> kindly invite you to chip in with the html files in docs. Imho they
> are ones that could use your time/skills ;-)
>
> Regards
> Emil
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH v3] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

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 the drivers list allow to see that some drivers can
be added to the "all DONE" section. It's the case for GL 4.1, 4.2 and
GLES 3.1.
---

Third time is the charm! ;)

I've rebased to the latest master again (there's been a lot of changes
on this file recently!)

 docs/GL3.txt | 102 ++-
 1 file changed, 52 insertions(+), 50 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index dc75cf8..52d8a21 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -44,7 +44,7 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_EXT_texture_shared_exponentDONE ()
   GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
   GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
-  GL_ARB_half_float_pixel   DONE (all drivers)
+  GL_ARB_half_float_pixel   DONE ()
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
@@ -98,7 +98,7 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_ARB_blend_func_extendedDONE ()
   GL_ARB_explicit_attrib_location   DONE (all drivers that 
support GLSL)
   GL_ARB_occlusion_query2   DONE ()
-  GL_ARB_sampler_objectsDONE (all drivers)
+  GL_ARB_sampler_objectsDONE ()
   GL_ARB_shader_bit_encodingDONE ()
   GL_ARB_texture_rgb10_a2ui DONE ()
   GL_ARB_texture_swizzleDONE ()
@@ -136,47 +136,47 @@ GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
   GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
-GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
+GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi, llvmpipe, softpipe
 
-  GL_ARB_ES2_compatibility  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_ES2_compatibility  DONE (i965, nv50)
   GL_ARB_get_program_binary DONE (0 binary formats)
-  GL_ARB_separate_shader_objectsDONE (all drivers)
+  GL_ARB_separate_shader_objectsDONE (i965, nv50)
   GL_ARB_shader_precision   DONE (all drivers that 
support GLSL 4.10)
-  GL_ARB_vertex_attrib_64bitDONE (llvmpipe, 
softpipe)
-  GL_ARB_viewport_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_vertex_attrib_64bitDONE ()
+  GL_ARB_viewport_array DONE (i965, nv50)
 
 
-GL 4.2, GLSL 4.20 -- all DONE: radeonsi
+GL 4.2, GLSL 4.20 --- all DONE: i965, radeonsi
 
-  GL_ARB_texture_compression_bptc   DONE (i965, nvc0, 
r600, radeonsi)
-  GL_ARB_compressed_texture_pixel_storage   DONE (all drivers)
-  GL_ARB_shader_atomic_counters DONE (i965, nvc0, 
radeonsi, softpipe)
-  GL_ARB_texture_storageDONE (all drivers)
-  GL_ARB_transform_feedback_instanced   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_base_instance  DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_shader_image_load_storeDONE (i965, radeonsi, 
softpipe)
+  GL_ARB_texture_compression_bptc   DONE (nvc0, r600)
+  GL_ARB_compressed_texture_pixel_storage   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_atomic_counters DONE (nvc0, softpipe)
+  GL_ARB_texture_storageDONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_transform_feedback_instanced   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_base_instance  DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_image_load_storeDONE (softpipe)
   GL_ARB_conservative_depth DONE (all drivers that 
support GLSL 1.30)
   GL_ARB_shading_language_420pack   DONE (all drivers that 
support GLSL 1.30)
-  GL_ARB_shading_language_packing   DONE (all drivers)
-  GL_ARB_internalformat_query   DONE (i965, nv50, 
nvc0, r600, radeonsi, 

Re: [Mesa-dev] [PATCH v2] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

Thanks!

I'll send a better formatted email when I'll get home.

2016-04-13 3:11 GMT-04:00 Michel Dänzer <mic...@daenzer.net>:

> 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 master.
>
> FYI, the way you added this comment, it'd be included in the Git commit
> log. If you add it after the --- line, it won't be.
>
>
> --
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH v2] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

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
comes up (we never know) it will be considered done although by default
it might not be.

Finally, expanding the drivers list allow to see that some drivers can
be added to the "all DONE" section. It's the case for GL 4.1, 4.2 and
GLES 3.1.
---
 docs/GL3.txt | 102 ++-
 1 file changed, 52 insertions(+), 50 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 39f5122..f7643c3 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -44,7 +44,7 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_EXT_texture_shared_exponentDONE ()
   GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
   GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
-  GL_ARB_half_float_pixel   DONE (all drivers)
+  GL_ARB_half_float_pixel   DONE ()
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
@@ -98,7 +98,7 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_ARB_blend_func_extendedDONE ()
   GL_ARB_explicit_attrib_location   DONE (all drivers that 
support GLSL)
   GL_ARB_occlusion_query2   DONE ()
-  GL_ARB_sampler_objectsDONE (all drivers)
+  GL_ARB_sampler_objectsDONE ()
   GL_ARB_shader_bit_encodingDONE ()
   GL_ARB_texture_rgb10_a2ui DONE ()
   GL_ARB_texture_swizzleDONE ()
@@ -136,47 +136,47 @@ GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
   GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
-GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
+GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi, llvmpipe, softpipe
 
-  GL_ARB_ES2_compatibility  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_ES2_compatibility  DONE (i965, nv50)
   GL_ARB_get_program_binary DONE (0 binary formats)
-  GL_ARB_separate_shader_objectsDONE (all drivers)
+  GL_ARB_separate_shader_objectsDONE (i965, nv50)
   GL_ARB_shader_precision   DONE (all drivers that 
support GLSL 4.10)
-  GL_ARB_vertex_attrib_64bitDONE (llvmpipe, 
softpipe)
-  GL_ARB_viewport_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_vertex_attrib_64bitDONE ()
+  GL_ARB_viewport_array DONE (i965, nv50)
 
 
-GL 4.2, GLSL 4.20 -- all DONE: radeonsi
+GL 4.2, GLSL 4.20 --- all DONE: i965, radeonsi
 
-  GL_ARB_texture_compression_bptc   DONE (i965, nvc0, 
r600, radeonsi)
-  GL_ARB_compressed_texture_pixel_storage   DONE (all drivers)
-  GL_ARB_shader_atomic_counters DONE (i965, nvc0, 
radeonsi, softpipe)
-  GL_ARB_texture_storageDONE (all drivers)
-  GL_ARB_transform_feedback_instanced   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_base_instance  DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_shader_image_load_storeDONE (i965, radeonsi, 
softpipe)
+  GL_ARB_texture_compression_bptc   DONE (nvc0, r600)
+  GL_ARB_compressed_texture_pixel_storage   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_atomic_counters DONE (nvc0, softpipe)
+  GL_ARB_texture_storageDONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_transform_feedback_instanced   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_base_instance  DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_image_load_storeDONE (softpipe)
   GL_ARB_conservative_depth DONE (all drivers that 
support GLSL 1.30)
   GL_ARB_shading_language_420pack   DONE (all drivers that 
support GLSL 1.30)
-  GL_ARB_shading_language_packing   DONE (all drivers)
-  GL_ARB_internalformat_query   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  

[Mesa-dev] [PATCH] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

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 default
it might not be.

Finally, expanding the drivers list allow to see that some drivers can
be added to the "all DONE" section. It's the case for GL 4.1, 4.2 and
GLES 3.1.
---
 docs/GL3.txt | 96 ++--
 1 file changed, 48 insertions(+), 48 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 7535dc5..f9af21e 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -44,7 +44,7 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_EXT_texture_shared_exponentDONE ()
   GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
   GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
-  GL_ARB_half_float_pixel   DONE (all drivers)
+  GL_ARB_half_float_pixel   DONE ()
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
@@ -98,7 +98,7 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_ARB_blend_func_extendedDONE ()
   GL_ARB_explicit_attrib_location   DONE (all drivers that 
support GLSL)
   GL_ARB_occlusion_query2   DONE ()
-  GL_ARB_sampler_objectsDONE (all drivers)
+  GL_ARB_sampler_objectsDONE ()
   GL_ARB_shader_bit_encodingDONE ()
   GL_ARB_texture_rgb10_a2ui DONE ()
   GL_ARB_texture_swizzleDONE ()
@@ -136,47 +136,47 @@ GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
   GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
-GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
+GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi, llvmpipe, softpipe
 
-  GL_ARB_ES2_compatibility  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_ES2_compatibility  DONE (i965, nv50)
   GL_ARB_get_program_binary DONE (0 binary formats)
-  GL_ARB_separate_shader_objectsDONE (all drivers)
+  GL_ARB_separate_shader_objectsDONE (i965, nv50)
   GL_ARB_shader_precision   DONE (all drivers that 
support GLSL 4.10)
-  GL_ARB_vertex_attrib_64bitDONE (llvmpipe, 
softpipe)
-  GL_ARB_viewport_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_vertex_attrib_64bitDONE ()
+  GL_ARB_viewport_array DONE (i965, nv50)
 
 
-GL 4.2, GLSL 4.20:
+GL 4.2, GLSL 4.20: --- all DONE: i965, radeonsi
 
-  GL_ARB_texture_compression_bptc   DONE (i965, nvc0, 
r600, radeonsi)
-  GL_ARB_compressed_texture_pixel_storage   DONE (all drivers)
-  GL_ARB_shader_atomic_counters DONE (i965, nvc0, 
radeonsi, softpipe)
-  GL_ARB_texture_storageDONE (all drivers)
-  GL_ARB_transform_feedback_instanced   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_base_instance  DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_shader_image_load_storeDONE (i965, radeonsi, 
softpipe)
+  GL_ARB_texture_compression_bptc   DONE (nvc0, r600)
+  GL_ARB_compressed_texture_pixel_storage   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_atomic_counters DONE (nvc0, softpipe)
+  GL_ARB_texture_storageDONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_transform_feedback_instanced   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_base_instance  DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_image_load_storeDONE (softpipe)
   GL_ARB_conservative_depth DONE (all drivers that 
support GLSL 1.30)
   GL_ARB_shading_language_420pack   DONE (all drivers that 
support GLSL 1.30)
-  GL_ARB_shading_language_packing   DONE (all drivers)
-  GL_ARB_internalformat_query   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_map_buffer_alignment   DONE (all drivers)
+  

[Mesa-dev] [PATCH] docs: expand "all drivers" to the list of drivers.

[Romain Failliot]

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 the drivers list allow to see that some drivers can
be added to the "all DONE" section. It's the case for GL 4.1, 4.2 and
GLES 3.1.
---
 docs/GL3.txt | 96 ++--
 1 file changed, 48 insertions(+), 48 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 7535dc5..f9af21e 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -44,7 +44,7 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_EXT_texture_shared_exponentDONE ()
   GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
   GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
-  GL_ARB_half_float_pixel   DONE (all drivers)
+  GL_ARB_half_float_pixel   DONE ()
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
@@ -98,7 +98,7 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   GL_ARB_blend_func_extendedDONE ()
   GL_ARB_explicit_attrib_location   DONE (all drivers that 
support GLSL)
   GL_ARB_occlusion_query2   DONE ()
-  GL_ARB_sampler_objectsDONE (all drivers)
+  GL_ARB_sampler_objectsDONE ()
   GL_ARB_shader_bit_encodingDONE ()
   GL_ARB_texture_rgb10_a2ui DONE ()
   GL_ARB_texture_swizzleDONE ()
@@ -136,47 +136,47 @@ GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
   GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
-GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
+GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi, llvmpipe, softpipe
 
-  GL_ARB_ES2_compatibility  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_ES2_compatibility  DONE (i965, nv50)
   GL_ARB_get_program_binary DONE (0 binary formats)
-  GL_ARB_separate_shader_objectsDONE (all drivers)
+  GL_ARB_separate_shader_objectsDONE (i965, nv50)
   GL_ARB_shader_precision   DONE (all drivers that 
support GLSL 4.10)
-  GL_ARB_vertex_attrib_64bitDONE (llvmpipe, 
softpipe)
-  GL_ARB_viewport_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_vertex_attrib_64bitDONE ()
+  GL_ARB_viewport_array DONE (i965, nv50)
 
 
-GL 4.2, GLSL 4.20:
+GL 4.2, GLSL 4.20: --- all DONE: i965, radeonsi
 
-  GL_ARB_texture_compression_bptc   DONE (i965, nvc0, 
r600, radeonsi)
-  GL_ARB_compressed_texture_pixel_storage   DONE (all drivers)
-  GL_ARB_shader_atomic_counters DONE (i965, nvc0, 
radeonsi, softpipe)
-  GL_ARB_texture_storageDONE (all drivers)
-  GL_ARB_transform_feedback_instanced   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_base_instance  DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_shader_image_load_storeDONE (i965, radeonsi, 
softpipe)
+  GL_ARB_texture_compression_bptc   DONE (nvc0, r600)
+  GL_ARB_compressed_texture_pixel_storage   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_atomic_counters DONE (nvc0, softpipe)
+  GL_ARB_texture_storageDONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_transform_feedback_instanced   DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_base_instance  DONE (nv50, nvc0, 
r600, llvmpipe, softpipe)
+  GL_ARB_shader_image_load_storeDONE (softpipe)
   GL_ARB_conservative_depth DONE (all drivers that 
support GLSL 1.30)
   GL_ARB_shading_language_420pack   DONE (all drivers that 
support GLSL 1.30)
-  GL_ARB_shading_language_packing   DONE (all drivers)
-  GL_ARB_internalformat_query   DONE (i965, nv50, 
nvc0, r600, radeonsi, llvmpipe, softpipe)
-  GL_ARB_map_buffer_alignment   DONE (all drivers)
+  GL_ARB_shading_language_packing   

Re: [Mesa-dev] Meaning of "DONE (core only)"

[Romain Failliot]

> 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.txt but also be able to add comments
that are easily recognizable. Something like "# dev comment" at the end of the
lines.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Meaning of "DONE (core only)"

[Romain Failliot]

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 soon as the we're ok on this.

Thanks!

[1]
https://github.com/MightyCreak/mesamatrix/issues/95#issuecomment-204027508

-- 
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [PATCH v2 3/4] docs: Renormalize some extensions.

[Romain Failliot]

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 <romain.faill...@foolstep.com>:
> 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
> though, but as an extension comment.
> ---
>  docs/GL3.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/docs/GL3.txt b/docs/GL3.txt
> index 17522d5..49ba7d7 100644
> --- a/docs/GL3.txt
> +++ b/docs/GL3.txt
> @@ -72,7 +72,7 @@ GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600, 
> radeonsi, llvmpipe, soft
>Buffer copying (GL_ARB_copy_buffer)   DONE ()
>Primitive restart (GL_NV_primitive_restart)   DONE ()
>16 vertex texture image units DONE ()
> -  Texture buffer objs (GL_ARB_texture_buffer_object)DONE for OpenGL 3.1 
> contexts ()
> +  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL 3.1 
> contexts)
>Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
>Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
>Signed normalized textures (GL_EXT_texture_snorm) DONE ()
> @@ -219,7 +219,7 @@ GL 4.5, GLSL 4.50:
>GL_ARB_texture_barrierDONE (i965, nv50, 
> nvc0, r600, radeonsi)
>GL_KHR_context_flush_control  DONE (all - but 
> needs GLX/EGL extension to be useful)
>GL_KHR_robust_buffer_access_behavior  not started
> -  GL_KHR_robustness 90% done (the ARB 
> variant)
> +  GL_KHR_robustness not started (90% 
> done with the ARB variant)
>GL_EXT_shader_integer_mix DONE (all drivers 
> that support GLSL)
>
>  These are the extensions cherry-picked to make GLES 3.1
> @@ -254,7 +254,7 @@ GLES3.2, GLSL ES 3.2
>GL_EXT_color_buffer_float DONE (all drivers)
>GL_KHR_blend_equation_advancednot started
>GL_KHR_debug  DONE (all drivers)
> -  GL_KHR_robustness 90% done (the ARB 
> variant)
> +  GL_KHR_robustness not started (90% 
> done with the ARB variant)
>GL_KHR_texture_compression_astc_ldr   DONE (i965/gen9+)
>GL_OES_copy_image not started (based 
> on GL_ARB_copy_image, which is done for some drivers)
>GL_OES_draw_buffers_indexed   not started
> --
> 2.5.0
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH v2 2/4] docs: Realign the "Status" column.

[Romain Failliot]

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 1ed5c1a..17522d5 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -30,8 +30,8 @@ version with all deprecated features is 3.0. Some of the 
later GL features
 are exposed in the 3.0 context as extensions.
 
 
-Feature   Status
-- 
+Feature Status
+--- 

 
 GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
@@ -109,170 +109,170 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
 
 GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
 
-  GL_ARB_draw_buffers_blendDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_draw_indirect DONE (i965, llvmpipe, 
softpipe)
-  GL_ARB_gpu_shader5   DONE (i965)
-  - 'precise' qualifierDONE
-  - Dynamically uniform sampler array indices  DONE (softpipe)
-  - Dynamically uniform UBO array indices  DONE ()
-  - Implicit signed -> unsigned conversionsDONE
-  - Fused multiply-add DONE ()
-  - Packing/bitfield/conversion functions  DONE (softpipe)
-  - Enhanced textureGather DONE (softpipe)
-  - Geometry shader instancing DONE (llvmpipe, 
softpipe)
-  - Geometry shader multiple streams   DONE ()
-  - Enhanced per-sample shadingDONE ()
-  - Interpolation functionsDONE ()
-  - New overload resolution rules  DONE
-  GL_ARB_gpu_shader_fp64   DONE (llvmpipe, 
softpipe)
-  GL_ARB_sample_shadingDONE (i965, nv50)
-  GL_ARB_shader_subroutine DONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_tessellation_shader   DONE (i965)
-  GL_ARB_texture_buffer_object_rgb32   DONE (i965, llvmpipe, 
softpipe)
-  GL_ARB_texture_cube_map_arrayDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_texture_gatherDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_texture_query_lod DONE (i965, nv50, 
softpipe)
-  GL_ARB_transform_feedback2   DONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_transform_feedback3   DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_draw_buffers_blend DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_draw_indirect  DONE (i965, llvmpipe, 
softpipe)
+  GL_ARB_gpu_shader5DONE (i965)
+  - 'precise' qualifier DONE
+  - Dynamically uniform sampler array indices   DONE (softpipe)
+  - Dynamically uniform UBO array indices   DONE ()
+  - Implicit signed -> unsigned conversions DONE
+  - Fused multiply-add  DONE ()
+  - Packing/bitfield/conversion functions   DONE (softpipe)
+  - Enhanced textureGather  DONE (softpipe)
+  - Geometry shader instancing  DONE (llvmpipe, 
softpipe)
+  - Geometry shader multiple streamsDONE ()
+  - Enhanced per-sample shading DONE ()
+  - Interpolation functions DONE ()
+  - New overload resolution rules   DONE
+  GL_ARB_gpu_shader_fp64DONE (llvmpipe, 
softpipe)
+  GL_ARB_sample_shading DONE (i965, nv50)
+  GL_ARB_shader_subroutine  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_tessellation_shaderDONE (i965)
+  GL_ARB_texture_buffer_object_rgb32DONE (i965, llvmpipe, 
softpipe)
+  GL_ARB_texture_cube_map_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_texture_gather DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_texture_query_lod  DONE (i965, nv50, 
softpipe)
+  GL_ARB_transform_feedback2DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
 GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
 
-  

[Mesa-dev] [PATCH v2 3/4] docs: Renormalize some extensions.

[Romain Failliot]

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
though, but as an extension comment.
---
 docs/GL3.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 17522d5..49ba7d7 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -72,7 +72,7 @@ GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   Buffer copying (GL_ARB_copy_buffer)   DONE ()
   Primitive restart (GL_NV_primitive_restart)   DONE ()
   16 vertex texture image units DONE ()
-  Texture buffer objs (GL_ARB_texture_buffer_object)DONE for OpenGL 3.1 
contexts ()
+  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL 3.1 
contexts)
   Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
   Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
   Signed normalized textures (GL_EXT_texture_snorm) DONE ()
@@ -219,7 +219,7 @@ GL 4.5, GLSL 4.50:
   GL_ARB_texture_barrierDONE (i965, nv50, 
nvc0, r600, radeonsi)
   GL_KHR_context_flush_control  DONE (all - but needs 
GLX/EGL extension to be useful)
   GL_KHR_robust_buffer_access_behavior  not started
-  GL_KHR_robustness 90% done (the ARB 
variant)
+  GL_KHR_robustness not started (90% done 
with the ARB variant)
   GL_EXT_shader_integer_mix DONE (all drivers that 
support GLSL)
 
 These are the extensions cherry-picked to make GLES 3.1
@@ -254,7 +254,7 @@ GLES3.2, GLSL ES 3.2
   GL_EXT_color_buffer_float DONE (all drivers)
   GL_KHR_blend_equation_advancednot started
   GL_KHR_debug  DONE (all drivers)
-  GL_KHR_robustness 90% done (the ARB 
variant)
+  GL_KHR_robustness not started (90% done 
with the ARB variant)
   GL_KHR_texture_compression_astc_ldr   DONE (i965/gen9+)
   GL_OES_copy_image not started (based on 
GL_ARB_copy_image, which is done for some drivers)
   GL_OES_draw_buffers_indexed   not started
-- 
2.5.0

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH v2 4/4] docs: Renormalize older extensions.

[Romain Failliot]

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 will help me later to parse the few extensions that use this syntax:
all drivers that support 
---
 docs/GL3.txt | 52 ++--
 1 file changed, 26 insertions(+), 26 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 49ba7d7..3058996 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -36,24 +36,24 @@ Feature 
Status
 GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   glBindFragDataLocation, glGetFragDataLocation DONE
-  Conditional rendering (GL_NV_conditional_render)  DONE ()
-  Map buffer subranges (GL_ARB_map_buffer_range)DONE ()
-  Clamping controls (GL_ARB_color_buffer_float) DONE ()
-  Float textures, renderbuffers (GL_ARB_texture_float)  DONE ()
+  GL_NV_conditional_render (Conditional rendering)  DONE ()
+  GL_ARB_map_buffer_range (Map buffer subranges)DONE ()
+  GL_ARB_color_buffer_float (Clamping controls) DONE ()
+  GL_ARB_texture_float (Float textures, renderbuffers)  DONE ()
   GL_EXT_packed_float   DONE ()
   GL_EXT_texture_shared_exponentDONE ()
-  Float depth buffers (GL_ARB_depth_buffer_float)   DONE ()
-  Framebuffer objects (GL_ARB_framebuffer_object)   DONE ()
+  GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
+  GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
   GL_ARB_half_float_pixel   DONE (all drivers)
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
-  Per-buffer blend and masks (GL_EXT_draw_buffers2) DONE ()
+  GL_EXT_draw_buffers2 (Per-buffer blend and masks) DONE ()
   GL_EXT_texture_compression_rgtc   DONE ()
   GL_ARB_texture_rg DONE ()
-  Transform feedback (GL_EXT_transform_feedback)DONE ()
-  Vertex array objects (GL_ARB_vertex_array_object) DONE ()
-  sRGB framebuffer format (GL_EXT_framebuffer_sRGB) DONE ()
+  GL_EXT_transform_feedback (Transform feedback)DONE ()
+  GL_ARB_vertex_array_object (Vertex array objects) DONE ()
+  GL_EXT_framebuffer_sRGB (sRGB framebuffer format) DONE ()
   glClearBuffer commandsDONE
   glGetStringi command  DONE
   glTexParameterI, glGetTexParameterI commands  DONE
@@ -68,28 +68,28 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
 GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   Forward compatible context support/deprecations   DONE ()
-  Instanced drawing (GL_ARB_draw_instanced) DONE ()
-  Buffer copying (GL_ARB_copy_buffer)   DONE ()
-  Primitive restart (GL_NV_primitive_restart)   DONE ()
+  GL_ARB_draw_instanced (Instanced drawing) DONE ()
+  GL_ARB_copy_buffer (Buffer copying)   DONE ()
+  GL_NV_primitive_restart (Primitive restart)   DONE ()
   16 vertex texture image units DONE ()
-  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL 3.1 
contexts)
-  Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
-  Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
-  Signed normalized textures (GL_EXT_texture_snorm) DONE ()
+  GL_ARB_texture_buffer_object (Texture buffer objs)DONE (for OpenGL 3.1 
contexts)
+  GL_ARB_texture_rectangle (Rectangular textures)   DONE ()
+  GL_ARB_uniform_buffer_object (Uniform buffer objs)DONE ()
+  GL_EXT_texture_snorm (Signed normalized textures) DONE ()
 
 
 GL 3.2, GLSL 1.50 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   Core/compatibility profiles   DONE
   Geometry shaders  DONE ()
-  BGRA vertex order (GL_ARB_vertex_array_bgra)  DONE ()
-  Base vertex offset(GL_ARB_draw_elements_base_vertex)  DONE ()
-  Frag shader coord (GL_ARB_fragment_coord_conventions) DONE ()
-  Provoking vertex (GL_ARB_provoking_vertex)DONE ()
-  Seamless cubemaps (GL_ARB_seamless_cube_map)  DONE ()
-  Multisample textures (GL_ARB_texture_multisample) DONE ()
-  Frag depth clamp (GL_ARB_depth_clamp) DONE ()
-  Fence objects (GL_ARB_sync)   DONE ()
+  GL_ARB_vertex_array_bgra (BGRA vertex order)  DONE ()
+  

[Mesa-dev] [PATCH v2 1/4] docs: howto to read and edit GL3.txt

[Romain Failliot]

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
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -1,13 +1,28 @@
+# Status of OpenGL extensions in Mesa
 
-Status of OpenGL 3.x features in Mesa
+Here's how to read this file:
 
+all DONE: , ...
+All the extensions are done for the given list of drivers.
 
-Note: when an item is marked as "DONE" it means all the core Mesa
-infrastructure is complete but it may be the case that few (if any) drivers
-implement the features.
+DONE
+The extension is done for Mesa and no implementation is necessary on the
+driver-side.
 
+DONE ()
+The extension is done for Mesa and all the drivers in the "all DONE" list.
 
-OpenGL Core and Compatibility context support
+DONE (, ...)
+The extension is done for Mesa, all the drivers in the "all DONE" list, and
+all the drivers in the brackets.
+
+in progress
+The extension is started but not finished yet.
+
+not started
+The extension isn't started yet.
+
+# OpenGL Core and Compatibility context support
 
 OpenGL 3.1 and later versions are only supported with the Core profile.
 There are no plans to support GL_ARB_compatibility. The last supported OpenGL
-- 
2.5.0

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [PATCH 3/4] docs: Renormalize some extensions.

[Romain Failliot]

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 <imir...@alum.mit.edu>:
> "In progress" would seem to imply someone is working on it, which, AFAIK, is
> not the case.
>
> On Mar 14, 2016 7:35 PM, "Romain Failliot" <romain.faill...@foolstep.com>
> wrote:
>>
>> 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
>> though, but as an extension comment.
>> ---
>>  docs/GL3.txt | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/docs/GL3.txt b/docs/GL3.txt
>> index 17522d5..321a90f 100644
>> --- a/docs/GL3.txt
>> +++ b/docs/GL3.txt
>> @@ -72,7 +72,7 @@ GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600,
>> radeonsi, llvmpipe, soft
>>Buffer copying (GL_ARB_copy_buffer)   DONE ()
>>Primitive restart (GL_NV_primitive_restart)   DONE ()
>>16 vertex texture image units DONE ()
>> -  Texture buffer objs (GL_ARB_texture_buffer_object)DONE for OpenGL
>> 3.1 contexts ()
>> +  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL
>> 3.1 contexts)
>>Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
>>Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
>>Signed normalized textures (GL_EXT_texture_snorm) DONE ()
>> @@ -219,7 +219,7 @@ GL 4.5, GLSL 4.50:
>>GL_ARB_texture_barrierDONE (i965, nv50,
>> nvc0, r600, radeonsi)
>>GL_KHR_context_flush_control  DONE (all - but
>> needs GLX/EGL extension to be useful)
>>GL_KHR_robust_buffer_access_behavior  not started
>> -  GL_KHR_robustness 90% done (the ARB
>> variant)
>> +  GL_KHR_robustness in progress (90%
>> done - the ARB variant)
>>GL_EXT_shader_integer_mix DONE (all drivers
>> that support GLSL)
>>
>>  These are the extensions cherry-picked to make GLES 3.1
>> @@ -254,7 +254,7 @@ GLES3.2, GLSL ES 3.2
>>GL_EXT_color_buffer_float DONE (all
>> drivers)
>>GL_KHR_blend_equation_advancednot started
>>GL_KHR_debug  DONE (all
>> drivers)
>> -  GL_KHR_robustness 90% done (the ARB
>> variant)
>> +  GL_KHR_robustness in progress (90%
>> done - the ARB variant)
>>GL_KHR_texture_compression_astc_ldr   DONE (i965/gen9+)
>>GL_OES_copy_image not started
>> (based on GL_ARB_copy_image, which is done for some drivers)
>>GL_OES_draw_buffers_indexed   not started
>> --
>> 2.5.0
>>
>> ___
>> mesa-dev mailing list
>> mesa-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH 4/4] docs: Renormalize older extensions.

[Romain Failliot]

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 will help me later to parse the few extensions that use this syntax:
all drivers that support 
---
 docs/GL3.txt | 52 ++--
 1 file changed, 26 insertions(+), 26 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 321a90f..0f5a1f6 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -36,24 +36,24 @@ Feature 
Status
 GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   glBindFragDataLocation, glGetFragDataLocation DONE
-  Conditional rendering (GL_NV_conditional_render)  DONE ()
-  Map buffer subranges (GL_ARB_map_buffer_range)DONE ()
-  Clamping controls (GL_ARB_color_buffer_float) DONE ()
-  Float textures, renderbuffers (GL_ARB_texture_float)  DONE ()
+  GL_NV_conditional_render (Conditional rendering)  DONE ()
+  GL_ARB_map_buffer_range (Map buffer subranges)DONE ()
+  GL_ARB_color_buffer_float (Clamping controls) DONE ()
+  GL_ARB_texture_float (Float textures, renderbuffers)  DONE ()
   GL_EXT_packed_float   DONE ()
   GL_EXT_texture_shared_exponentDONE ()
-  Float depth buffers (GL_ARB_depth_buffer_float)   DONE ()
-  Framebuffer objects (GL_ARB_framebuffer_object)   DONE ()
+  GL_ARB_depth_buffer_float (Float depth buffers)   DONE ()
+  GL_ARB_framebuffer_object (Framebuffer objects)   DONE ()
   GL_ARB_half_float_pixel   DONE (all drivers)
   GL_ARB_half_float_vertex  DONE ()
   GL_EXT_texture_integerDONE ()
   GL_EXT_texture_array  DONE ()
-  Per-buffer blend and masks (GL_EXT_draw_buffers2) DONE ()
+  GL_EXT_draw_buffers2 (Per-buffer blend and masks) DONE ()
   GL_EXT_texture_compression_rgtc   DONE ()
   GL_ARB_texture_rg DONE ()
-  Transform feedback (GL_EXT_transform_feedback)DONE ()
-  Vertex array objects (GL_ARB_vertex_array_object) DONE ()
-  sRGB framebuffer format (GL_EXT_framebuffer_sRGB) DONE ()
+  GL_EXT_transform_feedback (Transform feedback)DONE ()
+  GL_ARB_vertex_array_object (Vertex array objects) DONE ()
+  GL_EXT_framebuffer_sRGB (sRGB framebuffer format) DONE ()
   glClearBuffer commandsDONE
   glGetStringi command  DONE
   glTexParameterI, glGetTexParameterI commands  DONE
@@ -68,28 +68,28 @@ GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
 GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   Forward compatible context support/deprecations   DONE ()
-  Instanced drawing (GL_ARB_draw_instanced) DONE ()
-  Buffer copying (GL_ARB_copy_buffer)   DONE ()
-  Primitive restart (GL_NV_primitive_restart)   DONE ()
+  GL_ARB_draw_instanced (Instanced drawing) DONE ()
+  GL_ARB_copy_buffer (Buffer copying)   DONE ()
+  GL_NV_primitive_restart (Primitive restart)   DONE ()
   16 vertex texture image units DONE ()
-  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL 3.1 
contexts)
-  Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
-  Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
-  Signed normalized textures (GL_EXT_texture_snorm) DONE ()
+  GL_ARB_texture_buffer_object (Texture buffer objs)DONE (for OpenGL 3.1 
contexts)
+  GL_ARB_texture_rectangle (Rectangular textures)   DONE ()
+  GL_ARB_uniform_buffer_object (Uniform buffer objs)DONE ()
+  GL_EXT_texture_snorm (Signed normalized textures) DONE ()
 
 
 GL 3.2, GLSL 1.50 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
   Core/compatibility profiles   DONE
   Geometry shaders  DONE ()
-  BGRA vertex order (GL_ARB_vertex_array_bgra)  DONE ()
-  Base vertex offset(GL_ARB_draw_elements_base_vertex)  DONE ()
-  Frag shader coord (GL_ARB_fragment_coord_conventions) DONE ()
-  Provoking vertex (GL_ARB_provoking_vertex)DONE ()
-  Seamless cubemaps (GL_ARB_seamless_cube_map)  DONE ()
-  Multisample textures (GL_ARB_texture_multisample) DONE ()
-  Frag depth clamp (GL_ARB_depth_clamp) DONE ()
-  Fence objects (GL_ARB_sync)   DONE ()
+  GL_ARB_vertex_array_bgra (BGRA vertex order)  DONE ()
+  

[Mesa-dev] [PATCH 3/4] docs: Renormalize some extensions.

[Romain Failliot]

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
though, but as an extension comment.
---
 docs/GL3.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/GL3.txt b/docs/GL3.txt
index 17522d5..321a90f 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -72,7 +72,7 @@ GL 3.1, GLSL 1.40 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
   Buffer copying (GL_ARB_copy_buffer)   DONE ()
   Primitive restart (GL_NV_primitive_restart)   DONE ()
   16 vertex texture image units DONE ()
-  Texture buffer objs (GL_ARB_texture_buffer_object)DONE for OpenGL 3.1 
contexts ()
+  Texture buffer objs (GL_ARB_texture_buffer_object)DONE (for OpenGL 3.1 
contexts)
   Rectangular textures (GL_ARB_texture_rectangle)   DONE ()
   Uniform buffer objs (GL_ARB_uniform_buffer_object)DONE ()
   Signed normalized textures (GL_EXT_texture_snorm) DONE ()
@@ -219,7 +219,7 @@ GL 4.5, GLSL 4.50:
   GL_ARB_texture_barrierDONE (i965, nv50, 
nvc0, r600, radeonsi)
   GL_KHR_context_flush_control  DONE (all - but needs 
GLX/EGL extension to be useful)
   GL_KHR_robust_buffer_access_behavior  not started
-  GL_KHR_robustness 90% done (the ARB 
variant)
+  GL_KHR_robustness in progress (90% done 
- the ARB variant)
   GL_EXT_shader_integer_mix DONE (all drivers that 
support GLSL)
 
 These are the extensions cherry-picked to make GLES 3.1
@@ -254,7 +254,7 @@ GLES3.2, GLSL ES 3.2
   GL_EXT_color_buffer_float DONE (all drivers)
   GL_KHR_blend_equation_advancednot started
   GL_KHR_debug  DONE (all drivers)
-  GL_KHR_robustness 90% done (the ARB 
variant)
+  GL_KHR_robustness in progress (90% done 
- the ARB variant)
   GL_KHR_texture_compression_astc_ldr   DONE (i965/gen9+)
   GL_OES_copy_image not started (based on 
GL_ARB_copy_image, which is done for some drivers)
   GL_OES_draw_buffers_indexed   not started
-- 
2.5.0

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH 2/4] docs: Realign the "Status" column.

[Romain Failliot]

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 1ed5c1a..17522d5 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -30,8 +30,8 @@ version with all deprecated features is 3.0. Some of the 
later GL features
 are exposed in the 3.0 context as extensions.
 
 
-Feature   Status
-- 
+Feature Status
+--- 

 
 GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, 
softpipe
 
@@ -109,170 +109,170 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, 
radeonsi, llvmpipe, soft
 
 GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
 
-  GL_ARB_draw_buffers_blendDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_draw_indirect DONE (i965, llvmpipe, 
softpipe)
-  GL_ARB_gpu_shader5   DONE (i965)
-  - 'precise' qualifierDONE
-  - Dynamically uniform sampler array indices  DONE (softpipe)
-  - Dynamically uniform UBO array indices  DONE ()
-  - Implicit signed -> unsigned conversionsDONE
-  - Fused multiply-add DONE ()
-  - Packing/bitfield/conversion functions  DONE (softpipe)
-  - Enhanced textureGather DONE (softpipe)
-  - Geometry shader instancing DONE (llvmpipe, 
softpipe)
-  - Geometry shader multiple streams   DONE ()
-  - Enhanced per-sample shadingDONE ()
-  - Interpolation functionsDONE ()
-  - New overload resolution rules  DONE
-  GL_ARB_gpu_shader_fp64   DONE (llvmpipe, 
softpipe)
-  GL_ARB_sample_shadingDONE (i965, nv50)
-  GL_ARB_shader_subroutine DONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_tessellation_shader   DONE (i965)
-  GL_ARB_texture_buffer_object_rgb32   DONE (i965, llvmpipe, 
softpipe)
-  GL_ARB_texture_cube_map_arrayDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_texture_gatherDONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_texture_query_lod DONE (i965, nv50, 
softpipe)
-  GL_ARB_transform_feedback2   DONE (i965, nv50, 
llvmpipe, softpipe)
-  GL_ARB_transform_feedback3   DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_draw_buffers_blend DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_draw_indirect  DONE (i965, llvmpipe, 
softpipe)
+  GL_ARB_gpu_shader5DONE (i965)
+  - 'precise' qualifier DONE
+  - Dynamically uniform sampler array indices   DONE (softpipe)
+  - Dynamically uniform UBO array indices   DONE ()
+  - Implicit signed -> unsigned conversions DONE
+  - Fused multiply-add  DONE ()
+  - Packing/bitfield/conversion functions   DONE (softpipe)
+  - Enhanced textureGather  DONE (softpipe)
+  - Geometry shader instancing  DONE (llvmpipe, 
softpipe)
+  - Geometry shader multiple streamsDONE ()
+  - Enhanced per-sample shading DONE ()
+  - Interpolation functions DONE ()
+  - New overload resolution rules   DONE
+  GL_ARB_gpu_shader_fp64DONE (llvmpipe, 
softpipe)
+  GL_ARB_sample_shading DONE (i965, nv50)
+  GL_ARB_shader_subroutine  DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_tessellation_shaderDONE (i965)
+  GL_ARB_texture_buffer_object_rgb32DONE (i965, llvmpipe, 
softpipe)
+  GL_ARB_texture_cube_map_array DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_texture_gather DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_texture_query_lod  DONE (i965, nv50, 
softpipe)
+  GL_ARB_transform_feedback2DONE (i965, nv50, 
llvmpipe, softpipe)
+  GL_ARB_transform_feedback3DONE (i965, nv50, 
llvmpipe, softpipe)
 
 
 GL 4.1, GLSL 4.10 --- all DONE: nvc0, r600, radeonsi
 
-  

[Mesa-dev] [PATCH 1/4] docs: howto to read and edit GL3.txt

[Romain Failliot]

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
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -1,13 +1,28 @@
+# Status of OpenGL extensions in Mesa
 
-Status of OpenGL 3.x features in Mesa
+Here's how to read this file:
 
+all DONE: , ...
+All the extensions are done for the given list of drivers.
 
-Note: when an item is marked as "DONE" it means all the core Mesa
-infrastructure is complete but it may be the case that few (if any) drivers
-implement the features.
+DONE
+The extension is done for Mesa and no implementation is necessary on the
+driver-side.
 
+DONE ()
+The extension is done for Mesa and all the drivers in the "all DONE" list.
 
-OpenGL Core and Compatibility context support
+DONE (, ...)
+The extension is done for Mesa, all the drivers in the "all DONE" list, and
+all the drivers in the brackets.
+
+in progress
+The extension is started but not finished yet.
+
+not started
+The extension isn't started yet.
+
+# OpenGL Core and Compatibility context support
 
 OpenGL 3.1 and later versions are only supported with the Core profile.
 There are no plans to support GL_ARB_compatibility. The last supported OpenGL
-- 
2.5.0

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH 0/4] Small changes in GL3.txt (v2)

[Romain Failliot]

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 to read and edit GL3.txt
  docs: Realign the "Status" column.
  docs: Renormalize some extensions.
  docs: Renormalize older extensions.

 docs/GL3.txt | 353 +++
 1 file changed, 184 insertions(+), 169 deletions(-)

-- 
2.5.0

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Small changes in GL3.txt

[Romain Failliot]

Thanks for the explanations, I'll resend these patch the right way.

2016-03-14 10:01 GMT-04:00 Nicolai Hähnle <nhaeh...@gmail.com>:
> Hi Romain,
>
> On 13.03.2016 16:50, Romain Failliot wrote:
>>
>> 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 be glad to do it the proper way)
>
>
> It would be great if you provided git commit messages for your patches, and
> provide them in a format that is easily consumed by git. The explanations in
> your email are a good basis for such git commit messages.
>
> To produce properly formatted patches, the nicest path is via git
> send-email, since it directly produces emails with inline patches. The
> second best option (which requires less setup on your behalf) is to attach
> patches produced with git format-patch. This is harder to review, but it
> does preserve all the relevant git metadata.
>
> Apart from that, the patches look fine to me. mesamatrix.net is a useful
> service, let's help keep it running :)
>
> Cheers,
> Nicolai
>
>>
>> # gl3_txt_1_howto.patch
>> Add some explanations on how to read (and edit) GL3.txt.
>> It tends to give some sort of easy to follow standard.
>>
>> # gl3_txt_2_realign_status.patch
>> Realign the Status column to the same column number.
>>
>> # gl3_txt_3_renormalize_some_extensions.patch
>> The comment for GL_ARB_texture_buffer_object was between "DONE" and
>> the brackets, it's an exception compared to the way it's done for
>> other extensions.
>> The status of GL_KHR_robustness was "90% done", it is now "in
>> progress" and "90% done" is in the extension comment.
>>
>> # gl3_txt_4_renormalize_older_extensions.patch
>> On older extensions, there is an explanation first and the extension
>> name in brackets. I inverted that so we have the extension first and
>> then the explanation in brackets (it will help me later for the "all
>> drivers that support ").
>>
>> I might have more patches later, but I'd like to see if these are OK
>> for you first.
>>
>> Cheers!
>> Romain
>>
>>
>>
>> ___
>> mesa-dev mailing list
>> mesa-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Small changes in GL3.txt

[Romain Failliot]

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 be glad to do it the proper way)

# gl3_txt_1_howto.patch
Add some explanations on how to read (and edit) GL3.txt.
It tends to give some sort of easy to follow standard.

# gl3_txt_2_realign_status.patch
Realign the Status column to the same column number.

# gl3_txt_3_renormalize_some_extensions.patch
The comment for GL_ARB_texture_buffer_object was between "DONE" and
the brackets, it's an exception compared to the way it's done for
other extensions.
The status of GL_KHR_robustness was "90% done", it is now "in
progress" and "90% done" is in the extension comment.

# gl3_txt_4_renormalize_older_extensions.patch
On older extensions, there is an explanation first and the extension
name in brackets. I inverted that so we have the extension first and
then the explanation in brackets (it will help me later for the "all
drivers that support ").

I might have more patches later, but I'd like to see if these are OK
for you first.

Cheers!
Romain
diff --git a/docs/GL3.txt b/docs/GL3.txt
index ee7faca..1ed5c1a 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -1,13 +1,28 @@
+# Status of OpenGL extensions in Mesa
 
-Status of OpenGL 3.x features in Mesa
+Here's how to read this file:
 
+all DONE: , ...
+All the extensions are done for the given list of drivers.
 
-Note: when an item is marked as "DONE" it means all the core Mesa
-infrastructure is complete but it may be the case that few (if any) drivers
-implement the features.
+DONE
+The extension is done for Mesa and no implementation is necessary on the
+driver-side.
 
+DONE ()
+The extension is done for Mesa and all the drivers in the "all DONE" list.
 
-OpenGL Core and Compatibility context support
+DONE (, ...)
+The extension is done for Mesa, all the drivers in the "all DONE" list, and
+all the drivers in the brackets.
+
+in progress
+The extension is started but not finished yet.
+
+not started
+The extension isn't started yet.
+
+# OpenGL Core and Compatibility context support
 
 OpenGL 3.1 and later versions are only supported with the Core profile.
 There are no plans to support GL_ARB_compatibility. The last supported OpenGL
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 1ed5c1a..17522d5 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -30,8 +30,8 @@ version with all deprecated features is 3.0. Some of the later GL features
 are exposed in the 3.0 context as extensions.
 
 
-Feature   Status
-- 
+Feature Status
+--- 
 
 GL 3.0, GLSL 1.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, softpipe
 
@@ -109,170 +109,170 @@ GL 3.3, GLSL 3.30 --- all DONE: i965, nv50, nvc0, r600, radeonsi, llvmpipe, soft
 
 GL 4.0, GLSL 4.00 --- all DONE: nvc0, r600, radeonsi
 
-  GL_ARB_draw_buffers_blendDONE (i965, nv50, llvmpipe, softpipe)
-  GL_ARB_draw_indirect DONE (i965, llvmpipe, softpipe)
-  GL_ARB_gpu_shader5   DONE (i965)
-  - 'precise' qualifierDONE
-  - Dynamically uniform sampler array indices  DONE (softpipe)
-  - Dynamically uniform UBO array indices  DONE ()
-  - Implicit signed -> unsigned conversionsDONE
-  - Fused multiply-add DONE ()
-  - Packing/bitfield/conversion functions  DONE (softpipe)
-  - Enhanced textureGather DONE (softpipe)
-  - Geometry shader instancing DONE (llvmpipe, softpipe)
-  - Geometry shader multiple streams   DONE ()
-  - Enhanced per-sample shadingDONE ()
-  - Interpolation functionsDONE ()
-  - New overload resolution rules  DONE
-  GL_ARB_gpu_shader_fp64   DONE (llvmpipe, softpipe)
-  GL_ARB_sample_shadingDONE (i965, nv50)
-  GL_ARB_shader_subroutine DONE (i965, nv50, llvmpipe, softpipe)
-  GL_ARB_tessellation_shader   DONE (i965)
-  GL_ARB_texture_buffer_object_rgb32   DONE (i965, llvmpipe, softpipe)
-  GL_ARB_texture_cube_map_arrayDONE (i965, nv50, llvmpipe, softpipe)
-  GL_ARB_texture_gatherDONE (i965, nv50, llvmpipe, softpipe)
-  GL_ARB_texture_query_lod DONE (i965, nv50, softpipe)
-  GL_ARB_transform_feedback2  

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

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 understand some subtleties in the way
the drivers were supporting the hardwares, it's starting here:
https://github.com/MightyCreak/mesamatrix/issues/12#issuecomment-144483615
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

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.freedesktop.org/mesa/mesa/tree/docs/GL3.txt#n99

If I'm right, it means that, considering Ilia's web site,
GL_ARB_gpu_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" <mar...@gmail.com> a écrit :

> FMA isn't required really. R600 is mainly missing GS streams, which
> are complete on the mailing somewhere I think.
>
> Marek
>
> On Tue, Sep 29, 2015 at 7:32 AM, Romain Failliot
> <romain.faill...@foolstep.com> wrote:
> > 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, like "Fused
> > multiply-add", are really not done for R600 yet, or if they are indeed
> > unsupported as the parent extension status let us suppose.
> >
> > Thx
> > Romain
> >
> > 2015-07-31 23:42 GMT+02:00 Ilia Mirkin <imir...@alum.mit.edu>:
> >>
> >> OK, I believe I've fixed my list up. Note that you may have to
> >> shift-reload to get the updates, I think fd.o isn't setting the proper
> >> cache headers or something else is messed up.
> >
> >
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

@glenn:so, if I sum up, even though ARB_gpu_shader5 is marked unsupported
for R600 here (https://secure.freedesktop.org/~imirkin/glxinfo/glxinfo.html),
it doesn't mean that it is really unsupported for this driver.

@albert: thanks, I think I got that right in Mesamatrix (
http://mesamatrix.net) ;)

So that I'm clear, it's not about the fact that it is not done (i.e. red in
Mesamatrix), but I'm merely trying to find out which extensions will never
be supported by some drivers because the hardwares for them don't support
these extensions.

Cheers!
Romain

2015-09-29 17:51 GMT+02:00 Albert Freeman <albertwdfree...@gmail.com>:

> On 29 September 2015 at 14:48, Romain Failliot
> <romain.faill...@foolstep.com> 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.freedesktop.org/mesa/mesa/tree/docs/GL3.txt#n99
> >
> > If I'm right, it means that, considering Ilia's web site,
> GL_ARB_gpu_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" <mar...@gmail.com> a écrit :
> >>
> >> FMA isn't required really. R600 is mainly missing GS streams, which
> >> are complete on the mailing somewhere I think.
> >>
> >> Marek
> >>
> >> On Tue, Sep 29, 2015 at 7:32 AM, Romain Failliot
> >> <romain.faill...@foolstep.com> wrote:
> >> > 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, like "Fused
> >> > multiply-add", are really not done for R600 yet, or if they are indeed
> >> > unsupported as the parent extension status let us suppose.
> >> >
> >> > Thx
> >> > Romain
> >> >
> >> > 2015-07-31 23:42 GMT+02:00 Ilia Mirkin <imir...@alum.mit.edu>:
> >> >>
> >> >> OK, I believe I've fixed my list up. Note that you may have to
> >> >> shift-reload to get the updates, I think fd.o isn't setting the
> proper
> >> >> cache headers or something else is messed up.
> >> >
> >> >
> >
> >
> > ___
> > mesa-dev mailing list
> > mesa-dev@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/mesa-dev
> >
> Guide to GL3.txt:
> {
> If a line starting with '-' has no braces next to it, it means it is
> supported for all drivers (if it is marked DONE).
> If a line starting with '-' has braces next to it, whatever driver/s
> is in the braces has support for that feature (if any) (if it is
> marked DONE).
> When a driver has support for all features within an extension, it is
> removed from all braces on lines starting with '-' and placed in the
> braces for the extension name (the line above the first line marked
> '-').
>
> DONE just means that non driver specific support is complete (which is
> required before any driver can support that feature/extension).
>
> Usually extensions are not advertised to GL applications until they
> are deemed complete (for the driver that is in use), this can be
> overridden with e.g. export
> MESA_EXTENSION_OVERRIDE=GL_ARB_gpu_shader5. You can also disable
> advertising of a GL feature with e.g. export
> MESA_EXTENSION_OVERRIDE=-GL_ARB_gpu_shader5.
> }
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

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 drivers, some of them will support ARB_gpu_shader5,
some won't. That's it?
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

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, like "Fused
multiply-add", are really not done for R600 yet, or if they are indeed
unsupported as the parent extension status let us suppose.

Thx
Romain

2015-07-31 23:42 GMT+02:00 Ilia Mirkin :

> OK, I believe I've fixed my list up. Note that you may have to
> shift-reload to get the updates, I think fd.o isn't setting the proper
> cache headers or something else is messed up.
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

I'll have a look at that. I'll try to see which driver is for which
GPU and then make a hardcoded list too.

Thanks Ilia!

2015-07-29 4:25 GMT-04:00 Ilia Mirkin imir...@alum.mit.edu:
 Feel free to lift the info from my glxinfo page...

 http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html

 Note the grayed out bits... it's just a hardcoded list, search for
 UNSUPPORTED in
 http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.js . Note that
 it's per hardware group, not per driver (which is a fundamental
 problem with the approach 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,

   -ilia

 On Wed, Jul 29, 2015 at 12:35 AM, Romain Failliot
 romain.faill...@foolstep.com wrote:
 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 expected by the community ;)

 Anyhow, I'd like to improve the information displayed on the site by
 graying the cells of the drivers that can't support some specific
 extensions (if it's still the case since the old r300 and swrast have
 been removed). But for that I'd need a list of pairs
 extension-driver that shows which extension is invalid for which
 driver.

 Do you know that? Or do you know where I could find this information?

 Thanks a lot!
 Romain
 ___
 mesa-dev mailing list
 mesa-dev@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/mesa-dev
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] List of unsupported extensions per driver

[Romain Failliot]

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 expected by the community ;)

Anyhow, I'd like to improve the information displayed on the site by
graying the cells of the drivers that can't support some specific
extensions (if it's still the case since the old r300 and swrast have
been removed). But for that I'd need a list of pairs
extension-driver that shows which extension is invalid for which
driver.

Do you know that? Or do you know where I could find this information?

Thanks a lot!
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [PATCH] Set llvmpipe and softpipe note only for MSAA.

[Romain Failliot]

Cool! Thanks a lot!
Le 27 nov. 2014 12:05, Roland Scheidegger srol...@vmware.com 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!
 
  I'm not familiar with the patch and merge process, I just wonder if
  it is normal that my patch isn't merged yet (it's been more than 20
  days).
  I can wait, but I just want to be sure I'm not waiting for nothing :D
 
  Thanks!
 
  2014-11-03 6:02 GMT-05:00 Roland Scheidegger srol...@vmware.com:
 
  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 the patch attached):
 
  Set llvmpipe and softpipe note only for MSAA.
 
  Right now, in mesamatrix.net
  
 https://urldefense.proofpoint.com/v2/url?u=http-3A__mesamatrix.netd=AAMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_Im=kzXQqa7IRw5KjPPr67fHHaH3RMVOcsUcvSFCWxNS8Vks=-N1IRI3obYJVa_Y2haMbftx-cr4yrp4pPyxX6LfcyqUe=
 ,
  the footnote is set so that it seems to be
  for all the features, while actually it seems to be only for the MSAA.
 
 
 
  I'm ok with that change. Well in the txt file it seemed to make sense to
  add that as a footnote for GL 3.0 (because without it you're not truly
  GL 3.0 compliant) but I see this causes problems with parsing.
 
  Roland
 


___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [PATCH] Set llvmpipe and softpipe note only for MSAA.

[Romain Failliot]

Hi!

I'm not familiar with the patch and merge process, I just wonder if
it is normal that my patch isn't merged yet (it's been more than 20
days).
I can wait, but I just want to be sure I'm not waiting for nothing :D

Thanks!

2014-11-03 6:02 GMT-05:00 Roland Scheidegger srol...@vmware.com:

 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 the patch attached):

 Set llvmpipe and softpipe note only for MSAA.

 Right now, in mesamatrix.net
 https://urldefense.proofpoint.com/v2/url?u=http-3A__mesamatrix.netd=AAMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_Im=kzXQqa7IRw5KjPPr67fHHaH3RMVOcsUcvSFCWxNS8Vks=-N1IRI3obYJVa_Y2haMbftx-cr4yrp4pPyxX6LfcyqUe=,
 the footnote is set so that it seems to be
 for all the features, while actually it seems to be only for the MSAA.



 I'm ok with that change. Well in the txt file it seemed to make sense to
 add that as a footnote for GL 3.0 (because without it you're not truly
 GL 3.0 compliant) but I see this causes problems with parsing.

 Roland

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] feature request for mesamatrix.net

[Romain Failliot]

 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't implemented yet and if it looks difficult, etc.

Hi David!

Thanks for the suggestion!
I made the changes and am waiting for a code review from my other dev
(https://github.com/MightyCreak/mesamatrix/compare/opengl-urls?expand=1).
I preferred to make a direct link to the opengl.org specs, I think
it's more mobile friendly than hover links.

Cheers,
Creak
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] The GL3.txt format

[Romain Failliot]

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 definitely be red since it's not possible for these GPU to handle
these extensions. Am I right?
If I find a nice solution that doesn't bloat up the text file, would it be
alright for you?

Cheers,
Creak

2014-08-25 15:13 GMT-04:00 Marek Olšák mar...@gmail.com:


 Also I think some features that were added to soft/llvmpipe were
 marked as swrast in GL3.txt.

 Marek


___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] The GL3.txt format

[Romain Failliot]

So right now, if it's red it really means that the r300 could do it, but
it's not been implemented yet?


2014-09-05 11:12 GMT-04:00 Marek Olšák mar...@gmail.com:


 A lot of GL3 and GL4 features actually only require GL2 hardware and
 r300 should support them.

 Marek

 On Fri, Sep 5, 2014 at 4:57 PM, Romain Failliot
 romain.faill...@foolstep.com 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 way).
  http://creak.foolstep.com/mesamatrix/
 
  I'm wondering if something could be done for the r300 status. I think it
  will definitely be red since it's not possible for these GPU to handle
 these
  extensions. Am I right?
  If I find a nice solution that doesn't bloat up the text file, would it
 be
  alright for you?
 
  Cheers,
  Creak
 
  2014-08-25 15:13 GMT-04:00 Marek Olšák mar...@gmail.com:
 
 
  Also I think some features that were added to soft/llvmpipe were
  marked as swrast in GL3.txt.
 
  Marek
 
 

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] The GL3.txt format

[Romain Failliot]

Could it be possible to add these drivers in the lists instead of me adding
some more exceptions in my code?

(I ask that mainly because I might have bug reports saying that softpipe is
green but it's never mentioned in the original file)


2014-08-25 10:28 GMT-04:00 Roland Scheidegger srol...@vmware.com:


 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 the swrast,
 the
  softpipe and the llvmpipe? Aren't they all software drivers? What's the
  difference between all of them?
 
  Thanks you!
 
  swrast is Mesa's original software rasterizer - the oldest of the
 three.  In addition to being a standalone software driver, it's also used
 for software fallbacks in the classic drivers (i915, i965, r100, r200,
 nouveau_vieux).
 
  softpipe is newer - a Gallium based software rasterizer.  It has a lot
 more features than the old swrast.  It's not particularly fast, but is
 pretty simple in comparison to llvmpipe.
 
  llvmpipe uses LLVM to compile shaders to native assembly, rather than
 using an interpreter.  As such, it's much faster than the other two.
 
  At least, that's my understanding of the situation.
 
  --Ken

 In addition to that, softpipe is more meant as a development tool - way
 easier to debug if something goes wrong than llvmpipe. It is lagging a
 bit behind llvmpipe though in some areas.
 llvmpipe, while not listed in GL3.txt, actually can do all up to and
 including GL 3.3, with the exception of real MSAA (the implementation is
 fake and not conformant). Similar story with softpipe (though it has
 more non-compliant behavior wrt texturing especially, like explicit
 derivatives not working, no offsets etc.).

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] The GL3.txt format

[Romain Failliot]

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 the swrast, the
softpipe and the llvmpipe? Aren't they all software drivers? What's the
difference between all of them?

Thanks you!


2014-08-23 20:02 GMT-04:00 Marek Olšák mar...@gmail.com:


 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
 romain.faill...@foolstep.com wrote:
  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 is a DONE () -- with parenthesis, but nothing in it --
 it
  means that I should just take the all DONE: list, isn't it?
 
  Also, for the lines beginning with a -, I took the drivers
 compatibility
  of the parent line, i.e. the first before without a -.
 
  Is it right?
 
  And if you would like to format this file a bit more, that would help for
  the future ;)
 
  Thank you!
 
  Creak
 
  ___
  mesa-dev mailing list
  mesa-dev@lists.freedesktop.org
  http://lists.freedesktop.org/mailman/listinfo/mesa-dev
 

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] The GL3.txt format

[Romain Failliot]

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 is a DONE () -- with parenthesis, but nothing in it -- it
means that I should just take the all DONE: list, isn't it?

Also, for the lines beginning with a -, I took the drivers compatibility
of the parent line, i.e. the first before without a -.

Is it right?

And if you would like to format this file a bit more, that would help for
the future ;)

Thank you!

Creak
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] The GL3.txt format

[Romain Failliot]

 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 talking about ARB_gpu_shader5, right?
 Those are all sub-features of ARB_gs5 (it's a monster extension).


Yep (but I made something generic in case there are other monster extension
;))

Thanks!
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

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 e...@anholt.net:
 I'd definitely recommend working on a texturing format extension for
 your hardware as a great way to get started in Mesa.

In the meantime, I'll get my hands into the code...
Apparently the only texture format left is GL_ARB_texture_rgb10_a2ui.
I tried to get into the code, to see somewhere to start, but the code
doesn't really speak to me at the time... Can you give me some advices
to begin to code this feature?

Thanks!
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

2011/10/6 Heath Feather hfeat...@tabula.com:
 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.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

2011/10/6 Ian Romanick i...@freedesktop.org:
 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), nouveau drivers were bad for
my graphic card, its temperature increased until the system froze...
Have you heard of this issue and eventually a fix?

I'll retry nouveau driver, but if the issue is still here, I'll have
to buy an ATI card.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

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 get started in Mesa.

I thought deadline elimination could be a good start, but if you say
texturing format extension is doable (even for a newbie like me :)),
I'll try that!

I'll get my hand in the code now.
Be right back as soon as I can run my own mesa code :)

Thanks for all the help!

Creak
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

Hi Tom, hi Christian,

2011/9/26 Tom Stellard tstel...@gmail.com
 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 Mesa?

At the moment I have an nVidia G71 [GeForce 7950 GT].
I want to contribute to mesa because:
- I want to participate to an open source project
- I work in the game industry and I hope, one day, Linux will be a
serious platform to consider
- I think that the Floss community have an opportunity here to prove
that we can make these drivers for OpenGL 3 and 4 in less time than we
need to say it! (well maybe a little bit more...)

2011/9/26 Christian König deathsim...@vodafone.de:
 1. On what part of mesa (GLSL, interface, driver, video decoding etc..)
 do you like to work on?

At first, anything that could help me to get into the code.
Then, improve OpenGL compatibility (OpenGL 3 and 4).
And eventually maybe improve performances.

 2. How much time to you want to spare? Are you a student/professional or
 do you just want to spend some time on a hobby?

I'll do it in my spare time, for me and for free.

 3. What hardware to you have available?

Only the nVidia G71 [GeForce 7950 GT]

 4. Depending on question 1: How many experience do you have with
 different parts of programming (OpenGL, D3D, low level hardware hacking,
 etc...) ?

I have some knowledge in 3D programming, but none in low level hardware hacking.
I've done some OpenGL 2 and OpenGL ES code.
I've got really good knowledge in 3D-space programming (if it can help...)

 5. How many help do you need to get going? That could reach from
 questions like: How to install a compiler in my distro? to Where can
 I find documentation of hardware register xy?

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.
Things I've never done (or almost never) is submitting a patch to a
floss project.
But the ultimate first question would be: where is the bug tracker? :)
And the next one: do you have a simple bug to begin with. I'll do it asap.

Creak
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Help for a beginner

[Romain Failliot]

Great !! I'll read this right away!
Thanks!

2011/9/26 Benjamin Bellec b.bel...@gmail.com:
 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.
 Things I've never done (or almost never) is submitting a patch to a
 floss project.
 I wrote some words on this (in french) here:
 http://forums.fedora-fr.org/viewtopic.php?id=51681
 Its still updated despite the title of the topic.

 But the ultimate first question would be: where is the bug tracker? :)
 https://bugs.freedesktop.org/

 Benjamin

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Help for a beginner

[Romain Failliot]

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 and unwanted bug/feature. Once
plugged to this bug, I won't bother you until I finish, I'll learn by my own
at this point.

Hope someone is interested ;)

Cheers,
Romain
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev