Index:
[thread]
[date]
[subject]
[author]
From: Rodolphe Ortalo <Rodolphe.Ortalo@cert.fr>
To : ggi-develop@eskimo.com
Date: Thu, 29 Jul 1999 14:11:44 +0200
Re: Accellerated drivers (once more :( )
Jos Hulzink wrote:
> Question two: Say, I got a library. How does GGI know it has to use that
> library ? I mean: Does GGI know what chipset is behind the framebuffer ?
> Trying to tell a ViRGE it has to accellerate won't work in NVidia
> language...
The ViRGE driver should tell to the userspace software that it
has to use this or this library (with some preferences order).
This way, the ViRGE driver can say that a ViRGE-specific
userspace library is the best (hmm, potentially fastest I mean :-),
then a (to be done) generic pingpong-based library, then generic
ioctl, etc.
This is done via 'suggest-strings' setup in the driver module.
At least, it was like that...
E.g. see: degas/kgicon/kgi/accel/Cirrus/suggest_546x.inc
These strings are used for answering to ACCEL_GET_SUGGEST
ioctl commands (see 546x.c in the same directory).
These suggest strings should be in correspondance with the
suggest strings you define to name your ViRGE specific library
at build time. (There was something like this for the Matrox IIRC,
but I cannot find it again.)
Finally, note that the information I send you comes from my
own experience with some simple ioctl 'draw box' acceleration
with the Cirrus Logic 546x. So it is anterior to degas, and
more importantly anterior to the definition of kgicon. Maybe
the later introduced some changes.... (But I have not heard much
of such things.) Finally, this is not for the new KGI (but I guess
your driver is not yet for the things Steffen Seeger sent out
recently?)
Rodolphe
Index:
[thread]
[date]
[subject]
[author]