BMC/OpenBmc/openbmc.git/meta-google, branch styhead

meta-google: networking: Embed all .network files into image

2024-12-13T01:37:57+00:00

We shouldn't need to populate any of these files at runtime, embed a base copy into the image for all interfaces. Change-Id: Ie696b2c656a65b2475ec5483e4f2f58bde7ff6fd Signed-off-by: William A. Kennington III

meta-google: ncsi: re-add neigh configs on link up

2024-12-06T02:41:15+00:00

Change-Id: Ie3d592de19398c5115e347d98ce78eeffc6c057f Signed-off-by: Mo Elbadry

meta-google: networking: add state parsing for link state change

2024-12-05T23:24:53+00:00

Change-Id: I1261a316f4b11a6300f8b94bdd5986d0523a5299 Signed-off-by: Mo Elbadry

meta-google: networking: ignore fast carrier flipping

2024-12-05T23:05:34+00:00

We have seen that in some platforms there are extra interface carrier flipping in systemd and causing the default route missing. This prevents the route being deleted when that happens. Tested: keep bringing down/up the interface and the route is always configured correctly. Change-Id: I600347fa2f1008f220c979e1585912350f111267 Signed-off-by: Yuxiao Zhang

styhead: update WORKDIR usage additional fixes

2024-12-05T21:54:29+00:00

The latest yocto release(styhead,5.1) has made a significant change[1] to the use of the WORKDIR parameter. This is additional fixes added to fix some of machines. [1]: https://docs.yoctoproject.org/next/migration-guides/migration-5.1.html#workdir-changes Change-Id: Ic43be2f9036377166e3e064f5570dddf2418af45 Signed-off-by: Jayanth Othayoth

styhead: update WORKDIR usage

2024-12-05T21:54:29+00:00

The latest yocto release(styhead,5.1) has made a significant change[1] to the use of the WORKDIR parameter. This is not the complete change required but gets us going in the right direction. [1]: https://docs.yoctoproject.org/next/migration-guides/migration-5.1.html#workdir-changes Signed-off-by: Andrew Geissler Signed-off-by: Patrick Williams Change-Id: I4f184b361be69e7704a0657a4a00cdad981aff8a

treewide: add Upstream-Status to patches

2024-12-05T21:54:29+00:00

Yocto rebase build reports QA Issue: Missing Upstream-Status in patch Added simple fix by amending patch commit message "Upstream-Status: Pending" now to unblock rebase. Change-Id: I753c2c7faa4dcede7dd2b5e6eaba79580ce5e2a1 Signed-off-by: Jayanth Othayoth

google-misc: srcrev bump 376d781c13..6461f396bb

2024-12-04T21:50:59+00:00

Mo Elbadry (1): ncsid: skip setting mac address if it matches Change-Id: I87a82554f4612ece32524619c0d8dd1feab1fc8f Signed-off-by: Andrew Geissler

google-ipmi-sys: srcrev bump e89296998b..378b59abdd

2024-11-25T23:20:14+00:00

John Wedig (1): Use new template gbmc-bare-metal-active@.target Change-Id: I0131440461f303aa8c8a4f4380e28af9a90afe56 Signed-off-by: Andrew Geissler

meta-google: bare-metal-active systemd template

2024-11-25T23:11:09+00:00

This commit converts the systemd target gbmc-bare-metal-active.target to a template, so that we can have multiple systemd targets on platforms with multiple hosts. The host number will get passed in when instantiating the template, e.g. gbmc-bare-metal-active@0.target. A number of other recipes are updated to account for this new systemd template. Tested: - Set the bare metal flag /var/google/config-package/enable-bm.flag. - Started host-gpio-monitor@0.service, which started gbmc-bare-metal-active@0.target. That target caused disable-obmc-console.service and disable-ipmi-kcs.service to start. - Rebooted the host. At this point, the host-gpio-monitor@0.service disabled gbmc-bare-metal-active@0.target. That caused disable-obmc-console.service and disable-ipmi-kcs.service to stop. - Set /run/bm-drive-cleaning-done-ack.flag and /run/bm-ready.flag. - Ran “ipmitool raw 0x2e 0x32 0x79 0x2b 0x00 0x11” on the host - Confirmed that IPMI stopped working and checked the status of gbmc-bare-metal-active@0.target and host-gpio-monitor@0.service. Change-Id: I5ecac13570fb6d167edd2175c94e65464a9c18aa Signed-off-by: John Wedig