This is an automated email from the ASF dual-hosted git repository. xiaoxiang781216 pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit a23aaf45c26a10f13be694b0c7a4e344b5868889 Author: Matteo Golin <[email protected]> AuthorDate: Sat May 30 11:20:39 2026 -0400 docs/raspberrypi-4b: Update frame buffer resolution select info Reflect the changes to how the frame buffer driver determines its resolution. Signed-off-by: Matteo Golin <[email protected]> --- .../platforms/arm64/bcm2711/boards/raspberrypi-4b/index.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/platforms/arm64/bcm2711/boards/raspberrypi-4b/index.rst b/Documentation/platforms/arm64/bcm2711/boards/raspberrypi-4b/index.rst index 1e6c90bcdc9..06594075912 100644 --- a/Documentation/platforms/arm64/bcm2711/boards/raspberrypi-4b/index.rst +++ b/Documentation/platforms/arm64/bcm2711/boards/raspberrypi-4b/index.rst @@ -269,12 +269,12 @@ colourful rectangles on the screen. ``memcpy``'d to the frame buffer, the image will be clear. I have not modified the frame buffer example though since this is its own limitation. -.. todo:: +.. note:: - The frame-buffer driver always sets the physical and virtual display - resolution to 1080 x 1920 pixels with a depth of 32 bits per pixel. Other - options cannot yet be configured via Kconfig, nor is there any kind of - negotiation with the display to agree on some maximum quality options. + The frame buffer driver currently uses the resolution obtained by querying + the physical display. It is also possible to use + ``CONFIG_BCM2711_FB_FORCE_RESOLUTION=y`` to force the request of your + configured default resolution instead. lvgl ----
