All of lore.kernel.org
 help / color / mirror / Atom feed
From: david.hagood@gmail.com
To: linux-omap@vger.kernel.org
Subject: Getting accelerated X server running
Date: Tue, 17 Mar 2009 11:57:40 -0500 (CDT)	[thread overview]
Message-ID: <6de78edf1444a5dafbb7f3ae453a90ef.squirrel@localhost> (raw)

OK, I've managed to get the PowerVR driver compiled and loaded, created
the appropriate /dev/ entry, and now when I try to run the Xsgx as
supplied by the TI GFX SDK, I get the following:

beagleboard:/usr/X11R6_SGX# bin/Xsgx
PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet.
[4890, /USER/src/omap3-sgx/services4/srvkm/bridged/bridged_pvr_brid]
PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet.
[4890, /USER/src/omap3-sgx/services4/srvkm/bridged/bridged_pvr_brid]
sgxScreenInit: ERROR - can't enumerate pvr2d devices
Could not find the driver.  Make sure that the powervr driver has been loaded
Backtrace (1 deep):
0: bin/Xsgx [0x48038]

Fatal server error:
Segmentation fault caught

Aborted
beagleboard:/usr/X11R6_SGX# lsmod
Module                  Size  Used by
omaplfb                 8488  0
pvrsrvkm              292280  1 omaplfb
ipv6                  247228  24
beagleboard:/usr/X11R6_SGX# ls -la /dev/pvrsrvkm
crw-r--r-- 1 root root 249, 0 2009-03-17 11:41 /dev/pvrsrvkm
beagleboard:/usr/X11R6_SGX#


---------

No other X server is running. This is all begin done as root, so I don't
think there are permission issues. strace'ing the server shows that it
opens the driver file, then attempts a couple of IOCTLs that fail.

So, what am I missing? Is there some firmware/slushware/??? file that
needs to be be made available to initialize the hardware?



                 reply	other threads:[~2009-03-17 16:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6de78edf1444a5dafbb7f3ae453a90ef.squirrel@localhost \
    --to=david.hagood@gmail.com \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.