Jhalackova sle 17523 #1180
Jhalackova sle 17523 #1180
Conversation
| @@ -144,6 +144,38 @@ | |||
| <literal>config.txt</literal> file when needed, without overwriting any | |||
| user settings. | |||
| </para> | |||
| <para> | |||
| To override the settings from <literal>config.txt</literal> on &rpi4;, proceed as | |||
There was a problem hiding this comment.
That is not the purpose of this tool, it is about a separate EEPROM config.
| Use the <command>rpi-eeprom-update</command> tool to apply changes of the | ||
| <filename>extraconfig.txt</filename> file: |
There was a problem hiding this comment.
No, the tool is used to flash updated EEPROM firmware (plus a config for that firmware). For example, for early RPi4 models this may add support for booting from USB. Thus it should go into a new sect3 "EEPROM on Raspberry Pi 4" or so. It is not the same config as for the non-EEPROM components and should not overwrite any user-authored extraconfig.txt.
| @@ -144,6 +144,38 @@ | |||
| <literal>config.txt</literal> file when needed, without overwriting any | |||
| user settings. | |||
| </para> | |||
There was a problem hiding this comment.
Above paragraph about non-volatile memory needs to be updated to apply only to RPi3/CM3, not RPi4 which has EEPROM. Boot device order needs to be checked on, but date/time still is not saved.
| <term>&sls; 15 SP3 Release Notes</term> | ||
| <term>&sls; 15 SP4 Release Notes</term> |
There was a problem hiding this comment.
It would be advisable to keep that in a separate commit, to facilitate your backporting to SP3 (and any SLE Micro 5.x releases based on SP3). Currently combined with addition of RPi4. Could even be done in a separate SR to not be blocked by text discussion.
PR creator: Description
Applying changes for RPi 4 - updating settings in config.txt.
PR creator: Are there any relevant issues/feature requests?
PR creator: Which product versions do the changes apply to?
When opening a PR, check all versions of the documentation that your PR applies to.
main, no backport necessary)PR reviewer only: Have all backports been applied?
The doc team member merging your PR will take care of backporting to older documents.
When opening a PR, do not set the following check box.