Alex Deucher wrote:
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
3. Separate commands and data
Right now commands and data are submitted to the chip as one data
stream, either via the BCI or via DMA buffers. For easier security
checking command and data streams should be separated. Savage chip
Alex Deucher wrote:
Felix can probably phrase this better than I since he has worked more
closely with the 3D code. however, I think what he is asking is how
should vertex commends be formatted when sent to the 3D engine when
using indexed drawing commands? We want to separate drawing commands
a
On Fri, 20 Feb 2004 17:29:07 -0800
Tim Roberts <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
>
> >Felix can probably phrase this better than I since he has worked more
> >closely with the 3D code. however, I think what he is asking is how
> >should vertex commends be formatted when sent to th
On Fri, 20 Feb 2004, Alex Deucher wrote:
>> the main reason mach64 is still on a branch in DRI is it is insecure
>> by
>> default, I'm going to look into it when I've moved apartments and got
>> myself settled in again :-), I don't think putting insecure code into
>> the
>> trunk where it may get
--- Tim Roberts <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
>
> >--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> >
> >
> >>3. Separate commands and data
> >>
> >>Right now commands and data are submitted to the chip as one data
> >>stream, either via the BCI or via DMA buffers. For easier s
--- Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> > > mach64. I'd do the same with savage.
> >
> > Either way, seeing as the driver would be in the Mesa trunk, DRI
> branches
> > don't seem to make much sense anymore to me, unless it's for work
> on GLX
> > like the work Ian's doing.
> >
> > The who
On Fri, Feb 20, 2004 at 10:45:54PM +, Dave Airlie wrote:
>
> > > mach64. I'd do the same with savage.
> >
> > Either way, seeing as the driver would be in the Mesa trunk, DRI branches
> > don't seem to make much sense anymore to me, unless it's for work on GLX
> > like the work Ian's doing.
>
Dave Airlie wrote:
mach64. I'd do the same with savage.
Either way, seeing as the driver would be in the Mesa trunk, DRI branches
don't seem to make much sense anymore to me, unless it's for work on GLX
like the work Ian's doing.
The whole point of DRI branches before was to isolate new driver work
> > mach64. I'd do the same with savage.
>
> Either way, seeing as the driver would be in the Mesa trunk, DRI branches
> don't seem to make much sense anymore to me, unless it's for work on GLX
> like the work Ian's doing.
>
> The whole point of DRI branches before was to isolate new driver work,
Alan Hourihane wrote:
On Fri, Feb 20, 2004 at 05:30:57PM +0100, Felix Kühling wrote:
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane <[EMAIL PROTECTED]> wrote:
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current
On Fri, Feb 20, 2004 at 05:30:57PM +0100, Felix Kühling wrote:
> On Fri, 20 Feb 2004 14:55:55 +
> Alan Hourihane <[EMAIL PROTECTED]> wrote:
>
> > Felix,
> >
> > How about dropping your current DRI savage driver into the Mesa trunk (6.1)
> > and whipping the driver into shape with the current
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane <[EMAIL PROTECTED]> wrote:
> Felix,
>
> How about dropping your current DRI savage driver into the Mesa trunk (6.1)
> and whipping the driver into shape with the current DRI trunk.
Are you suggesting to continue development on DRI trunk or make a
On Fri, 20 Feb 2004 08:04:43 -0800
Ian Romanick <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
>
> > The last one is the easier one I think. In savagetex.c in
> > savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty
> > fancy computation of the 9bit LOD bias (probably some f
Felix Kühling wrote:
The last one is the easier one I think. In savagetex.c in
savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty
fancy computation of the 9bit LOD bias (probably some fixed point
format) from a floating point value. The lodbias mesa demo shows no
visible chang
Felix,
How about dropping your current DRI savage driver into the Mesa trunk (6.1)
and whipping the driver into shape with the current DRI trunk.
I think that will serve you best, in that Mesa 5.x is obviously being
left behind now, and if you hit problems they may be bugs in 5.x your
hitting.
I
On Thu, 19 Feb 2004 18:58:25 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
[snip]
>
> I really interested on helping, specially on savage4 driver because is the
> only one i have access, unfortunately i don't have much experience on
> hardware programing but i'm learning a lot checking the sav
On Thu, 19 Feb 2004 18:26:50 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > Hello S3 Savage users,
> >
> [snip]
>
> Felix,
>
>I'd like to give you a hand on the 3D driver while I still have some
> free time, but I have to admit, I'm
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> Hello S3 Savage users,
>
[snip]
Felix,
I'd like to give you a hand on the 3D driver while I still have some
free time, but I have to admit, I'm somewhat intimidated. What's a
good task that I can work on to get my feet wet on the 3D side? It's
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> Hello S3 Savage users,
>
>
[snip]
>
> 3. Separate commands and data
>
> Right now commands and data are submitted to the chip as one data
> stream, either via the BCI or via DMA buffers. For easier security
> checking command and data streams shoul
At 06:25 PM 19/2/2004, Felix Kühling wrote:
Hello S3 Savage users,
---snip---
From the list below I'm going to do (1) and (2) pretty soon. Basically
I'd like to do all of this, all at the same time, if I could. But I have
other things that need attention too. So anybody who has some spare time
Hello S3 Savage users,
The most basic grunt work on the Savage 3D driver has been done in the
last three months. The driver was ported to Mesa 5 and support for the
Savage3D chip family was added. The result is available in CVS on the
savage-2-0-0-branch in DRI CVS. Now I consider the driver prett
21 matches
Mail list logo
