From mint-bounce@lists.fishpool.fi Thu Jul 7 21:50:27 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1120765511.42cd8647bc1be@imp4-q.free.fr> Date: Thu, 07 Jul 2005 21:45:11 +0200 From: Xavier Joubert To: MiNT List Subject: Re: [MiNT] [XAAES] Does not generate MU_TIMER events when asked References: <20050707132928.155c2829.mandin.patrice@wanadoo.fr> <1120737364.5673.93.camel@linuxbox> <1120741253.5673.106.camel@linuxbox> <20050707161808.4ca22b12.mandin.patrice@wanadoo.fr> <1120 In-Reply-To: <1120753420.5673.144.camel@linuxbox> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 80.118.208.211 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: xavier.joubert@free.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: 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=2.1 tagged_above=-50.5 required=7.0 tests=BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j67JoRff012906 Selon Odd Skancke : > 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. 1- It's documented this way. 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... :) Regards, Xavier