I updated my repository and the back to error doesn't crash Weston. Then It
seems not more usefull to manage unhandled device.
But to show problems that we can find in embedded solution, I continue some
explanations.
On board we have input device just for the on/off button, another for
gpio_keypad
Hi,
On 7 June 2013 11:16, Marc Chalain wrote:
> I tried and at now, it seems to add a lot of complexity.
> I solution is to read the weston.ini file inside input.c... but is it
> regular ?
This is the usual solution for now, yes.
> 2013/6/7 Daniel Stone
>>
>> Hi,
>>
>> On 7 June 2013 06:33, Ma
I tried and at now, it seems to add a lot of complexity.
I solution is to read the weston.ini file inside input.c... but is it
regular ?
2013/6/7 Daniel Stone
> Hi,
>
> On 7 June 2013 06:33, Marc Chalain wrote:
> > A input device could not be not configurated. That should not be an error
> > a
Hi,
On 7 June 2013 06:33, Marc Chalain wrote:
> A input device could not be not configurated. That should not be an error
> and just an unhandled device.
> On embedded configuration there is different input devices which are not
> used.
The intention of this codepath is to avoid the situation on
A input device could not be not configurated. That should not be an error
and just an unhandled device.
On embedded configuration there is different input devices which are not
used.
weston-evdev-unconfigure-device-unhandled.patch
Description: Binary data
_
