- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
Implementing Better On Screen Keyboard Support in Weston and Alternatives
Good day,
I'm working on a device making use of NXP's i.MX93 chipset with an environment powered by Weston. Critically, this environment will need to display an on-screen keyboard (OSK).
Unfortunately, we're running into an issue with the available OSKs supported by Weston. Weston provides its own built-in OSK, but it is incredibly limited, and lacks many essential features that modern day OSKs have. It doesn't scale, it lacks graphical feedback on keys, certain keys are outright missing, it doesn't support swipe-typing, and graphically, it's not visually appealing.
So we looked around and found other OSKs, such as Squeekboard, Stevia, and wvkbd. With these OSKs, we ran into a problem: Weston doesn't support the necessary Wayland protocols to communicate with these OSKs (text-input-v3, input-method-v2, virtual-keyboard-v1, and wlr-layer-shell-v1).
Thus, I realized I was at a crossroad with 3 possible directions:
1. Fix up Weston's built-in keyboard to suit my needs.
2. Implement the necessary protocols in Weston to support the alternative Wayland OSKs.
3. Port over a different Wayland compositor which supports the protocols necessary for these OSKs (such as Wayfire, which is based on wlroots).
I'm aware that NXP provides 2D compositing acceleration for Weston using the G2D graphics library in their own fork of Weston (weston-imx). Thus, solution 3 would likely include adding support for G2D acceleration to the wlroots Wayland compositor library.
Thus, here's my question:
Has anyone else ran into this issue and what approach did you end up taking? Is there a possibility to have NXP officially support wlroots-based Wayland compositors as an alternative to Weston? Other ideas?
Thank you for your time!
wlroots-based Wayland isn't supported by NXP official,
it Seems wlroots only support wl_drm and zwp_linux_dmabuf_v1_interface that mesa supported.
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/egl/drivers/dri2/platform_wayland.c#L2008
maybe you can refer to weston add the eglBindWaylandDisplayWL calling in wlroots.
https://gitlab.freedesktop.org/wayland/weston/-/blob/main/libweston/renderer-gl/egl-glue.c#L657
