Re: [MiNT] WCOWORK vs WINDOM for components

["Joakim Högberg" <gokmase@gmail.com>]

>> Hmm .. you were one of those kids where if you couldn't be captain of 
>> the team,
>> you took your ball and went home huh?  Its your way, or you won't play 
>> with us.

I trust Ozk 100% to have good reasons for not wanting to play the game as
you are suggesting. When it comes to implementations in FreeMiNT and its
components, I do put my faith in Frank Naumann and Odd Skancke, since they
(to a very, very, very large extent) are the ones who are making it all happen.

When it comes to ideas, anyone is free to express them - but they are the 2 main developers.
Final decisions should be taken by them, or am I wrong?

> Well, the ball you are playing with is too big for me. So, yes, since I
>cant play with it I go home, hoping you can make all these things come
>true. Now you are the captain, I've gone home, you show us how to play
>ball!

Again, Ozk's results with XaAES speaks for themselves. And after your numerous years of
knowledge with N.AES and clean asm coding, I can think of noone at all better suited to find
good implementations. My opinion.

Finally, the idea to use a dedicated mode instead of a new set of AES calls seems fully okay
to me. It does in no way conflict with the documented calls, since one would have to enable the
WCOWORK mode in order to have things working in the new way. As long as WCOWORK is not
enabled for any given app, XaAES will allow it to run in full compatible mode = no breaking of documented
behaviour.

Please let's not invent problems. And Ozk, please keep up your good work.

Regards,

/Joakim