From mint-bounce@lists.fishpool.fi  Fri Jul  8 14:05:11 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] [XAAES] Does not generate MU_TIMER events when asked
From: Odd Skancke <ozk@atari.org>
To: MiNT List <mint@fishpool.com>
In-Reply-To: <1120765511.42cd8647bc1be@imp4-q.free.fr>
References: <20050707132928.155c2829.mandin.patrice@wanadoo.fr>
	 <1120737364.5673.93.camel@linuxbox> <1120741253.5673.106.camel@linuxbox>
	 <op.stjqubiv8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <20050707161808.4ca22b12.mandin.patrice@wanadoo.fr>
	 <1120749916.5673.132.camel@linuxbox>
	 <20050707173558.6c03162d.mandin.patrice@wanadoo.fr>
	 <1120751333.5673.140.camel@linuxbox>
	 <1120752540.42cd539c55d77@imp5-q.free.fr>
	 <1120753420.5673.144.camel@linuxbox>
	 <1120765511.42cd8647bc1be@imp4-q.free.fr>
Content-Type: text/plain
Date: Fri, 08 Jul 2005 16:02:31 +0200
Message-Id: <1120831351.6112.8.camel@linuxbox>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-4) 
Content-Transfer-Encoding: 7bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: ozk@atari.org
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>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=-0.8 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00
X-Spam-Level: 

tor, 07,.07.2005 kl. 21.45 +0200, skrev Xavier Joubert:
> Selon Odd Skancke <ozk@atari.org>:
> >  Aha? Are you absolutely sure? I thought this problem was XaAES only,
> > and that it worked on other AES's. Thats the impression I got. I think
> > Olivier also have comments about this too.
> 
> Yes, I am.

 Okie, then my assumptions were wrong ;-)

> 
> 1- It's documented this way.

 Yes, thats what I thought too. Got confused by being told this problem
was XaAES only.

> 
> 2- Please re-read Olivier's post. He describes MyAES's implementation as the one
> in XaAES before your fix. He also write that's it's the same as in other AES...
> Of course, the fact that he also misunderstood your mails make all this harder
> to decode... :)

 I reread the Oliviers post and yes, you're right ;-) I have changed it
back to the correct handling of MU_TIMER now.



 Best Regards,
Odd Skancke