<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/OpenBmc/openbmc.git/setup, branch FAN_PID</title>
<subtitle>OpenBMC Distribution (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/atom?h=FAN_PID</id>
<link rel='self' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/atom?h=FAN_PID'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/'/>
<updated>2022-06-14T04:49:03+00:00</updated>
<entry>
<title>setup: minor changes to machine list</title>
<updated>2022-06-14T04:49:03+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-05-31T14:25:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=6acb610e07e864f5ec8d371dc7964a1852d4feb4'/>
<id>urn:sha1:6acb610e07e864f5ec8d371dc7964a1852d4feb4</id>
<content type='text'>
- Pass column results to `expand` to eliminate tabs.

This enables easy copy/paste into markdown files for updating.

- Filter out QEMU machines.

We enable the QEMU machines from Yocto to be used for building but
they're not actively supported.  Remove them to reduce the noise
in the tool output.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I53c3f039cb36c705aa614627aeb40b20471c499c
</content>
</entry>
<entry>
<title>setup: enable all qemu* machines</title>
<updated>2022-04-07T20:36:34+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-03-30T15:32:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=cbcd6f4c549b9e9119545a17a48191930841739d'/>
<id>urn:sha1:cbcd6f4c549b9e9119545a17a48191930841739d</id>
<content type='text'>
The existing support for qemuarm wasn't working.  Sometimes, when
submitting recipes to upstream, it is useful to test image builds
against various qemu* machine models.  Enhance the setup script so that
we can build any of the qemu* machines that Poky supports and treat them
like a generic meta-phosphor machine.

Tested: Used `setup qemumips` and was able to `bitbake phosphor-image`
successfully.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Ide141c879dd674fe3771984f7fd41006a64ce54f
</content>
</entry>
<entry>
<title>setup: retab to soft-tabs</title>
<updated>2022-04-07T19:37:24+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-04-01T14:22:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=2c0e2b61ce98a353fef0f285568ba4952f290a1d'/>
<id>urn:sha1:2c0e2b61ce98a353fef0f285568ba4952f290a1d</id>
<content type='text'>
Change-Id: Id9d3d4ff314c0635f9f5ad6fc81d5f19977f65c1
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
</content>
</entry>
<entry>
<title>setup: handle invalid machine argument more gracefully</title>
<updated>2022-01-28T12:39:08+00:00</updated>
<author>
<name>Zev Weiss</name>
<email>zev@bewilderbeest.net</email>
</author>
<published>2022-01-28T05:15:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=1ebfa83c9f0581514a59a93ad556b942857d2290'/>
<id>urn:sha1:1ebfa83c9f0581514a59a93ad556b942857d2290</id>
<content type='text'>
If 'setup' is sourced with an invalid machine name, the error message is
now sent to stderr and the failure is propagated back up the stack with
a non-zero return value.

Change-Id: I50ad40b58c1479ce9ee80ea52536075eddd09b4c
Signed-off-by: Zev Weiss &lt;zev@bewilderbeest.net&gt;
</content>
</entry>
<entry>
<title>setup: fix shellcheck errors</title>
<updated>2021-11-03T23:09:42+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-10-26T21:18:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=06ce8af68b0a9bd6a68b86f424b6f13596193dd9'/>
<id>urn:sha1:06ce8af68b0a9bd6a68b86f424b6f13596193dd9</id>
<content type='text'>
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I4c09e61294506659500f9760993dd4b8b6f22f23
</content>
</entry>
<entry>
<title>setup: skip non-phosphor machines</title>
<updated>2021-02-20T01:49:38+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-02-20T01:45:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=aef980975e4ed5f11b990decee6903178188a363'/>
<id>urn:sha1:aef980975e4ed5f11b990decee6903178188a363</id>
<content type='text'>
We already had logic to skip non-phosphor machines in the
'list' operation, but did not skip those machines when targeting
them.  Those machines are almost certain to not operate as
expected and in some cases, such as EVB models, we have two
meta-layers associated with the machine.  Skipping non-phosphor
machines ensures that the setup script picks the right
configuration and does not attempt to target a machine that won't
work.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: If68c27e2a8675405672df497827dde6e86147108
</content>
</entry>
<entry>
<title>setup: tolerate `which` failures</title>
<updated>2021-02-19T21:10:20+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-02-19T21:07:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=a469a0ffe98eb48e976a23675fdb02cf7d8b75e3'/>
<id>urn:sha1:a469a0ffe98eb48e976a23675fdb02cf7d8b75e3</id>
<content type='text'>
If this script is sourced in a shell that has something like
`set -e`, then it fails if the column program does not exist
because the `which columm` fails.  Make a few changes to
tolerate this and not fail:
    - Use $(...) rather than `...`.
    - Use `... || true` when appropriate to allow continuance.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I9008778e8aee4747faa4decff74a2fb361a206ed
</content>
</entry>
<entry>
<title>setup: support any level of machine conf depth</title>
<updated>2021-01-27T22:00:40+00:00</updated>
<author>
<name>Maksym Sloyko</name>
<email>maxims@google.com</email>
</author>
<published>2020-12-08T22:11:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=f197793a823fd9ddbb31a21a465933734e626e24'/>
<id>urn:sha1:f197793a823fd9ddbb31a21a465933734e626e24</id>
<content type='text'>
Modify setup script to support any level of machine conf depth.
Internally Google uses machines that sit yet another layer deep
in the repository. Instead of adding yet another level of depth
to the expansion, look for all configs using `find`, if it's
available. If it's not, ball back to the old wildcard expansion.

Signed-off-by: Maksym Sloyko &lt;maxims@google.com&gt;
Change-Id: I1066fe5f6ece4454e3555ca97f75bd91d6da1dba
</content>
</entry>
<entry>
<title>setup: support single-deep machine conf directories</title>
<updated>2020-05-01T13:10:48+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2020-04-30T13:06:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=e855ad8576ce02db51c8fc0c89810dbd337c21e8'/>
<id>urn:sha1:e855ad8576ce02db51c8fc0c89810dbd337c21e8</id>
<content type='text'>
The witherspoon config was moved directly into meta-ibm, which caused
the setup script to not be able to find it.  Modify the setup script
to also find machine config files in single-deep meta directories.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Icb24649c2e90cd29f72e8b661085b85cde6fcad5
</content>
</entry>
<entry>
<title>setup: Use machine-specific build directories by default</title>
<updated>2020-04-27T22:08:58+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2020-04-19T11:26:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/commit/?id=ab714a26c3f883c68f08043cd7d8a0af4c84e2ba'/>
<id>urn:sha1:ab714a26c3f883c68f08043cd7d8a0af4c84e2ba</id>
<content type='text'>
bitbake can struggle to cope with switching machine configurations in
the one build directory, so default to using machine-specific build
directories.

It's recommended that the following be added to your .profile
to provide a common location for bitbake data caches:

```
BB_ENV_EXTRAWHITE="SSTATE_DIR DL_DIR"
SSTATE_DIR="/var/cache/bitbake/sstate-cache"
DL_DIR="/var/cache/bitbake/downloads"
export BB_ENV_EXTRAWHITE SSTATE_DIR DL_DIR
```

Change-Id: I70abb6a6bc901c42266f92c9f8c230b793b7a0f9
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
</content>
</entry>
</feed>
