RE: [MiNT] AES in kernel

[Jo-Even.Skarstein@vital.no]

> -----Original Message-----
> From:	Vincent Manuel Barrilliot [SMTP:vbarr@cme.nist.gov]
> Sent:	Tuesday, January 09, 2001 4:20 PM
> To:	mint@fishpool.com
> Subject:	Re: [MiNT] AES in kernel
> 
> As fas as the GEM is concerned, input devices managements is up to the
> VDI, 
> which the AES should use to get its events and dispatch them.
> 
Why must it be so? If /dev/mouse worked properly, *and* it was possible for
other kernel modules to access /dev/mouse and /dev/keyboard without causing
a context switch, the "AES in kernel" design should work just fine. And the
VDI could read these devices as well.

> An AES in the kernel pauses the problem of being able to Fselect an
> VDIevent 
> 
But why use a VDIevent device? If the AES doesn't use the VDI for it's
input, there's no need for this.

> device, and also the system can be dragged down by a crashed AES. But it
> solves 
> 
The system can also be dragged down by any other crashed device driver or
filesystem. Most of the AES would run outside the kernel anyway, so would
the VDI.

> the problem of synchronisation, 32-fd limit and improves performance.
> 
Indeed.

Jo Even Skarstein

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This email with attachments is solely for the use of the individual or 
entity to whom it is addressed. Please also be aware that 
Vital Insurance/DnB Group cannot accept any payment orders or other 
legally binding correspondance with customers as a part of an email. 

This email message has been virus checked by the virus programs used 
in the Vital Insurance/DnB Group.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *