Open Phlamethrower opened 4 years ago
So it does. I'll take a look next week.
This issue still seems to be present, FWIW.
cat /etc/rpi-issue
)?
RISC OS 5.28vcgencmd version
)?
Both of the following versions of the firmware:
*vcgencmd version
Jun 10 2020 17:52:12
Copyright (c) 2012 Broadcom
version e46bba1638cca2708b31b9daf4636770ef981735 (clean) (release) (start)
(version that shipped with the RISC OS 5.28 ROM images)
*vcgencmd version
Oct 22 2020 14:06:02
Copyright (c) 2012 Broadcom
version 74e754ff8947c58d2773253f77f6f68a303188f8 (clean) (release) (start)
(latest)
uname -a
)?
*FX 0
RISC OS 5.28 (19 Oct 2020)
Describe the bug
vcgencmd get_config hdmi_pixel_freq_limit:0
returns the errorhdmi_pixel_freq_limit:0 is unknown
, despite the fact thatvcgencmd get_config int
lists a value for it. The other settings with ":0" or ":1" suffixes appear to be affected in the same way. Behaviour seems to be the same regardless of whether a value for the setting is specified in config.txt (and regardless of whether the old-stylehdmi_pixel_freq_limit
or new-stylehdmi_pixel_freq_limit:0
name is used).To reproduce
Expected behaviour
(or similar), as per
vcgencmd get_config int
Actual behaviour
System
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Also seen under RISC OS with May 27th firmware on Pi 4B & 3B