| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Typo in the file name meant it wasn't getting applied.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I112be527fc90c2f85a531d5f0dc6bda1b94cb2e5
|
|
We've now got this specified in the platform-indepdent config in the
meta-asrock layer, so there's no need to repeat it in each platform's
packagegroup-asrock-apps.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I2c79abd77d2b936ae57efce74f7fc102d83dd452
|
|
All existing ASRock platforms use most of the same core packages
(entity-manager, dbus-sensors, x86-power-control, phosphor-ipmi-kcs...),
so we might as well define it all in one place instead of duplicating it
for each machine.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ife82b12cf909de6bdd770943adb30327a22438e1
|
|
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I4d532d70e35a2944fcc74a52d22e6d6fec02aba1
|
|
Upstream poky made a commit that adds an `/etc/motd` with a strong
warning that meta-poky is not intended to be used for production
purposes. There isn't anything we use directly from meta-poky anymore,
so clean up all references to it.
See poky commit a226865c8683398b5f58628ba2ec5aee1ee6c19d for additional
context.
We could potentially switch from using the `poky` subtree to picking
up OECore directly, but right now it also provides us a qualified set of
OECore + bitbake.
Tested: Built yosemite4 and confirmed `motd` output is absent when
SSHing in.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9c08650d2278b3ba26794c009adad3e593767f58
|
|
Enable the heartbeat & system-fault LEDs.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Id5f4952a61823f17bf3db764b092ef885f01caf2
|
|
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: 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
|
|
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
|
|
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
|
