On 17 Aug 2001, Thayne Harbaugh wrote:
> On 17 Aug 2001 11:39:38 -0400, Brian S. Julin wrote:
> >
> > On 17 Aug 2001, Thayne Harbaugh wrote:
> > > > 1) Blt/ROP/Alpha support
> > > libblt and the new libbuf?
>
> I still haven't seen libbuf show up in CVS - what's the ETA for it's
> structure to be unveiled?
I don't know. Brian?
> > > > 2) Motion Video support
> > > Isn't this in libovl or does it not work yet?
> >
> > Yes and yes.
>
> Is the structure sufficient in libovl so that someone, like myself,
> might complete libovl? What are the problems that need to be fixed with
> libovl?
The problem is that there is no target, which supports video support.
> > > > 3) management of layers (beyond what we can do with memvis/display-sub).
> > > What exactly are layers?
> >
> > DFB has it's own construct called layers which seem to be a sort
> > of region management system.
>
> I don't think I have great concern with layers - am I wrong? What are
> the "can't do without" features that layers provide?
See, what libovl supports independent from the target... :)
> > > > DirectFB won't tap your hardware to its limit,
> > >
> > > Why is that?
> >
> > Because it doesn't give the user the information needed to decide
> > how to allocate resources.
>
> This information being modes and video memory. Are there other
> resources that need to advertise information?
This is any kind of resources, not only modes and video memory. libgalloc
allows you to request a resource say "I wanna have this one with a minimum
size of 256x256[GT_8BIT] but not larger than 1024x768[GT_16BIT]" and
libgalloc will take the largest possible size, so that there is still
enough memory to allocate other resource, for example. DirectFB has no way
to provide that (so far I have seen its API).
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
