Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I507f963b15106b686b04275b13137f1036afcd03
|
|
Enable the heartbeat & system-fault LEDs.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Id5f4952a61823f17bf3db764b092ef885f01caf2
|
|
Enable the heartbeat & system-fault LEDs.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Id2507a05dbc8a17cd415a1a863a0b40319e43bad
|
|
We've had it enabled in the device-tree for a while now, but didn't have
the driver support to actually make use of it configured; let's fix
that.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I3104509a4e18de948b9f671d3feb0942f9efb0e3
|
|
It seems e3c246d4i suffers from the same missing pull-up on the reset
line that also affects e3c256d4i, so enable the quirk override to
disable MMC/SDHCI driver support in u-boot as a workaround.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I411f3857110f6c7e9fefccfb330742daf417138c
|
|
As it turns out, e3c256d4i isn't the only board with this problem,
so move the u-boot config fragment to meta-common and make it available
via an override.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I7182a6a1dd12603fec1d0633edc60d018285914f
|
|
Enable SOL on all ASRock platforms. The defaults for the
xyz.openbmc_project.Ipmi.SOL interface are sufficient, but the
/xyz/openbmc_project/ipmi/sol/eth0 settings object doesn't unless
explicitly instantiated.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I176444f9e8f608667de514d450dca18ce46e2c42
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I4125773f51c8318555577206c09ca1bdb99e626e
|
|
This replicates the values (ASRock manufacturer ID and such) returned by
'ipmitool mc info' on the factory BMC firmware.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I580281b91ee0b2cd00bf5e13f8c9497adf362c9e
|
|
While on all other currently supported ASRock platforms the Aspeed VUART
provides the host serial console, we haven't had any success using it
over eSPI on e3c256d4i, so instead we're using a pair of SUARTs
connected via the UART mux.
This unforunately requires leaving the AST2500's built-in Super-IO
enabled, because the host firmware needs to access it shortly after
power-on in order to configure its UART output, so we also have to open
up some of the u-boot backdoor config options too.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ibdab607d504cebd956a7e23191c09cd0d5c44e50
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ic6c5460f587ae141ed69e704e359152713171097
|
|
This is a single-socket mini-ITX Xeon board with an AST2500 BMC, roughly
an updated version of the e3c246d4i. Note though that because this
platform uses eSPI instead of LPC, it currently requires some driver
support that's not yet in the OpenBMC kernel to actually boot the host.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ib3a13e0ac9f4130c7965ce63f804eb169262fcd3
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I8d21ddbe3d43c63576377e934739be3cec96268f
|
|
This replicates the values returned by 'ipmitool mc info' on the factory
(AMI) BMC firmware.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I1b4b76ecf5a69f11fe59a0dbf2d2522dac911cc8
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I6242d255eb49b995c56309a6b3398c72ce87a8c7
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I1195e18cbe1957702fe31ab5eb2b8a14f71bbad2
|
|
This is a half-width single-socket Xeon server board with an AST2500
BMC.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I3362a992997d02d43f409e1df00c9f8098d05c5b
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
|
|
bmcweb is already added as a default in the meta-phosphor package
groups. A large number of machines have mistakenly also explicitly
added a RDEPEND on assorted package groups, which is not necessary.
Clean these up.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifd3726d18aab45475f80d054a4640196ac0b71d2
|
|
The webui-vue package is now enabled by default. Clean up all the meta
layers to clean up the explicit enablement.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4895be56c70d2c8666dd96cec18d2c097f0c05a3
|
|
This moves the OpenBMC kernel to a v6.5 base for ASPEED.
The 6.5 kernel moved all 32-bit ARM device trees, so our BMC device
tress are now under an 'aspeed' subdirectory. This change means systems
must describe the KERNEL_DEVICETREE with the aspeed directory prefix.
There are 78 patches in the tree, with 40 of those patches not
yet queued for merging in v6.6.
The remaining out of tree patches include:
Andrew Jeffery (6):
dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation
pmbus (max31785): Add support for devicetree configuration
pmbus (core): One-shot retries for failure to set page
pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers
ARM: dts: aspeed: witherspoon: Update max31785 node
ipmi: kcs_bmc: Add a "raw" character device interface
Cédric Le Goater (1):
/dev/mem: add a devmem kernel parameter to activate the device
Eddie James (16):
ARM: dts: aspeed: bonnell: Add reserved memory for TPM event log
dt-bindings: soc: Add Aspeed XDMA Engine
soc: aspeed: Add XDMA Engine Driver
soc: aspeed: xdma: Add user interface
soc: aspeed: xdma: Add reset ioctl
soc: aspeed: xdma: Add trace events
i2c: core: Add mux root adapter operations
iio: si7020: Lock root adapter to wait for reset
eeprom: ee1004: Enable devices on multiple busses
dt-bindings: trivial-devices: Add Atmel AT30TSE004A serial eeprom
eeprom: ee1004: Add OF matching support
leds: pca955x: Refactor with helper functions and renaming
leds: pca955x: Use pointers to driver data rather than I2C client
leds: pca955x: Optimize probe led selection
leds: pca955x: Add HW blink support
leds: Ensure hardware blinking turns off when requested
Jae Hyun Yoo (1):
clk: ast2600: enable BCLK for PCI/PCIe bus always
Joel Stanley (14):
net: ftgmac100: Ensure tx descriptor updates are visible
ARM: aspeed: Add debugfs directory
ARM: soc: aspeed: Add secure boot controller support
dt-bindings: trivial-devices: Remove Infineon SLB9673 TPM
ARM: dts: nuvoton: npmc750-evb: Add default console
tpm: tis-i2c: Add more compatible strings
leds: pca955x: Revert "Remove the unused function pca95xx_num_led_regs()"
arm64: configs: Add Nuvoton NPCM defconfig
ARM: configs: aspeed: Add new FSI drivers
ARM: config: aspeed_g5: Enable SSIF BMC driver
ARM: config: aspeed: Remove FIRMWARE_MEMMAP
ARM: config: aspeed: Add Ampere SMPro drivers
ARM: config: Add openbmc defconfig
ARM: config: openbmc: Add HPE GPX and Nuvoton 7xx
Johannes Holland (1):
dt-bindings: tpm: Add schema for TIS I2C devices
Potin Lai (1):
mtd: spi-nor: winbond: Add support for w25q01jvq
Change-Id: Ib97af192391af6e71c96fe14e12cfc88c23d7a7d
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
This reverts commit ec7cab9378f548e94ee4af83946b2583d1fc7194.
ec7cab9378f5 ("Add socket-id for the first console") was only a partial
fixup of the obmc-console configurations found in the tree. For
historical reasons not all platforms that support multiple consoles
install a client configuration file for all consoles. Instead they relied
on some default behaviour that was removed in obmc-console's 4e7186918599
("Fixed broken dbus interface for multiple consoles"). Applying the
configuration changes in the manner of ec7cab9378f5 ("Add socket-id for
the first console") resulted in an asymmetric configuration between the
client and server, breaking some SSH SOL instances.
As of ae2460d0b8e8 ("obmc-console: Provide a default value for
`console-id`.") in obmc-console the requirement to specify
`socket-id`[^1] is lifted. Instead, the configuration can choose to
override a default value. This restores the original behaviour and
unbreaks SSH SOL.
[^1]: Now an alias of the `console-id` configuration key
Websocket and IPMI consoles remain broken. A fix is under development
that also takes a proper approach to supporting multiple consoles in
bmcweb, and the same solution pattern can be applied in ipmid.
More discussion of the problems involved can be found here:
https://amboar.github.io/notes/2023/05/08/happenings-in-obmc-console.html
Change-Id: I274284c791758f336da6d6301dc523bac2b5dd69
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
This drop adds socket-id for first console. This was left out before
but with the new design this parameter is required and enforced by
obmc-console code. It is decided to set "socket-id = console0"
initially because that is the current path used by bmcweb but in future
you can change this value to whatever is appropriate.
The console information is now available through the DBUS interface.
Each console server register it's object path on DBUS. The leaf node of
the object path is used to create a console path. For example in the
following console0 the leaf node "console0" is used to make up the
console path and the GUI will use console path "/console/console0" to
connect to the console.
busctl tree xyz.openbmc_project.Console.console0
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/console
`-/xyz/openbmc_project/console/console0
Here is a discord thread where new design was discussed.
https://discord.com/channels/775381525260664832/1083551792094249051
Tested:
Tested on the rainier system.
Related commits:
1) phosphor-dbus-interface: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/61486
2) obmc-console: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/62496
3) bmcweb: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62525
Change-Id: I5fd06f3aac69872a3e5032d592a9b59711795cfe
Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>
|
|
On the romed8hm3 board (as on some other ASRock AMD platforms) the host
CPU's TSI interface is connected to a super-io chip instead of being run
directly to the BMC, so in order to retrieve CPU temperature readings we
have to go through the super-io chip's back-door i2c interface. This
enables the driver support we need to do so.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I5db6fb9e1a290f42af9561c2eb889ac00cddd104
|
|
This brings the manufacturer & product info returned by 'ipmitool mc
info' into line with what the factory (AMI) firmware returns.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ia7eefefe2776f8b5693328698d969c638e9cff2b
|
|
This brings the manufacturer & product info returned by 'ipmitool mc
info' into line with what the factory (AMI) firmware returns.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ib9e2d1f7e6286083d4697ce5e4b539ca41b12be9
|
|
Like other ASRock Rack systems, romed8hm3 has the host console at
0x2f8 using IRQ 3, running at 115200 baud.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ib05faf98329ae275ae36f57e3c413b1ffbf7839e
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ifa6ea971eec3ceef9c2ba4d8ec8b1ef922d21d61
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I8aa7fc6b4105bd8a85075868de2ffb3e9d879658
|
|
This package is an old interface from 'skeleton' for which there
are no users outside of an IBM IPMI OEM handler, but the package isn't
even installed on any IBM machines. Remove all references to this
package from the tree so that it can be further removed.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icda5c156940450ab033365d7f93d5542d6646696
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:
```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```
Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
|
|
phosphor-defaults.inc now automatically inherits extrausers and
configures the default root/0penBmc account, so individual platforms no
longer need to specify either explicitly.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ic2b725f0eaadfafef67069449497e57438fa0fba
|
|
The default configuration of the VRM that supplies the VDDCR_CPU supply
rail (ISL96147) provides a voltage that's significantly too high; we
need to twiddle some magic bits in a specific register to bring it into
spec (no public documentation of this particular VRM is available as far
as I've been able to find, unfortunately).
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I44d607b827e0fc7c18b9c336e63d0188e0955fd1
|
|
This is a single-socket Epyc server board from ASRock Rack with an
AST2500 BMC and a 64MB SPI flash for the BMC firmware.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I162036f9e27a949d0cf8a85f92206ee659d884eb
|
|
Per [1][2], Yocto is starting to deprecate ABORT and has replaced
the "ABORT" action in BB_DISKMON_DIRS entries with "HALT".
1. https://wiki.yoctoproject.org/wiki/Inclusive_language
2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5
Tested:
Built obmc-phosphor-image successfully and eliminate the following
warnings:
```
WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to
"HALT", update configuration
```
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
|
|
Upstream has removed the image-prelink bbclass[1], so remove it from any
local.conf.sample that still has it enabled.
1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
The MAINTAINERS files are no longer used and are out of date (references
to IRC still exist in most of them). Remove them and rely on the OWNERS
exclusively.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0f5d2719ad97e218ce03c4503efe1b1c92ac455e
|
|
This obviates the need to specify the packages explicitly in
packagegroup-asrock-apps, and drops some chunky binaries from the image
that weren't serving much purpose, saving 389K on the compressed rofs
(about 2%).
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ieb4ef39fe8a9e6a0e3783e2710d7702fcd1654a5
|
|
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.
Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I9c224ea0de69ea378732f40f3b4d9fe8964360b0
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
Without the patches enabled by this feature, the default e3c246d4i
strapping leaves the AST2500's SuperIO enabled, which causes the host
boot process to hang (POST code 0x9a).
Fixes: #3820
Signed-off-by: Zev Weiss <zweiss@equinix.com>
Change-Id: I45de4945ff7f3322ed87494ad2c7aa41ce345438
|
|
The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:
1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.
This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.
Tested:
* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.
```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.
```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```
* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.
Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
|
|
The config has a slight hack regarding the SioPowerGood/PowerOk signals
(as explained in a comment in the file). The O_PWROK GPIO line perhaps
"should" be the SioPowerGood signal, but we also don't have
SioOnControl, so power-control disables its SIO support anyway, and
using O_PWROK as PowerOk seems to work alright.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ie3ef974e7edc172c82f63cb0129d90d098b15906
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|