RE: [MiNT] AES in kernel

[Vincent Manuel Barrilliot <vbarr@cme.nist.gov>]

Hi,

> 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.

I see the GEM as a package. The VDI is the low-level stuff, the AES is the 
high-level stuff.
I wouldn't like the AES to have to deal with various formats of /dev/mouse or 
/dev/keyboard. Drivers and hardware-dependant I/O are the VDI's domain I think.


> But why use a VDIevent device? If the AES doesn't use the VDI for it's
> input, there's no need for this.

Well it should !
I don't remember how the mouse packets are formatted when they come out from the 
/dev/mouse, but if it's different from Linux to FreeMiNT, I'd rather have to 
write only one driver for the VDI, not one for XaAES, one for oAESis etc :)

And the AES should use the VDI for its input, otherwize mouse accelerators 
installed with the vex_motv() VDI function won't work.

Vincent