On Wednesday 26 March 2008 19:32:22 Kristian Høgsberg wrote:
On Wed, Mar 26, 2008 at 1:50 PM, Tom Cooksey
[EMAIL PROTECTED] wrote:
...
I guess what I was thinking about was a single API which can be used on
3D-less
(or legacy, if you want) hardware and on modern hardware. If the
On Wednesday 19 March 2008 16:26:37 Zack Rusin wrote:
On Wednesday 19 March 2008 05:21:43 am Tom Cooksey wrote:
2) Sortof related to the above... it would be very cool to have a very
simple drawing API to use on top of the modesetting API. A simple blit
solid fill would surfice. I've
On Wed, Mar 26, 2008 at 1:50 PM, Tom Cooksey
[EMAIL PROTECTED] wrote:
...
I guess what I was thinking about was a single API which can be used on
3D-less
(or legacy, if you want) hardware and on modern hardware. If the graphics
hardware
is a simple pointer to a main-memory buffer which
I've had some time to play with the modesetting branch. I am using a laptop
with
an Intel 965GM, is this likely to work? At the moment, when I run
tests/modedemo
I get a hard lock. :-/
Well there is fixes pushed allmost everydays so make sure to use lastest git
:)
Yep, I'm
On Wednesday 19 March 2008 05:21:43 am Tom Cooksey wrote:
2) Sortof related to the above... it would be very cool to have a very
simple drawing API to use on top of the modesetting API. A simple blit
solid fill would surfice. I've always found it odd that the internal
kernal API for
On Friday 07 March 2008 18:35:10 Jesse Barnes wrote:
On Friday, March 07, 2008 1:21 am Tom Cooksey wrote:
I'm a developer working on getting OpenGL ES working with QWS - the window
system built into Qt/Embedded. That is, Trolltech's own windowing system,
completely independent of X. The
On Tue, 18 Mar 2008 17:54:47 +0100
Tom Cooksey [EMAIL PROTECTED] wrote:
I've had some time to play with the modesetting branch. I am using a laptop
with
an Intel 965GM, is this likely to work? At the moment, when I run
tests/modedemo
I get a hard lock. :-/
Well there is fixes pushed
to hang together. This is
what
I have so far (most of which is probably wrong, so please correct):
Write a QWS driver where the server opens the framebuffer using DRM Modesetting.
The server also initializes the DRM. QWS clients render into off-screen buffers
(pbuffers or Framebuffer objects?) using
using DRM
Modesetting.
The server also initializes the DRM. QWS clients render into off-screen
buffers
(pbuffers or Framebuffer objects?) using OpenGL (Mesa/Gallium?). The QWS
client
then magicaly gets the DRM ID of the off-screen buffer (Is there a 1:1
relationship
between a DRM buffer
On Friday, March 07, 2008 1:21 am Tom Cooksey wrote:
I'm a developer working on getting OpenGL ES working with QWS - the window
system built into Qt/Embedded. That is, Trolltech's own windowing system,
completely independent of X. The typical hardware we're working with is
PowerVR MBX, an
10 matches
Mail list logo
