On Thu, 8 Feb 2001, Brian S. Julin wrote:
>
> On Thu, 8 Feb 2001, Christoph Egger wrote:
> > 2. Can these "features" really handled by LibOVL?
> > I am not sure, if this is the case.
> > For example, the texture-stuff - isn't that something that
> > belongs to libblit?
>
> The GGI_FT* stuff was for a layer that would end up being below
> LibBSE, the same way LibBSE is below LibOVL and Libblit. It would
> end up something like this, but I'm making up some of these library
> names on the fly:
>
> LibGGI
> LibGAlloc - Feature Negotation/Allocation API
> LibBSE
> LibOVL
> LibSprite
> LibVideoPort - YUV port, VGA feature connector,
> TV capture, etc.
> LibBlit
> LibMISC - Splitline, frame-flip-on-sync, etc.
hmm... is libmisc that one, which is already in libggi?
> Lib3DMem - 3D textures, AGP, Z-buffer, etc.
Does libxmi fit here as well?
Regarding to my question above:
Textures - if 2d or 3d - are usually distorted by the (3d) rendering
engine. That's why I asked, if the "features" can really be handled
by LibOVL. But looking at your sketch, textures and all kind of
buffers should be handled by Lib3DMem, no?
> For now, LibBSE would handle everything it could itself, but when
> the time comes that other features not handled by BSE are implemented,
> libBSE, LibGAlloc would be written and LibBSE would switch to
> making calls to LibGAlloc to find the resources it needs.
>
> The general idea is that the higher levels are simpler to code with,
> while the lower levels are capable of squeezing more resources out of the
> hardware, but they do not contain any code to actually use the resource,
> they just know how to allocate the resource. The primary function in
> LibGAlloc would be a supercharged version of setmode/checkmode that
> allows you to ask for a prioritized list of features along with the video
> mode.
I see.
> > 3. Can anyone explain me, what GGI_FT_PASSTHRU is intended to be and
> > should allow?
>
> Video overlay, e.g. from a TV capture card.
err... the comment says, it is FOR EXAMPLE a feature connector.
A feature connector of what? And what could it be else?
A Video overlay is no connector of something, no?
> > 4. These #defines are all bitwise. So, it is possible to combine and
> > use them at once?
>
> Yes. So say you want to allocate enough system RAM to hold data
> for a hardware cursor offboard, you would use:
>
> GGI_FT_SPRITE | GGI_FT_MEMVIS | GGI_FT_SPRITE_POINTER
>
> Of course, some things don't make sense. You probably won't
> see too many multi-layer character font cells with a Z-buffer :-)
Should GGI_FT_MEMVIS force to use system RAM or does it say "Fall
back to system RAM if not enough VRAM is available" ?
Christoph Egger
E-Mail: [EMAIL PROTECTED]
