nanogui: Frame buffer Interface
Subject:
Re: Frame buffer Interface
From:
Erwin Rol ####@####.####
Date:
8 Feb 2000 21:33:25 -0000
Message-Id: <38A0990B.1BCDD170@muffin.org>
Greg Haerr wrote:
>
> At this point, I don't think it's a great idea to have RTEMS get in
> the business of mouse parsing, and "specialized" events handed
> off to applications. Instead, RTEMS can fire an event when
> an input file descriptor or otherwise occurs, and the application
> (normally Microwindows in this case) can then read the
> custom data and deal with it. For instance, with this model,
> if a mouse has to change, a Microwindows shared library can
> implement the new mouse, rather than having the RTEMS kernel
> recompiled. In addition, with this model, adding a new device
A small note: RTEMS doesn't not have shared libs, nor the posibility
to load a executable from disk to execute it. Everything is one
binary image. And you will need the posibility to leave out
devices you don't need to keep the memory footh print small.
> into RTEMS is as easy as hooking up the character device,
> the driver writer doesn't in addition have to implement the
> above event interface, because it may not be used with
> Microwindows, and it's not POSIX.
>
> Regards,
>
> Greg
