patacongo commented on issue #18566: URL: https://github.com/apache/nuttx/issues/18566#issuecomment-4634678071
If you use the frame buffer driver at /dev/fb0, then you are committing to a single user solution. This writes directly to the hardware with no serialization and so is no suitable for a mult-threaded solution. A better solution would be to use the NX graphics server that will serialize the data and a ram-backed framebuffer driver each thread as controlled by the interfaces in libs/libnx. That RAM-backed framebuffer driver does not yet exist, be would not be difficult and could exported the same interface as /dev/fb0 for each asynchronous window. The multiple processes with graphics accesses can operate independently in each window. The only other alternative that comes to mind is a user "funnel" thread that serializes requests. That, however, would be a lot more work. I think a single threaded solution is inadequate as a graphics solution. ________________________________ From: Alan C. Assis ***@***.***> Sent: Friday, June 5, 2026 11:56 AM To: apache/nuttx ***@***.***> Cc: patacongo ***@***.***>; Mention ***@***.***> Subject: Re: [apache/nuttx] [GSoC 2026] Providing X11 Support Using NanoX (Issue #18566) [https://avatars.githubusercontent.com/u/37000?s=20&v=4]acassis left a comment (apache/nuttx#18566)<https://github.com/apache/nuttx/issues/18566#issuecomment-4634560359> Nice work @ppisa<https://github.com/ppisa> and @michallenc<https://github.com/michallenc> ! Kudos!!! I don't know if my comment appeared there: image.png (view on web)<https://github.com/user-attachments/assets/93e6669e-5a3e-49b6-9aa8-d951c1572f01> @Acfboy<https://github.com/Acfboy> please try to implement a src/drivers/scr_nuttx.c driver (similar to scr_fb.c) to use the NuttX Framebuffer (/dev/fb0). Besides qemu-intel64:fb you can also try with sim:fb, it will be easier to test directly on NuttX SIMulator (and easier to debug using GDB with it) — Reply to this email directly, view it on GitHub<https://github.com/apache/nuttx/issues/18566?email_source=notifications&email_token=ABFUG6UPVD5LVP72637S6O346MJWNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTGQ2TMMBTGU42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4634560359>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABFUG6TS52T2A4QHKILJUW346MJWNAVCNFSM6AAAAACWYGSI56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMZUGU3DAMZVHE>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/ABFUG6Q2ISNVXTD6R22XAC346MJWNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTGQ2TMMBTGU42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/ABFUG6XXM6ARBRX4D2OYYPT46MJWNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRTGQ2TMMBTGU42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
