<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/OpenBmc/openbmc.git/meta-amd, branch master</title>
<subtitle>OpenBMC Distribution (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/atom?h=master</id>
<link rel='self' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/'/>
<updated>2026-03-28T16:39:38+00:00</updated>
<entry>
<title>treewide: update release compatibility</title>
<updated>2026-03-28T16:39:38+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2026-03-28T15:09:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=ab867218c90f081388ddae6259aca1f361334e26'/>
<id>urn:sha1:ab867218c90f081388ddae6259aca1f361334e26</id>
<content type='text'>
Latest yocto release will be wrynose; update layer compatibilities
accordingly.

Squash numerous commits from each upstream-layers subtree:
    (cherry picked from commit cd1179544d74026c99a4938824146cec4f5acfca)
    (cherry picked from commit 930a65579d2c159ce0b05cf81916d20a04f5835f)
    (cherry picked from commit 8028c573db6923525c2918724f2bd36d4a420e0b)
    (cherry picked from commit 1e4a9929a90a6f9608e8df7ec073d3467b6ee217)
    (cherry picked from commit a75c2f0b6f9d10c116b3da7106234bce6c8c1a4f)

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Ia5b19ed374bbc3f7a5aced7ef8bb4ec1f0da9444
</content>
</entry>
<entry>
<title>meta-amd: fix BitBake spacing for walnascar</title>
<updated>2026-03-19T15:10:51+00:00</updated>
<author>
<name>Jayanth Othayoth</name>
<email>ojayanth@gmail.com</email>
</author>
<published>2025-10-20T07:54:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=d6b501016bad685bea6ef947748c15e3bb52f11f'/>
<id>urn:sha1:d6b501016bad685bea6ef947748c15e3bb52f11f</id>
<content type='text'>
Update .bb, .bbappend, and .inc files to enforce consistent spacing
around '=' in variable assignments. This addresses stricter parsing
introduced in Yocto 5.2 (walnascar), which now rejects empty variable
names and malformed assignments (e.g., '+= "value"').

Changes:
  - Convert FOO=bar → FOO = bar, FOO+=val → FOO += val
  - Preserve indentation inside function blocks (e.g., do_install)
  - Skip lines with multiple '=' or inline Python/shell code

Reference:
  - Yocto 5.2 Migration Guide:
    https://docs.yoctoproject.org/dev/migration-guides/release-notes-5.2.html

Change-Id: Ieae25a20e090b61d7cdc69f1255d48c077eb5be3
Signed-off-by: Jayanth Othayoth &lt;ojayanth@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-amd:daytonax:kernel: shrink image size</title>
<updated>2026-03-19T15:10:51+00:00</updated>
<author>
<name>Jayanth Othayoth</name>
<email>ojayanth@gmail.com</email>
</author>
<published>2025-10-21T06:25:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=d3b6e420a62a5603e324dfd0d4a85fab98bd878b'/>
<id>urn:sha1:d3b6e420a62a5603e324dfd0d4a85fab98bd878b</id>
<content type='text'>
During the migration to Linux kernel 6.12, the Daytonax platform
encountered flash image size overflows due to increased kernel
binary size.

To mitigate this, several debug and graphics-related kernel options
were disabled to reduce the overall image footprint:

- CONFIG_FUNCTION_TRACER:
  Disables function-level instrumentation used by ftrace.
  Impact: Reduces kernel size significantly. Removes support for
  function call tracing and performance profiling.

- CONFIG_DEBUG_LIST:
  Disables runtime checks for linked list misuse.
  Impact: Saves space and runtime overhead. May reduce visibility
  into certain memory corruption bugs.

- CONFIG_DRM and CONFIG_DRM_ASPEED_GFX:
  Disables Direct Rendering Manager and Aspeed graphics support.
  Impact: Reduces graphics subsystem footprint. Suitable for
  headless BMC environments.

These changes help ensure the kernel image fits within the allocated
flash partition while retaining essential functionality for BMC
operation.

Change-Id: Ib0abbeeda89d21fc3f8d54d46f9fe9a280065692
Signed-off-by: Jayanth Othayoth &lt;ojayanth@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-amd:ethanolx:kernel: shrink image size</title>
<updated>2026-03-19T15:10:51+00:00</updated>
<author>
<name>Jayanth Othayoth</name>
<email>ojayanth@gmail.com</email>
</author>
<published>2025-10-21T06:19:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=919d88aa5d332efe932cc7697a5cc63d272f7ed4'/>
<id>urn:sha1:919d88aa5d332efe932cc7697a5cc63d272f7ed4</id>
<content type='text'>
During the migration to Linux kernel 6.12, the ethanolx platform
encountered flash image size overflows due to increased kernel
binary size.

To mitigate this, several debug and graphics-related kernel options
were disabled to reduce the overall image footprint:

- CONFIG_FUNCTION_TRACER:
  Disables function-level instrumentation used by ftrace.
  Impact: Reduces kernel size significantly. Removes support for
  function call tracing and performance profiling.

- CONFIG_DEBUG_LIST:
  Disables runtime checks for linked list misuse.
  Impact: Saves space and runtime overhead. May reduce visibility
  into certain memory corruption bugs.

- CONFIG_DRM and CONFIG_DRM_ASPEED_GFX:
  Disables Direct Rendering Manager and Aspeed graphics support.
  Impact: Reduces graphics subsystem footprint. Suitable for
  headless BMC environments.

These changes help ensure the kernel image fits within the allocated
flash partition while retaining essential functionality for BMC
operation.

Change-Id: I259ffcfeab33e4726ad5138e4f0ba9135086628f
Signed-off-by: Jayanth Othayoth &lt;ojayanth@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-amd: migrate recipes to use UNPACKDIR</title>
<updated>2026-02-25T21:35:08+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2026-02-23T21:06:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=033d9634eb151c29f623beec939c1aec59ffd7fa'/>
<id>urn:sha1:033d9634eb151c29f623beec939c1aec59ffd7fa</id>
<content type='text'>
Update recipes with file:// sources to use S = "${UNPACKDIR}" instead of
S = "${WORKDIR}/sources" and remove UNPACKDIR = "${S}" assignments.

This aligns with BitBake's UNPACKDIR migration where UNPACKDIR defaults to
${WORKDIR}/sources and S should be set relative to UNPACKDIR.

Change-Id: I73efe0fd753d837fb61757ba0dee9cff3755afb8
Signed-off-by: Andrew Geissler &lt;geissonator@yahoo.com&gt;
</content>
</entry>
<entry>
<title>meta-amd: install obmc-console-ssh service instances</title>
<updated>2026-01-21T13:26:07+00:00</updated>
<author>
<name>Andrew Geissler</name>
<email>geissonator@yahoo.com</email>
</author>
<published>2026-01-20T15:34:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=b992b56c2cdad82977bdae175c7fdec3033610ec'/>
<id>urn:sha1:b992b56c2cdad82977bdae175c7fdec3033610ec</id>
<content type='text'>
The installation of templated services has moved to the bitbake
recipes[1].

[1]: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/85881

Change-Id: Id58f0765cac9ad4d9de2d11846431f5afd211045
Signed-off-by: Andrew Geissler &lt;geissonator@yahoo.com&gt;
</content>
</entry>
<entry>
<title>led-manager: migrate configs to json</title>
<updated>2026-01-06T08:59:34+00:00</updated>
<author>
<name>Alexander Hansen</name>
<email>alexander.hansen@9elements.com</email>
</author>
<published>2025-02-10T10:58:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=d3bf1a1507a694a76ed2775a7b2e965cab5c3f3f'/>
<id>urn:sha1:d3bf1a1507a694a76ed2775a7b2e965cab5c3f3f</id>
<content type='text'>
This is in preparation for [1].

There is some script [2] which looks like it's generating yaml output,
which is not considered here. It's mentioned in [3].

If you are using that script to generate, please mention.

Tested: Don't have access to any of these platforms, relying on CI
results and feedback from others.

References:

[1] https://gerrit.openbmc.org/c/openbmc/phosphor-led-manager/+/77570
[2] https://github.com/openbmc/phosphor-mrw-tools/blob/4954d029d2d7f892976fb19d3fa9c502d64e1d1e/gen_led_groups.pl
[3] meta-phosphor/recipes-phosphor/leds/phosphor-led-manager-config-mrw-native.bb

Change-Id: I43f50ecc30f2ff3b29ca7a709a462735546bf9f9
Signed-off-by: Alexander Hansen &lt;alexander.hansen@9elements.com&gt;
</content>
</entry>
<entry>
<title>treewide: add whinlatter LAYERSERIES_COMPAT</title>
<updated>2025-07-23T16:31:44+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2025-07-23T15:27:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=a7e82f1843133483b8dbbb8430bf8dcb8c5f0a74'/>
<id>urn:sha1:a7e82f1843133483b8dbbb8430bf8dcb8c5f0a74</id>
<content type='text'>
Change-Id: I1d53510329749ff122c8a65157a72c8ff88bd306
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
</content>
</entry>
<entry>
<title>meta-phosphor: bmcweb options to PACKAGECONFIG</title>
<updated>2025-07-22T15:20:55+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed@tanous.net</email>
</author>
<published>2025-06-30T19:01:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=11a2e68c782ffe7e2e6cbf7d793b74de4c37b867'/>
<id>urn:sha1:11a2e68c782ffe7e2e6cbf7d793b74de4c37b867</id>
<content type='text'>
For some of the most commonly set bmcweb options, change them into
packageconfig entries.

Systems that used these config options have been moved to the
PACKAGECONFIG.  Some systems that had CMAKE build options still had
those directly removed.

Change-Id: I741f60a725905d67f7a8ef698f95b25895088db4
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
<entry>
<title>Fix whitespace warnings</title>
<updated>2025-07-08T22:23:02+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>etanous@nvidia.com</email>
</author>
<published>2025-07-08T17:25:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=f03e009a48783314356e5ad0d6a7ef0c7aeee329'/>
<id>urn:sha1:f03e009a48783314356e5ad0d6a7ef0c7aeee329</id>
<content type='text'>
The newest yocto version flags any assignment without a space around it
as a warning.  The apply the recommended script[1] to fix it.

[1] https://github.com/shr-project/meta-webosose/blob/jansa/master/meta-webos/scripts/add-whitespace-around-assignment.sh

Change-Id: I93c715c38d3387fbef976452aefc3f0a7b50cab9
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
</feed>
