<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/tmp/openbmc.git/meta-phosphor/conf/machine/include, branch master</title>
<subtitle>OpenBMC Distribution (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=master</id>
<link rel='self' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/'/>
<updated>2025-08-19T21:14:34+00:00</updated>
<entry>
<title>RBMC: Create redundant BMC include</title>
<updated>2025-08-19T21:14:34+00:00</updated>
<author>
<name>Matt Spinler</name>
<email>spinler@us.ibm.com</email>
</author>
<published>2025-08-18T15:51:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=162061ef4af4cb5c0d792c2548cebaf974b4a04c'/>
<id>urn:sha1:162061ef4af4cb5c0d792c2548cebaf974b4a04c</id>
<content type='text'>
This file can be included in a system .conf file to enable the
redundant-bmc machine feature which can then be used in recipe
packageconfigs to enable redundant BMC functionality.

Change-Id: I4408396bf5786dc33cc783c90bc9c631a248ebec
Signed-off-by: Matt Spinler &lt;spinler@us.ibm.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/tmp/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>
<entry>
<title>meta-phosphor: add whitespace around variable definitions</title>
<updated>2025-07-07T20:34:30+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2025-07-07T20:07:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=95c4c0c1864b343707561a39d5a20d7fe12569fe'/>
<id>urn:sha1:95c4c0c1864b343707561a39d5a20d7fe12569fe</id>
<content type='text'>
Latest bitbake gives a QA warning for "lack of whitespace around the
assignment".  Clean these up.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Iff0618dacb6afcece814b2b307fef5fc82bc1324
</content>
</entry>
<entry>
<title>meta-openpower: move ibm cpu configs</title>
<updated>2025-06-10T16:10:30+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2025-06-04T02:04:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=47fc69b9557ce80209a9be83ee158e87cf6e3bb5'/>
<id>urn:sha1:47fc69b9557ce80209a9be83ee158e87cf6e3bb5</id>
<content type='text'>
Move the IBM CPU configs to the openpower layer.  The only usage of
them in meta-phosphor was for an entity-manager config that also belongs
in meta-openpower.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I0092c779afe6c92a51b3681ba5d34203f6ab6964
</content>
</entry>
<entry>
<title>meta-phosphor: simplify FLASH_SIZE specification</title>
<updated>2023-06-20T06:09:35+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2023-06-19T20:46:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=05f3b1b3683d0341ccfef633d08aa2f3a9fd8965'/>
<id>urn:sha1:05f3b1b3683d0341ccfef633d08aa2f3a9fd8965</id>
<content type='text'>
FLASH_SIZE was previously defaulted in a few bbclasses and bbappends,
but this can result in it not being defined in all recipes if the
machine has not overridden the FLASH_SIZE.  openbmc/openbmc#3876
reported one such case where the u-boot-fw-utils recipe does not
receive the correct FLASH_SIZE and ends up erasing the wrong flash
region as if it were the u-boot enviroment.  Specify it in the common
include so it is available everywhere.

Resolves openbmc/openbmc#3876.

Change-Id: Iacdde1a5d0081b54321110d655da18bb3846cd14
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
</content>
</entry>
<entry>
<title>meta-phosphor: static-norootfs: use xz for small flash images</title>
<updated>2023-03-27T15:00:35+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2023-03-24T15:38:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=9c780567682098adf1f4c261e1487cc97ee8fd41'/>
<id>urn:sha1:9c780567682098adf1f4c261e1487cc97ee8fd41</id>
<content type='text'>
The 32MB flash machines typically do not have enough space to hold
a zstd compressed rootfs, so default them to use xz.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I6f24d771e41853c13ec55c9a35bc5dff3f523cb2
</content>
</entry>
<entry>
<title>meta-phosphor: introduce static non-rootfs image type</title>
<updated>2023-01-14T01:41:49+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-12-14T15:10:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=b9e124c6a51c8a9859a2257bc9205382fc7a010e'/>
<id>urn:sha1:b9e124c6a51c8a9859a2257bc9205382fc7a010e</id>
<content type='text'>
Define a new image type 'static-norootfs' that takes the entire
rootfs and places it as the initramfs for the kernel's FIT image,
so that the BMC is entirely running from a ramdisk.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I0163f5be0a1b176e0db5f89b85f34e4feae8a588
</content>
</entry>
<entry>
<title>meta-phosphor: split image type configs to includes</title>
<updated>2023-01-14T01:41:49+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-12-09T23:03:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=e20e692f16c2d2ad59be61320fcc8bc7a52969c1'/>
<id>urn:sha1:e20e692f16c2d2ad59be61320fcc8bc7a52969c1</id>
<content type='text'>
We have reached branch-capacity in the bb.utils.contains checks
at 3 image types.  In order to be able to more easily add additional
image types, split the differences out into additional inc-snippets
for each image type.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Ibcdb5c885c67cb6d8728dfd315eb07f99b1a2173
</content>
</entry>
<entry>
<title>meta-phosphor: Add vmlinux to image types</title>
<updated>2022-03-28T14:11:54+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2022-03-28T01:44:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=74d209f0df779f35e2e0b61bf8c3af5aaf764b6b'/>
<id>urn:sha1:74d209f0df779f35e2e0b61bf8c3af5aaf764b6b</id>
<content type='text'>
Ensure the vmlinux is archived as part of the build artifacts for
debugging.

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
Change-Id: If84c284cfc60f6b8ae5c641ef7ee06255f29d8c1
</content>
</entry>
<entry>
<title>meta-phosphor: remove obmc-system-mgmt from qemu</title>
<updated>2021-11-10T18:11:44+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-11-05T13:50:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=d83b524fcf1bf3a0fa2851591e0abf845fbdeaa3'/>
<id>urn:sha1:d83b524fcf1bf3a0fa2851591e0abf845fbdeaa3</id>
<content type='text'>
It was reported that after 5a5f33c729e6b5869362172b63595422eb84a418 the
qemu images are not buildable.  Treat qemu systems like an 'evb' so that
the obmc-system-mgmt package is not included.  Make a minor change to
how evb is specified so that it is treated as a MACHINEOVERRIDE that can
be leveraged in multiple recipes.

Tested by ensuring that `evb-ast2600` still successfully resolves all
package dependencies (with `bitbake -p`).

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Iff4573aa3d4aac30a6681ed75741a6e351bda982
</content>
</entry>
</feed>
