linguini1 opened a new pull request, #18999:
URL: https://github.com/apache/nuttx/pull/18999
## Summary
This change causes the frame buffer allocation to use the connected device's
physical resolution by default. The user also has the option to force a request
for a different, compile-time selected resolution if the physical display can
support something else the user would prefer.
## Impact
* Closes #17301
* Users now get the resolution supported by their display
* Users can override resolution selection for devices with a known, fixed
display
* Documentation contains updated information
## Testing
Using my "Pico Projector" as the display device and the `fb` example, here
is the output when the physical display resolution is used
(`CONFIG_BCM2711_FB_FORCE_RESOLUTION=n`):
```console
nsh> fb
VideoInfo:
fmt: 21
xres: 1824
yres: 984
nplanes: 1
PlaneInfo (plane 0):
fbmem: 0x3e513000
fblen: 7237632
stride: 7296
display: 0
bpp: 32
Mapped FB: 0x3e513000
0: ( 0, 0) (1824,984)
1: (165, 89) (1494,806)
2: (330,178) (1164,628)
3: (495,267) (834,450)
4: (660,356) (504,272)
5: (825,445) (174, 94)
Test finished
```
And with `CONFIG_BCM2711_FB_FORCE_RESOLUTION=y`:
```console
nsh> fb
VideoInfo:
fmt: 21
xres: 1920
yres: 1080
nplanes: 1
PlaneInfo (plane 0):
fbmem: 0x3e402000
fblen: 8355840
stride: 7680
display: 0
bpp: 32
Mapped FB: 0x3e402000
0: ( 0, 0) (1920,1080)
1: (174, 98) (1572,884)
2: (348,196) (1224,688)
3: (522,294) (876,492)
4: (696,392) (528,296)
5: (870,490) (180,100)
Test finished
```
--
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]
