Holger Waechtler wrote:
>
> On Mon, 7 Jun 1999, Keith Whitwell wrote:
>
> >
> > I think a better approach would be to compile everything
> > we are capable of & do the checks at runtime.
>
> That's exactly the thing I want to do. The linux-3dnow target is currently
> the one which compiles in all available optimisations and decides at
> startup, which ones it will use. This is done by gl_identify_cpu_features.
>
> To be shure, that the feature-detection-function works correct, it gives
> out some messages at this time. As soon it is well tested, we can remove
> all related printf's.
>
> Later we can rename the linux-3dnow(-glide) to linux-generic-x86 or
> something like this.
OK. I think we should do this real soon (eg, right now) that way we can
get bug reports from the widest possible set of users to track down
problems.
> (And if the autoconf stuff works, we won't need these targets anymore - )
This sounds like it is done, perhaps we should disable the old methods
on the experimental branch for the same reasons - get people using
autoconf by default so we can shake out any problems.
> I would be happy, if we could do something similiar with the FX/NV/G200
> driver - Mesa would become a generic super-driver similiar to the SVGA
> X-Server, which decides at runtime, which hardware driver it will use.
>
> Hmmm..., what interface use the GLX-drivers -- could we use them for a
> Mesa-without-glx, too ???
I like this idea too, at least as a stopgap until PI's work is in
widespread use. The mlx/aclapi drivers were a step in this direction.
Simon P. indicated some interest in porting the g200 work to that api -
I don't know if he is still working on this or not.
Keith
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev