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