From owner-mint@fishpool.com Thu May 22 15:04:48 2003 Date: Thu, 22 May 2003 14:43:51 +0200 (CEST) From: Standa Opichal X-X-Sender: stop@mail.idoox.com To: Odd Skancke cc: mint@fishpool.com Subject: Re: [MiNT] xaaes.atariforge.net In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi 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: List-unsubscribe: List-ID: X-List-ID: Hi! On Thu, 22 May 2003, Odd Skancke wrote: > The point is that everything hardware should be accessed via external > drivers, XDD's, XIFs and XFS's. Much easier to write drivers for other > hardware this way. But you knew this? Oh, yes, I should knew that the device driver is a need. Of course, sorry. ;) BTW: What about to redesign the FreeMiNT basic input device handling for this to become just a general mouse driver normally used. I doen't make much sense to me that you need an extra driver to be able to run AES. I'd like to see a decent IKBD (or vex_*) scanning layer that would somehow create events on the /dev/keyboard (nkcc equipped), /dev/mouse, /dev/joystick that would be used by the kernel itself as well AES or any other application that would need to. I've written this here some time ago, but noone gave me a decent answer (or I forgot that already because nothing was done in this field). Any comments? best regards STan