On Sunday 03 July 2005 19:21, Matthew Tippett wrote:
> There is a standard name the library.
>
> See Section 8.2 - Packaging/Libraries of the OpenGL|ES spec on Khronos' web
> page.
>
> It should be libGLES_xx.so where xx is CM or CL.
Those correspond to libraries that implement OpenGL|ES. We're n
On 7/3/05, Brian Paul <[EMAIL PROTECTED]> wrote:
> I said I'd like to keep the src/egl/main/ directory cross-platform.
> The Linux version of libEGL.so could certainly have additional code in
> it. But I'm certainly open to ideas. I just don't have much time to
> spend on this project.
The code
Title: Re: DRI vs DRM
There is a standard name the library.
See Section 8.2 - Packaging/Libraries of the OpenGL|ES spec on Khronos' web page.
It should be libGLES_xx.so where xx is CM or CL.
Regards... Matthew
--
Blackberry-Sent
Matthew Tippett
Acting Engineering Manager,
On Sunday 03 July 2005 18:40, Brian Paul wrote:
> I said I'd like to keep the src/egl/main/ directory cross-platform.
> The Linux version of libEGL.so could certainly have additional code in
> it. But I'm certainly open to ideas. I just don't have much time to
> spend on this project.
I'm still
Jon Smirl wrote:
On 7/3/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
Why aren't the DRI drivers themselves EGL drivers? That's sort of the model I
was anticipating:
- eglChooseDisplayMESA("display/0")
- EGL translates to /dev/dri/card0, opens it
- ioctl: what's the DRI driver name for this dev
On 7/3/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> Why aren't the DRI drivers themselves EGL drivers? That's sort of the model I
> was anticipating:
>
> - eglChooseDisplayMESA("display/0")
> - EGL translates to /dev/dri/card0, opens it
> - ioctl: what's the DRI driver name for this device?
> -
On Sunday 03 July 2005 12:31, Jon Smirl wrote:
> On 7/3/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > Shouldn't this just be a string you pull right out of a drm ioctl? I
> > know the name currently lives in the server, but as with many things the
> > server does I think that's a mistake.
> >
>
On 7/3/05, Jon Smirl <[EMAIL PROTECTED]> wrote:
> Any ideas on what to call my DRM sysfs attribute which provides the
> name of the corresponding DRI library? I named it "dri" initially but
> that may not be descriptive enough.
I called it dri_library_name, we can always change it.
--
Jon Smirl
On 7/3/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> Shouldn't this just be a string you pull right out of a drm ioctl? I know the
> name currently lives in the server, but as with many things the server does I
> think that's a mistake.
>
> Binding EGL driver load to sysfs is not portable.
The c
Any ideas on what to call my DRM sysfs attribute which provides the
name of the corresponding DRI library? I named it "dri" initially but
that may not be descriptive enough.
--
Jon Smirl
[EMAIL PROTECTED]
---
SF.Net email is sponsored by: Disc
On Sul, 2005-07-03 at 05:04, Jon Smirl wrote:
> There are three DRI drivers with no DRM. What is up with these?
> gamma
> s3v
> trident
trident was never finished
s3v and gamma were both against old DRM and are not shipped in curren
trees
---
On Sunday 03 July 2005 00:04, Jon Smirl wrote:
> Is this table right?
>
> DRMDRI
> ffb ffb
> i810i830
> i830i830
> i915i915
With the caveat that i830 is old and deprecated.
> There are three DRI drivers with no DRM. What is up with these?
> gamma
> s3v
>
>
> There are three DRI drivers with no DRM. What is up with these?
> gamma
> s3v
> trident
>
Well gamma did have one but its got hosed as it wasn't very pretty and
responsbile for a lot of pain.. but keeping the dri driver building isnt
too much hassle.. and you never know someone out there might
13 matches
Mail list logo
