From mint-bounce@lists.fishpool.fi  Wed Dec 10 12:46:21 2008
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=seznam.cz;
	h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-Smtpd:X-Seznam-User:X-QM-Mark;
	b=T+phmZ0JDk3TWW5cVvw/xE6S7HcxK3L6w6EaaJJrxfvwx0yffl2yAVH6DyQywDS/w
	XQCuln21NLmG9hxZlnGC6ZbwSe531a3e9rzRBUdsEcJHJEBzSZbyixWlAjP3Tg/SEee
	U07Re5I8rCzPDblO70YVuofMmwFHper0UnTsh/A=
Cc: mint@lists.fishpool.fi
Message-Id: <4A7CC9B8-CD45-43A7-B25F-A411119A81A2@seznam.cz>
From: Standa Opichal <opichals@seznam.cz>
To: "Olivier.Landemarre@utbm.fr" <Olivier.Landemarre@utbm.fr>
In-Reply-To: <20081207131915.56323fda0ad6pb9f@webmail1.utbm.fr>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [MiNT] the kernel (was: Re: OT Highwire)
Date: Wed, 10 Dec 2008 18:43:10 +0100
References: <212971.87942.qm@web27406.mail.ukl.yahoo.com> <28CA7DC2-DCAC-40B1-A3D3-7B48AEFF3712@seznam.cz> <20081207131915.56323fda0ad6pb9f@webmail1.utbm.fr>
X-Mailer: Apple Mail (2.929.2)
X-Smtpd: 1.1.2-1@13597:13600
X-Seznam-User: opichals@seznam.cz
X-QM-Mark: email-qm5<261791813>
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: opichals@seznam.cz
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

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:

> Hello
>
>>
>> Or 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 kernel
>> could 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
>
> Olivier
>
>>
>> Best Regards
>>
>> Standa
>>
>>
>>
>>
>
>
>
>


