Bug #1178
closed
TFT identification not working
Added by Hammel about 1 month ago.
Updated 22 days ago.
Category:
04 - Root File System
Description
TFT displays are being reported as HDMI by functions:getConfig, which causes incorrect handling by libpibox.
It would be simpler to identify a TFT by checking for /dev/fb1. This could be done by both getConfig and libpibox independently.
I prefer libpibox to do it and add a ptools that can retrieve what libpibox thinks in getConfig.
- Description updated (diff)
- Status changed from New to In Progress
- % Done changed from 0 to 50
Fixed genConfig and tested on ironman, media and pistore hardware.
Change committed and pushed.
These changes need to be tested with Launcher which will log it's display type on startup. However, where it logs this needs to be updated to show TFT along with LCD, HDMI and UNKNOWN.
Update: actually that is already there. I just need to test with the launcher.
- % Done changed from 50 to 70
libpibox need a fix (strncmp vs strcmp when checking pibox-config display type line) to support this, along with a fix to the libpibox build (missing LDADD lines for some ptools) that was causing ptools to not get built properly.
After fixing those the HDMI is not reported correctly using the updated init scripts.
I still need to push these. Then I should rebuild libpibox in the various rpiX trees, rebuild the dev packages and reinstall all the pidevs.
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
Tested on
- Media System
- PiStore
- Ironman
All work as expected now. This covers the range of display types we might encounter.
Code committed and pushed in both dev platform and libpibox.
Closing issue.
Also available in: Atom
PDF
Updated by