linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: glxgears on Etnaviv: couldn't get an RGB, Double-buffered visual
Date: Fri, 24 Nov 2017 16:02:50 +0000	[thread overview]
Message-ID: <1511539365.3497.67.camel@synopsys.com> (raw)

Hello,

Being in the middle of bring-up of the new board with Vivante GPU (HSDK namely,
see?https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arc/plat-hsdk)
I was looking at simple 3D test apps to see how Etnaviv works on the hardware.

So far I was able to get kmscube working perfectly fine and the next item I took
was glxgears (for some reason I was under impression that's de facto "Hello world" app
in the GPU world). But apparently even with Xserver up and running glxgears doesn't work.

Moreover I tried the same thing on Wandboard Quad but to no avail as well.
That's what I saw:
------------------------->8---------------------
# glxgears
Error: couldn't get an RGB, Double-buffered visual

# glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig?
------------------------->8---------------------

Googling didn't help here unfortunately so maybe some pointers could be
suggested here... like what do I do wrong and if glxgears is supposed to
work on top of DRM GPU at all?

Thanks a lot in advance!

-Alexey

             reply	other threads:[~2017-11-24 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 16:02 Alexey Brodkin [this message]
2017-11-24 16:11 ` glxgears on Etnaviv: couldn't get an RGB, Double-buffered visual Lucas Stach
2017-11-24 16:25   ` Alexey Brodkin
2017-11-24 16:38     ` Lucas Stach
2017-11-24 16:49       ` Alexey Brodkin
2017-11-24 17:11         ` Lucas Stach
2017-11-24 17:23           ` Alexey Brodkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1511539365.3497.67.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).