Actions
Feature #950
closedUpdate config.txt with HDMI configurations
Status:
Rejected
Priority:
Immediate
Assignee:
Category:
04 - Root File System
Target version:
Start date:
26 Mar 2023
Due date:
% Done:
100%
Estimated time:
Severity:
01 - Critical
Description
The config.txt supports include statements.
Firstboot can identify the HDMI device name from it's EDID with
$ /opt/vc/bin/tvservice -n device_name=MPI-MPITEST
This can allow selection of a display-specific config.txt to include into config.txt. For example, the Elecrow 5in Touchscreen requires the following config.txt settings.
# elecrow 5" HDMI touchscreen hdmi_force_hotplug=1 max_usb_current=1 hdmi_drive=1 hdmi_group=2 hdmi_mode=1 hdmi_mode=87 hdmi_cvt 800 480 60 6 0 0 0 dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900 display_rotate=0
Firstboot identifies the device as the MPI-MPITEST and copies MPI-MPITEST-config.txt to hdmiconfig.txt, which is included at the end of config.txt. This makes it easy to add new display configurations, by just getting their EDID device ID and creating a config.txt specific to them.
The display specific configs will need to be stored in the dev platform under /etc/displays/.
Related issues
Updated by Hammel almost 2 years ago
- Precedes Feature #948: Support elecrow 5" hdmi touchscreen display added
Updated by Hammel almost 2 years ago
S15Config will handle updating the config.txt. Here is the pseudo code for that.
- Get the device id: /opt/vc/bin/tvservice -n
- This sets device_name=<edid device name>
- Append this to /etc/pibox-config
- Search for matching config in /etc/displays.
- If found, copy to /media/mmcblk0p1/hdmi-config.txt
- If not found, zero out /media/mmcblk0p1/hdmi-config.txt
This implies the addition of the following line to the default config.txt in the dev platform.
include hdmi-config.txt
Updated by Hammel almost 2 years ago
- Target version changed from 2.0 - Harkonnen to 3.0 - Corrino
- Severity changed from 01 - Critical to 02 - High
Moving to 3.0 since the Pi Zero support is not going to make it for PiBox 2.0.
Updated by Hammel over 1 year ago
- Priority changed from Urgent to Immediate
- Severity changed from 02 - High to 04 - Low
Updated by Hammel over 1 year ago
In the following case:
# /opt/vc/bin/tvservice -n [E] No device present
There is nothing to do since there is no attached HDMI monitor.
Updated by Hammel over 1 year ago
- Severity changed from 04 - Low to 01 - Critical
Updated by Hammel over 1 year ago
- Status changed from New to Rejected
- % Done changed from 0 to 100
This is effectively a duplicate of RM #948. The solution to the problem can be found in that issue.
Rejecting this issue.
Actions