Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Jhalackova sle 17523 #1180

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Jhalackova sle 17523 #1180

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3a84c6d
Added overriding of config.txt options by rpi-eeprom-config.
lvicoun Apr 26, 2022
757b56d
Formatted.
lvicoun Apr 26, 2022
4f8e758
Updated SP version. Added RPi version.
lvicoun Apr 27, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 33 additions & 1 deletion xml/deployment_prep_aarch64_raspi.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,38 @@
<literal>config.txt</literal> file when needed, without overwriting any
user settings.
</para>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

<para>
To override the settings from <literal>config.txt</literal> on &rpi4;, proceed as
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is not the purpose of this tool, it is about a separate EEPROM config.

follows:
</para>
<procedure>
<step>
<para>
Extract the current configuration to the
<filename>extraconfig.txt</filename> file:
</para>
<screen>&prompt.root;rpi-eeprom-config > extraconfig.txt</screen>
</step>
<step>
<para>
Update the <filename>extraconfig.txt</filename> with the required values.
For details about possible values, refer to
<link xlink:href="https://www.raspberrypi.com/documentation/computers/config_txt.html#what-is-config-txt"/>
</para>
</step>
<step>
<para>
Use the <command>rpi-eeprom-update</command> tool to apply changes of the
<filename>extraconfig.txt</filename> file:
Comment on lines +168 to +169
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

</para>
<screen>&prompt.root;rpi-eeprom-config -a extraconfig.txt</screen>
</step>
<step>
<para>
Reboot your system.
</para>
</step>
</procedure>
</sect3>
<sect3 xml:id="sec-aarch64-deprpi-otp">
<title>OTP memory</title>
Expand Down Expand Up @@ -323,7 +355,7 @@ dtoverlay=i2c-rtc,ds1307</screen>
</para>
<variablelist>
<varlistentry>
<term>&sls; 15 SP3 Release Notes</term>
<term>&sls; 15 SP4 Release Notes</term>
Comment on lines -326 to +358
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

<listitem>
<para>
For more information about hardware compatibility, supported options and
Expand Down