OK, so moving on from my previous post, I have worked out that for my requirements, I CAN use DRM (and touchscreen) by correctly identifying the right devices, which respectively are /dev/dri/by-path/platform-gpu-card and /dev/input/by-path/platform-fe205000.i2c-event, which link to the DRI card supporting dumb buffers, and the touchscreen eventX interface respectively.
Once I had also configured LVGL to not use it's own version of malloc, things progressed smoothly, particularly since the 9.1 update supplies a tick interface so I didn't have to.
I can create an on-screen keyboard, and all works well.
However, I now have an issue (well, two, strictly). I have a system which has multiple mice - I have a regular USB wireless mouse, and a mini-keyboard which has a built-in trackpad.
I see that there are entries in /dev/input for mouse0 and mouse1, but that there is also a 'mice' entry.
Am I correct in assuming that this is effectively a "multiplexed" mouse, i.e. if I read events from it, I get events from either mouse?
LVGL also doesn't seem to have a keyboard handler in the conventional sense, although it has a keypad handler. I'm guessing that the traditional platforms it is used on, such as STM, ESP et al, don't generally support such a device, although they may have matrix keypads.
Has anyone done anything with this on a linux platform, or am I hacking away down an untrodden path again?
Once I had also configured LVGL to not use it's own version of malloc, things progressed smoothly, particularly since the 9.1 update supplies a tick interface so I didn't have to.
I can create an on-screen keyboard, and all works well.
However, I now have an issue (well, two, strictly). I have a system which has multiple mice - I have a regular USB wireless mouse, and a mini-keyboard which has a built-in trackpad.
I see that there are entries in /dev/input for mouse0 and mouse1, but that there is also a 'mice' entry.
Am I correct in assuming that this is effectively a "multiplexed" mouse, i.e. if I read events from it, I get events from either mouse?
LVGL also doesn't seem to have a keyboard handler in the conventional sense, although it has a keypad handler. I'm guessing that the traditional platforms it is used on, such as STM, ESP et al, don't generally support such a device, although they may have matrix keypads.
Has anyone done anything with this on a linux platform, or am I hacking away down an untrodden path again?
Statistics: Posted by SteveSpencer — Fri Aug 09, 2024 12:59 pm