On Mon, May 21, 2018, 7:52 AM Kirspel, Kevin <kevin-kirs...@idexx.com> wrote:
> RTEMS LIBBSD has support for EVDEV which is a standard API for keyboard, > mouse, and touchscreen. Is it the best choice, I don't know. Maybe a > better question is "What standard input system should RTEMS support?". > That's the question. Using the FreeBSD support has a number of advantages but I admit that I didn't know that support was in place. I have no idea what minimum footprint using that implies even if you don't use the TCP IP stack. In the cpukit there has long been support for a frame buffer device framework and a mouse input parsing library. I expect the FreeBSD support comes with specific device support that this is weak on. But footprint is important. Any idea how large a simple non-networked example would be with the FreeBSD code as a base? And we need examples and howtos. If I didn't know about it, it isn't reasonable to expect someone new to find it. :( --joel > Kevin Kirspel > Electrical Engineer - Sr. Staff > Idexx Roswell > 235 Hembree Park Drive > Roswell GA 30076 > Tel: (770)-510-4444 ext. 81642 > Direct: (770)-688-1642 > Fax: (770)-510-4445 > > -----Original Message----- > From: Chris Johns [mailto:chr...@rtems.org] > Sent: Sunday, May 20, 2018 5:51 PM > To: Mikhail Svetkin <mikhail.svet...@gmail.com>; Kirspel, Kevin < > kevin-kirs...@idexx.com> > Cc: users@rtems.org; Emre Cetin <hsnemrece...@gmail.com> > Subject: Re: Raspberry Pi Rtems-Graphical-Toolkit > > On 16/5/18 9:39 pm, Mikhail Svetkin wrote: > > > > I think it will be very good if RTEMS has some kind of input subsystem > > (keyboards, mouse, touchscreen) with standard API. > > > > Do you have an example standard API what would be suitable? > > Chris > _______________________________________________ > users mailing list > users@rtems.org > http://lists.rtems.org/mailman/listinfo/users
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
