El Thu, 3 Aug 2006 09:24:14 -0400
"Timothy Miller" <[EMAIL PROTECTED]> escribio:
> On 8/3/06, Nicolas Boulay <[EMAIL PROTECTED]> wrote:
> > That's the first step. After you have to deal with the fact : is it
> > more important to have a dedicated controler that could be tricky to
> > use, or general processing unit less specialised but more versatil so
> > easier to programm ?
> >
> > For example, you could use the coprocesseur interface of the LEON to
> > add some specific instruction. If a 32 cpu is to big, 8 bits one could
> > do the job. Some ASM programm still exist for it.
>
> What I think we need is something very small and not fancy that fits
> into the 3S4000 and takes up about as much space as the VGA controller
> would have anyhow. We could try to imitate an existing instruction
> set, but I think that might be a handicap.
>
> Also, as I learned in the Advanced Computer Architecture course I just
> took last quarter, it's bad to design around an instruction set.
> Let's design an architecture, and then make an instruction set that
> implements it most trivially.
I think that vga controler must wait before other parts so it can use that
parts.
For example:
It can use bitblt to copy font characters and emulate text modes at boot.
The set mode BIOS rutine must load font on mem and prepare other things(mem
zones for char cache 4kb, real framebuffer, etc), every time a char is writed
to the card a bitblt copy the right char bitmap to the real framebuffer(it can
be easy if we chose the right address for the mem zones)
My "logic" roadmap of OGC developement over OGD1(even before OGD1)
1 Basic framebuffer, not botable, usable only as 2nd(test/auxiliar) card
(video controler[DONE], mem controler, pci minimal controler, basic driver)
2 Accelerated framebuffer, not botable
(Basic 3D part for 2D aceleration bit blit ... basic accelerated driver)
3 Accelerated framebuffer, VGA cappable, botable
(VGA controller using implemmented fearures, BIOS, ...)
4 Accelerated, 3D, video, botable, ...
("avanced" 3D, Video features(scale, yuv ...)do we have that?, others)
5 More test, more test, more test
I think too that the diferent plataform drivers must be based in a reference
driver library, so we can reuse a lot of code.
And i have doubts about the size of all the things we must put in BIOS ROM.
This is like i see it so may be i am fully wrong
Diego.
PD:Excuse my bad english
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
