Re: [Mesa-dev] Gallium interface rename proposals

[Eric Anholt]

On Sat, Sep 19, 2020 at 3:24 AM Marek Olšák  wrote:
>
> Hi,
>
> I don't know if you have been following gitlab, but there are a few cleanups 
> that I have been considering doing.
>
> Rename PIPE_TRANSFER flags to PIPE_MAP, and pipe_transfer_usage to 
> pipe_map_flags:
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5749
>
> Other proposed renames:
>
> transfer_map -> resource_map
> transfer_unmap -> resource_unmap
> transfer_flush_region -> resource_flush_mapped_range
> draw_vbo -> draw
>
> pipe_transfer_* aux helpers -> pipe_resource_* or pipe_texture_* depending on 
> context. We already have pipe_buffer_map.
>
> I'm inclined to keep the struct pipe_transfer name unchanged to indicate that 
> mappings can cause internal copies.\

I'm a fan of all of these changes, it feels like they get us closer to
normal terminology in the field.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Gallium interface rename proposals

[Brian Paul]

This all sounds find to me, FWIW.

-Brian


On 09/19/2020 04:24 AM, Marek Olšák wrote:

Hi,

I don't know if you have been following gitlab, but there are a few 
cleanups that I have been considering doing.


Rename PIPE_TRANSFER flags to PIPE_MAP, and pipe_transfer_usage to 
pipe_map_flags:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5749 



Other proposed renames:

transfer_map -> resource_map
transfer_unmap -> resource_unmap
transfer_flush_region -> resource_flush_mapped_range
draw_vbo -> draw

pipe_transfer_* aux helpers -> pipe_resource_* or pipe_texture_* 
depending on context. We already have pipe_buffer_map.


I'm inclined to keep the struct pipe_transfer name unchanged to indicate 
that mappings can cause internal copies.


Please let me know your preferences.

Thanks,
Marek


___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fmesa-devdata=02%7C01%7Cbrianp%40vmware.com%7Cbedfd0817f704e06e75808d85c863fb3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637361078970597391sdata=qI2%2BFMvRDEIePjAOjbGVwCOusUxyw6I1wwL7fJb%2Blgs%3Dreserved=0



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

Re: [Mesa-dev] Etnaviv: eglCreateWindowSurface fails with glmark2

[Fabio Estevam]

Hi Lucas,

On Mon, Sep 21, 2020 at 9:59 AM Lucas Stach  wrote:

> Try starting glmark with --visual-config red=8 as a workaround to get a
> scanout capable visual.

You are right: passing --visual-config red=8 works with the old
version of glmark2.

The latest glmark2 version works without passing any extra parameter.

I believe this has been fixed by this glmark2 commit:
https://github.com/glmark2/glmark2/commit/c50755b5a19370fef5b865c9a4a9eeb0bbe56a8f

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

Re: [Mesa-dev] XDC 2020 feedback and comments

[Jason Ekstrand]

First off, I think you all did a fantastic job.  I felt that things
ran very smoothly and, as far as the talks themselves go, I think it
went almost as smoothly as an in-person XDC.  I'm really quite
impressed.  I do have a couple pieces of more nuanced feedback:

 1. I think we were maybe a bit too scared of overloading jitsi.
Having more people in the instance for questions might have made that
portion go better.  As it was, there was only one or two talks that
had any live questions.  That said, there are a few advantages to
having things funneled through IRC, the most obvious of which being
that people can ask their question mid-talk and have it handled at the
end instead of having to remember it for 20 minutes.

 2. I really miss the hallway track.  On Thursday, after the
conference, Bas, Connor, and I used jitsi to have a chat about
ray-tracing.  That was really fun and I wish I'd done something like
that every day of XDC.  Maybe it's my own fault for not setting up
said chats but I think it could have been made more accessible (I had
no idea how to fork off a jitsi instance) and/or encouraged somehow.

--Jason

On Mon, Sep 21, 2020 at 3:07 AM Samuel Iglesias Gonsálvez
 wrote:
>
> Hi all,
>
> Huge thanks again to the entire team from Intel, for their great work
> organizing XDC 2020, our first virtual conference!
>
> As usual we're looking for feedback on both XDC itself, and the CFP
> process and program selection. Both about what was great and should be
> kept for next year's edition, and where there's room for improvement.
>
> The board does keep some notes, for those interested in what we have
> already:
>
> - XDC notes for prospective organizers:
> https://www.x.org/wiki/Events/RFP/
>
> - CFP notes: https://www.x.org/wiki/Events/PapersCommittee/
>
> If you want to send in your comments in private, please send them to
> the X.org Foundation board: bo...@foundation.x.org
>
> Cheers,
>
> Sam
> ___
> 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] Etnaviv: eglCreateWindowSurface fails with glmark2

[Fabio Estevam]

Hi Lucas,

On Mon, Sep 21, 2020 at 9:59 AM Lucas Stach  wrote:

> Since a while Mesa offers 10bit EGL configs, which have the highest
> priority and thus get selected if the application doesn't care about
> bit depth. imx-drm is unable to scanout those formats.
>
> Try starting glmark with --visual-config red=8 as a workaround to get a
> scanout capable visual.

Thanks for the suggestion.

I bumped the glmark2 version to the latest one in master and now it
runs fine without any extra parameters.

Thanks,

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

Re: [Mesa-dev] Etnaviv: eglCreateWindowSurface fails with glmark2

[Lucas Stach]

Hi Fabio,

On Mo, 2020-09-21 at 09:41 -0300, Fabio Estevam wrote:
> Hi,
> 
> I am trying to run glmark2 and I am getting the following error on an
> imx6qp-sabresd with kernel 5.8.4:
> 
> # glmark2-es2-drm -d
> Debug: Using Udev to detect the right DRM node to use
> Debug: Looking for the main GPU DRM node...
> Debug: Not found!
> Debug: Looking for a concrete GPU DRM node...
> Debug: Success!
> Debug: Trying to use the DRM node /dev/dri/card0
> Debug: Success!
> Debug: Using eglGetPlatformDisplayEXT()
> Debug: Got 6 suitable EGLConfigs:
> Debug:
> Debug: cfg buf  rgb  colorbuffer dp st config native support
> surface sample
> Debug:  id  sz  lum  r  g  b  a  th cl caveat
> render  visidtype  buf ns
> Debug: --
> --
> Debug: 0x2  32  rgb 10 10 10  2  16  0   None   true0x30334241
> 0x4   0  0
> Debug: 0xa  32  rgb  8  8  8  8  16  0   None   true0x34325241
> 0x4   0  0
> Debug: 0x3  32  rgb 10 10 10  2  24  0   None   true0x30334241
> 0x4   0  0
> Debug: 0xb  32  rgb  8  8  8  8  24  0   None   true0x34325241
> 0x4   0  0
> Debug: 0x4  32  rgb 10 10 10  2  24  8   None   true0x30334241
> 0x4   0  0
> Debug: 0xc  32  rgb  8  8  8  8  24  8   None   true0x34325241
> 0x4   0  0
> Debug:
> Debug: Best EGLConfig ID: 0x3
> Error: eglCreateWindowSurface failed with error: 0x3009
> Error: eglCreateWindowSurface failed with error: 0x3009
> Error: CanvasGeneric: Invalid EGL state
> Error: main: Could not initialize canvas
> 
> kmscube runs without issues.
> 
> glmark2-es2-drm used to work fine with older kernel/Mesa versions.
> 
> Does anyone have any ideas?

Since a while Mesa offers 10bit EGL configs, which have the highest
priority and thus get selected if the application doesn't care about
bit depth. imx-drm is unable to scanout those formats.

Try starting glmark with --visual-config red=8 as a workaround to get a
scanout capable visual.

Regards,
Lucas

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

[Mesa-dev] Etnaviv: eglCreateWindowSurface fails with glmark2

[Fabio Estevam]

Hi,

I am trying to run glmark2 and I am getting the following error on an
imx6qp-sabresd with kernel 5.8.4:

# glmark2-es2-drm -d
Debug: Using Udev to detect the right DRM node to use
Debug: Looking for the main GPU DRM node...
Debug: Not found!
Debug: Looking for a concrete GPU DRM node...
Debug: Success!
Debug: Trying to use the DRM node /dev/dri/card0
Debug: Success!
Debug: Using eglGetPlatformDisplayEXT()
Debug: Got 6 suitable EGLConfigs:
Debug:
Debug: cfg buf  rgb  colorbuffer dp st config native support surface sample
Debug:  id  sz  lum  r  g  b  a  th cl caveat render  visidtype  buf ns
Debug: 
Debug: 0x2  32  rgb 10 10 10  2  16  0   None   true0x30334241
0x4   0  0
Debug: 0xa  32  rgb  8  8  8  8  16  0   None   true0x34325241
0x4   0  0
Debug: 0x3  32  rgb 10 10 10  2  24  0   None   true0x30334241
0x4   0  0
Debug: 0xb  32  rgb  8  8  8  8  24  0   None   true0x34325241
0x4   0  0
Debug: 0x4  32  rgb 10 10 10  2  24  8   None   true0x30334241
0x4   0  0
Debug: 0xc  32  rgb  8  8  8  8  24  8   None   true0x34325241
0x4   0  0
Debug:
Debug: Best EGLConfig ID: 0x3
Error: eglCreateWindowSurface failed with error: 0x3009
Error: eglCreateWindowSurface failed with error: 0x3009
Error: CanvasGeneric: Invalid EGL state
Error: main: Could not initialize canvas

kmscube runs without issues.

glmark2-es2-drm used to work fine with older kernel/Mesa versions.

Does anyone have any ideas?

Thanks,

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

[Mesa-dev] XDC 2020 feedback and comments

[Samuel Iglesias Gonsálvez]

Hi all,

Huge thanks again to the entire team from Intel, for their great work
organizing XDC 2020, our first virtual conference!

As usual we're looking for feedback on both XDC itself, and the CFP
process and program selection. Both about what was great and should be
kept for next year's edition, and where there's room for improvement.

The board does keep some notes, for those interested in what we have
already:

- XDC notes for prospective organizers: 
https://www.x.org/wiki/Events/RFP/

- CFP notes: https://www.x.org/wiki/Events/PapersCommittee/

If you want to send in your comments in private, please send them to
the X.org Foundation board: bo...@foundation.x.org

Cheers,

Sam


signature.asc
Description: This is a digitally signed message part
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev