I looked into this a bit - perhaps one solution suggested would be 2
efforts - one to get hotplugging support working on your platform in
some form or another, and some discovery/recovery code added to DirectFB
and dfb apps that care.
The old Sourceforge hotplug project is now deprecated and udev is used
by most distros. However there are a few "light" hotplugging packages
out there that might be good enough for more embedded systems.
Niels Roest wrote:
Just thinkin out loud -
general operation of DirectFB for input devices is thus:
- open the device
- create a thread
- do a blocking read, if something is read -> pass it to the DirectFB
event handler.
in other words.. if the device node disappears, something bad happens.
Along the same line, the 'device open' only happens at startup.
hth
Niels
Strelchun, Timothy wrote:
I'm working with DirectFB 1.0.1 and have found that USB keyboard and mouse
support for hot-plugging does not function.
1. Only the USB devices plugged-in before a DirectFB application begins are available for use in the application (in other words, it does not recognize devices plugged in after the application starts).
2. If any USB devices available to the DirectFB application are removed while the application is running, the DirectFB application gets a segmentation fault.
Does anybody have this working? Has anybody else encountered this problem and resolved it'?
I'm curious if is a DirectFB input provider issue, a kernel issue (we are running 2.6.23), or both?
Thanks,
Timothy
--
Timothy Strelchun
CE Software Engineering
Digital Home Group
Intel Corporation
The views expressed above are my own and not those of Intel
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
