From mint-bounce@lists.fishpool.fi Mon Dec 14 01:14:25 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=RpvOr5MX4f76uN6HUddtZoXN/G3MXnmHcFoXF3Lq9LM=; b=I9n0hkQk/ipO/U9KHMisr7bkDIxcjb2GT9VcJWTOI+Zm6k31H5leSkHELFG7iuw5v3 KbLDP0Pl648HGfhhRXYNsZZ6M8HS15+KtYOXN8eHIdyZR3FMdT3MfD9U4MdUNYpUpnwL uzc+qE28szKECBH4o6g616knBl1gOQeXNq4DY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=dNWlTbbLEcoI3WwPJEhA2wWB/K49WVqE6oWniTDQ4IJRtiSIec6p83oMGqNEPue2Vt 2hV+wwNwl/mlPViWVwOevzAE41aPN1hujLigs3e852KXqKAXLGpJVugObxa1gsAyXbEe Fy+mdNgAiw6gAqb5BbuzpSQULCLnwit8+NPXo= MIME-Version: 1.0 In-Reply-To: <4B24BDDE.5050101@freesbee.fr> References: <0944D844-C44A-41C0-9835-EE146E4BEF16@gmail.com> <11a6f2b10912121057j23eb7d03jd0a20f8d8d21e419@mail.gmail.com> <9FE28962-9732-4837-9D82-A017D5C5DCEE@gmail.com> <4B2400DC.6010809@freesbee.fr> <4B240DC3.1060705@freesbee.fr> <1260663257.20336.1248.camel@jetpack.demon.co.uk> <4B24BDDE.5050101@freesbee.fr> Date: Mon, 14 Dec 2009 17:12:27 +1100 Message-ID: <11a6f2b10912132212j1087a6c7p67aa73fd011a5fb9@mail.gmail.com> Subject: Re: [MiNT] [MiNT]patches, was: Mintlib: Bindings for EsetShift() and VsetMask() From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nBE6EPD1024267 2009/12/13 Vincent Rivière : > Helmut Karlowski wrote: >> >> I use this in xaloader, and currently xaaes is the only km I know so it >> should not be dangerous to anything else atm. > > Could you please tell us why you need to unload xaaes ? > I don't see any obvious reason (it doesn't mean there is none). > > -- > Vincent Rivière > to dynamically change AES, this would be required.. I sounds like because XaAES is the only current KM, some more work is needed in various areas of it. But without another KM to test with and against, it may be differcult to get practical results.. I have an idea for a certain type of AVSERVER that may or may not be useful as a KM. If it were a KM, it would be required that it be unloadable also.. Paul