On Sat, 31 Jul 2004 01:22:45 +0100, Sérgio Monteiro Basto
<[EMAIL PROTECTED]> wrote:
> On Fri, 2004-07-30 at 23:08, Felix Kühling wrote:
> > Hi,
> >
> > I'm looking into porting the savage driver to the new interface so it
> > can be built in the Mesa tree. I took a look at the r128 and mga drivers
While you're in there messing with CreateScreen what was the decision
on the framebuffer parameter in CreateNewScreen? Is this something that
should be deleted before things get shipped?
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo!
On Fri, 2004-07-30 at 23:08, Felix Kühling wrote:
> Hi,
>
> I'm looking into porting the savage driver to the new interface so it
> can be built in the Mesa tree. I took a look at the r128 and mga drivers
> for reference. I noticed that the old drivers (I still have a
> savage-2-0-0-branch lying
Felix Kühling wrote:
On Fri, 30 Jul 2004 15:24:03 -0700
Ian Romanick <[EMAIL PROTECTED]> wrote:
An old libGL will call the driver's CreateScreen function. This
function calls __driUtilCreateScreen, which does the extra work that is
now done in a new libGL, then calls the driver's CreateNewScreen
On Fri, 30 Jul 2004 15:24:03 -0700
Ian Romanick <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
>
> > I'm looking into porting the savage driver to the new interface so it
> > can be built in the Mesa tree. I took a look at the r128 and mga drivers
> > for reference. I noticed that the old driv
Felix Kühling wrote:
I'm looking into porting the savage driver to the new interface so it
can be built in the Mesa tree. I took a look at the r128 and mga drivers
for reference. I noticed that the old drivers (I still have a
savage-2-0-0-branch lying around) used to check the DRI/DDX/DRM versions
Hi,
I'm looking into porting the savage driver to the new interface so it
can be built in the Mesa tree. I took a look at the r128 and mga drivers
for reference. I noticed that the old drivers (I still have a
savage-2-0-0-branch lying around) used to check the DRI/DDX/DRM versions
(using driCheckD
