Index:
[thread]
[date]
[subject]
[author]
From: James A Simmons <jsimmons@acsu.buffalo.edu>
To : ggi-develop@eskimo.com
Date: Tue, 21 Jul 1998 13:45:17 -0400 (EDT)
Re: New ggi_graphtype
On Mon, 20 Jul 1998, James A Simmons wrote:
> On Tue, 14 Jul 1998, Andrew Apted wrote:
>
> > Marcus writes:
> >
> > > > I don't think we should have code in
> > > > every target to detect endianess to set the appropriate subscheme.
> > > > DirectBuffer uses "native" and "reverse" endian which makes more
> > > > sense in this case.
> > >
> > > Detecting native/reverse endian will require MORE work in
> > > targets than LSB/MSB. In the first case the target has to know
> > > the endianess of BOTH the CPU and the gfx hardware.
> >
> > Probably (depending on the target, e.g. KGI might handle the endianness
> > itself and export the native/reverse info to LibGGI).
> >
> > > With my suggestion it only has to know the endianess of the gfx HW.
> >
> > The advantage of native/reverse is that it shields *programs* from
> > having to know what endianness they are, and IMHO this is more important
> > than a bit of extra work within LibGGI.
>
> Should be in the kgi drivers. <ost cards have a special register to deal
> with endianess.
Yes I agree. In fact i can patch Maxtrox millenium card for this. I will
bring the patch tomorrow.
>
> >
> > Cheers,
> > _____________________________________________ ____
> > \ /
> > Andrew Apted <andrew@ggi-project.org> \/
> >
> >
> >
>
>
Index:
[thread]
[date]
[subject]
[author]