Re: [MiNT] XaAES / GEM memory issues

[Odd Skancke <oskancke@online.no>]

On Mon, 8 Jan 2001, Sven Karlsson wrote:

> Hi Frank,
> 
> > > Frank, do you have any specific reasons why not to integrate these parts
> > > of VDI and AES?
> > 
> > Yes, this completly break any os design. VDI & AES have to use proper
> > device drivers that are provided from the underlying GEMDOS.
> 

 <--SNIP-->
...

> using device drivers:
>  1. ACIA interupt occurs and is handled by the device driver
>  2. The device driver wakes the waiting AES up. (one context switch)
>  3. AES decides which application should get the event and wakes that
> application up. (second context switch)

 This seems to be the only solution in my opinion....

> 
> Using the hardware directly (AES as a super device driver)
>  1. ACIA occurs and is handled the AES
>  2. AES decides which application should get the event and wakes the
> applciation up. (one context switch)

 ... because with this option, only the AES and it's "clients" would ever
get mouse/kbd events. I think that any hardware events like mouse/kbd has
to be handled by the kernel by means of device drivers. It has to be the
device driver that decides which app should get which events, based on
which application is "on top". Since there is more to MiNT than the
VDI/AES, I don't think the second would be a good option at all. Or it
could be that I have misinterpretated things badly...

 How do you propose to make other application (non-GEM/AES/VDI ones) get
mouse/kbd messages with the latter approach?

 Regards,
 
 Odd Skancke - ozk@atari.org - http://assemsoft.atari.org