On Thu, 12 Apr 2001, Morten Rolland wrote:
> "Brian S. Julin" wrote:
> >
> > Well, I've had a bit more of a look at DirectFB docs, and
> > herein lies the problem: There's no way to essentially do a "checkmode"
> > or check anything but raw capabilities; everything is gotten
> > on the spot with a "Create" call, which either fails, or actually
> > sets up the resource. So, this will present some severe challenges for
> > a GGI target and for LibGalloc.
> >
> > I guess the best we can do is just have checkmode always succeed
> > unless there is something obvious wrong -- with the result being
> > that setmode will often fail... In Galloc's case, resource requests
> > will have to also be approved more or less blindly.
>
> A very simple idea;
>
> Upon installation (of GGI, with directfb target), why not run a
> "capability investigator" that tries "all sorts" of Create, and
> outputs a file when done that lists the modes that worked?
> I have no idea about how many tries "all sorts" would requiere...
>
> Checkmode could consult this file when needed. If there is no such
> file, your strategy could be used (e.g. checkmode OKs it, praying
> it will actually work when tried).
I'd prefer to having a dynamic allocated array holding all the modes
that worked rather than a file for speed...
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
