Hi!VDI assembly usage should not be too much of a problem as I was talking about some other m68k kernel (linux-m68k). Anyway, if this is idea is taken seriously, fVDI (and perhaps even oVDI) could be adjusted to work on any platform, it's 'just' some more work to do ;)
The big difference from the OSIS times is that we do have an open- source VDI, AES, and importantly full featured gemlib implementations all in basically gcc compatible shape. One could simply get cairo as the base graphics layer and fix-up a VDI layer on top to provide source based compatibility.
From my point of view, the question is 'who cares?' :) Best Regards Standa On Dec 7, 2008, at 1:19 PM, Olivier.Landemarre@utbm.fr wrote:
HelloOr a different kernel... I voiced this idea before...What about porting GEM and related layer on top of the Linux-m68k kernel? That could be fun because one would probably learn something and it would not be perceived as useless in the CV. Digging deep in the Linux kernelcould be a dream job offer resulting experience.This is an old idea, first think with the OSIS project, then this was the same idea that would implement the Milan team. near ten years ago I have think the same and talk about this on fcsa without interesting anybody. Since apear Aranym that is a very good step to this project and fvdi. I have write MyAES for this project, that's why this part have very few dependency from Mint kernel. Actually only problem stay to this sort of project come from VDI layer for two reasons:- fVDI have a lot of assembly code in it- VDI in general is fully independent from AES, that is not modern at all and is a problem for a more powerfull and modern AES.At this time I have start write VDI functions, but it's far from replace any VDI and problems of health have broken development.Regards OlivierBest Regards Standa