Initial commit

This commit is contained in:
Your Name
2026-04-23 17:07:55 +08:00
commit b7e39e063b
16725 changed files with 1625565 additions and 0 deletions
+9
View File
@@ -0,0 +1,9 @@
# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}/"
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "genesis3-layer"
BBFILE_PATTERN_genesis3-layer := "^${LAYERDIR}/"
LAYERSERIES_COMPAT_genesis3-layer = "langdale mickledore"
@@ -0,0 +1,24 @@
KMACHINE = "aspeed"
KERNEL_DEVICETREE = "${KMACHINE}-ast2500-evb.dtb"
PREFERRED_PROVIDER_virtual/bootloader = "u-boot-aspeed"
PREFERRED_PROVIDER_u-boot = "u-boot-aspeed"
PREFERRED_PROVIDER_u-boot-fw-utils = "u-boot-fw-utils-aspeed"
UBOOT_MACHINE = "ast_g5_phy_defconfig"
UBOOT_DEVICETREE = "ast2500-evb"
OBMC_POWER_SUPPLY_INSTANCES = "0 1"
MACHINE_FEATURES += " \
obmc-bmc-state-mgmt \
obmc-phosphor-fan-mgmt \
obmc-phosphor-chassis-mgmt \
obmc-chassis-state-mgmt \
obmc-host-state-mgmt \
"
require conf/machine/include/ast2500.inc
require conf/machine/include/obmc-bsp-common.inc
PREFERRED_PROVIDER_virtual/phosphor-led-manager-config-native = "gen3-led-manager-config-native"
@@ -0,0 +1,18 @@
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "8"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
##OEROOT##/meta \
##OEROOT##/meta-poky \
##OEROOT##/meta-openembedded/meta-oe \
##OEROOT##/meta-openembedded/meta-networking \
##OEROOT##/meta-openembedded/meta-python \
##OEROOT##/meta-phosphor \
##OEROOT##/meta-aspeed \
##OEROOT##/meta-ibm \
##OEROOT##/meta-ibm/meta-genesis3 \
"
@@ -0,0 +1,255 @@
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
#
# Machine Selection
#
MACHINE ??= "genesis3"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
#DL_DIR ?= "${TOPDIR}/downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "openbmc-phosphor"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to ipk:
PACKAGE_CLASSES ?= "package_ipk"
#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686, x86_64, aarch64
#SDKMACHINE ?= "i686"
SANITY_TESTED_DISTROS:append ?= " *"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "src-pkgs" - add -src packages for all installed packages
# (adds source code for debugging)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
USER_CLASSES ?= "buildstats"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. It can also
# run tests against any SDK that are built. To enable this uncomment these lines.
# See classes/test{image,sdk}.bbclass for further details.
#IMAGE_CLASSES += "testimage testsdk"
#TESTIMAGE_AUTO_qemuall = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necessary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS ??= "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can be
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
#
# Yocto Project SState Mirror
#
# The Yocto Project has prebuilt artefacts available for its releases, you can enable
# use of these by uncommenting the following line. This will mean the build uses
# the network to check for artefacts at the start of builds, which does slow it down
# equally, it will also speed up the builds by not having to build things if they are
# present in the cache. It assumes you can download something faster than you can build it
# which will depend on your network.
#
#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"
#
# Qemu configuration
#
# By default native qemu will build with a builtin VNC server where graphical output can be
# seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG:append:pn-qemu-system-native = " sdl"
# By default libsdl2-native will be built, if you want to use your host's libSDL instead of
# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
#ASSUME_PROVIDED += "libsdl2-native"
# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
# a handy set of menus for controlling the emulator.
#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+"
#
# Hash Equivalence
#
# Enable support for automatically running a local hash equivalence server and
# instruct bitbake to use a hash equivalence aware signature generator. Hash
# equivalence improves reuse of sstate by detecting when a given sstate
# artifact can be reused as equivalent, even if the current task hash doesn't
# match the one that generated the artifact.
#
# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
#
#BB_HASHSERVE = "auto"
#BB_SIGNATURE_HANDLER = "OEEquivHash"
#
# Memory Resident Bitbake
#
# Bitbake's server component can stay in memory after the UI for the current command
# has completed. This means subsequent commands can run faster since there is no need
# for bitbake to reload cache files and so on. Number is in seconds, after which the
# server will shut down.
#
#BB_SERVER_TIMEOUT = "60"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "2"
@@ -0,0 +1,27 @@
SUMMARY = "YAML configuration for IBM Genesis3"
PR = "r1"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10"
inherit allarch
SRC_URI:genesis3 = " \
file://genesis3-ipmi-fru.yaml \
file://genesis3-ipmi-fru-properties.yaml \
"
S = "${WORKDIR}"
do_install:genesis3() {
install -m 0644 -D genesis3-ipmi-fru.yaml \
${D}${datadir}/${BPN}/ipmi-fru-read.yaml
install -m 0644 -D genesis3-ipmi-fru-properties.yaml \
${D}${datadir}/${BPN}/ipmi-extra-properties.yaml
}
FILES:${PN}-dev = " \
${datadir}/${BPN}/ipmi-fru-read.yaml \
${datadir}/${BPN}/ipmi-extra-properties.yaml \
"
ALLOW_EMPTY:${PN} = "1"
@@ -0,0 +1,15 @@
/system/chassis/motherboard/bmc/ethernet0:
xyz.openbmc_project.Inventory.Decorator.Replaceable:
FieldReplaceable: 'false'
xyz.openbmc_project.Inventory.Decorator.Cacheable:
Cached: 'true'
xyz.openbmc_project.Inventory.Item:
Present: 'true'
/system/chassis/motherboard/bmc/ethernet1:
xyz.openbmc_project.Inventory.Decorator.Replaceable:
FieldReplaceable: 'false'
xyz.openbmc_project.Inventory.Decorator.Cacheable:
Cached: 'true'
xyz.openbmc_project.Inventory.Item:
Present: 'true'
@@ -0,0 +1,20 @@
0:
/system/chassis/motherboard/bmc/ethernet0:
entityID: 6
entityInstance: 1
interfaces:
xyz.openbmc_project.Inventory.Item.NetworkInterface:
MACAddress:
IPMIFruProperty: Custom Field 2
IPMIFruSection: Board
xyz.openbmc_project.Inventory.Item.Ethernet:
/system/chassis/motherboard/bmc/ethernet1:
entityID: 6
entityInstance: 2
interfaces:
xyz.openbmc_project.Inventory.Item.NetworkInterface:
MACAddress:
IPMIFruProperty: Custom Field 3
IPMIFruSection: Board
xyz.openbmc_project.Inventory.Item.Ethernet:
@@ -0,0 +1,7 @@
FILESEXTRAPATHS:append := "${THISDIR}/${PN}:"
SRC_URI:append = " file://inventory.yaml"
do_install:append() {
install -D ${WORKDIR}/inventory.yaml ${D}${base_datadir}/events.d/inventory.yaml
}
@@ -0,0 +1,2 @@
SYSFS_PATH=/sys/bus/i2c/devices/25-0051/eeprom
FRUID=0
@@ -0,0 +1,27 @@
inherit obmc-phosphor-systemd
FILESEXTRAPATHS:prepend:genesis3 := "${THISDIR}/${PN}:"
DEPENDS:append:genesis3 = " genesis3-yaml-config"
EXTRA_OECONF:genesis3 = " \
YAML_GEN=${STAGING_DIR_HOST}${datadir}/genesis3-yaml-config/ipmi-fru-read.yaml \
PROP_YAML=${STAGING_DIR_HOST}${datadir}/genesis3-yaml-config/ipmi-extra-properties.yaml \
"
EEPROM_NAMES = "motherboard"
EEPROMFMT = "system/chassis/{0}"
EEPROM_ESCAPEDFMT = "system-chassis-{0}"
EEPROMS = "${@compose_list(d, 'EEPROMFMT', 'EEPROM_NAMES')}"
EEPROMS_ESCAPED = "${@compose_list(d, 'EEPROM_ESCAPEDFMT', 'EEPROM_NAMES')}"
ENVFMT = "obmc/eeproms/{0}"
SYSTEMD_ENVIRONMENT_FILE:${PN}:append:genesis3 := " ${@compose_list(d, 'ENVFMT', 'EEPROMS')}"
TMPL = "obmc-read-eeprom@.service"
TGT = "${SYSTEMD_DEFAULT_TARGET}"
INSTFMT = "obmc-read-eeprom@{0}.service"
FMT = "../${TMPL}:${TGT}.wants/${INSTFMT}"
SYSTEMD_LINK:${PN}:append:genesis3 := " ${@compose_list(d, 'FMT', 'EEPROMS_ESCAPED')}"
@@ -0,0 +1,19 @@
SUMMARY = "Phosphor LED Group Management for Romulus"
PR = "r1"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10"
inherit native
PROVIDES += "virtual/phosphor-led-manager-config-native"
SRC_URI += "file://led.yaml"
S = "${WORKDIR}"
# Overwrite the example led layout yaml file prior
# to building the phosphor-led-manager package
do_install() {
SRC=${S}
DEST=${D}${datadir}/phosphor-led-manager
install -D ${SRC}/led.yaml ${DEST}/led.yaml
}
@@ -0,0 +1,375 @@
bmc_booted:
power:
Action: 'On'
LED_ID_DWR_FRNT_P:
Action: 'Off'
LED_ID_DWR_BACK_P:
Action: 'Off'
power_on:
power:
Action: 'On'
led_id_dwr:
LED_ID_DWR_FRNT_P:
Action: 'On'
LED_ID_DWR_BACK_P:
Action: 'On'
led_pwr_dwr:
LED_PWR_DWR_FRNT:
Action: 'On'
LED_PWR_DWR_BACK:
Action: 'On'
led_id_cpu0:
LED_ID_CPU0:
Action: 'On'
led_id_cpu1:
LED_ID_CPU1:
Action: 'On'
led_id_cpu2:
LED_ID_CPU2:
Action: 'On'
led_id_cpu3:
LED_ID_CPU3:
Action: 'On'
led_rssd01_power:
rssd01_power_green:
Action: 'On'
led_rssd02_power:
rssd02_power_green:
Action: 'On'
led_rssd03_power:
rssd03_power_green:
Action: 'On'
led_rssd04_power:
rssd04_power_green:
Action: 'On'
led_rssd05_power:
rssd05_power_green:
Action: 'On'
led_rssd06_power:
rssd06_power_green:
Action: 'On'
led_rssd07_power:
rssd07_power_green:
Action: 'On'
led_rssd08_power:
rssd08_power_green:
Action: 'On'
led_rssd09_power:
rssd09_power_green:
Action: 'On'
led_rssd10_power:
rssd10_power_green:
Action: 'On'
led_rssd11_power:
rssd11_power_green:
Action: 'On'
led_rssd12_power:
rssd12_power_green:
Action: 'On'
led_rssd13_power:
rssd13_power_green:
Action: 'On'
led_rssd14_power:
rssd14_power_green:
Action: 'On'
led_rssd15_power:
rssd15_power_green:
Action: 'On'
led_rssd16_power:
rssd16_power_green:
Action: 'On'
led_rssd17_power:
rssd17_power_green:
Action: 'On'
led_rssd18_power:
rssd18_power_green:
Action: 'On'
led_rssd19_power:
rssd19_power_green:
Action: 'On'
led_rssd20_power:
rssd20_power_green:
Action: 'On'
led_rssd21_power:
rssd21_power_green:
Action: 'On'
led_rssd22_power:
rssd22_power_green:
Action: 'On'
led_rssd23_power:
rssd23_power_green:
Action: 'On'
led_rssd24_power:
rssd24_power_green:
Action: 'On'
led_rssd25_power:
rssd25_power_green:
Action: 'On'
led_rssd26_power:
rssd26_power_green:
Action: 'On'
led_rssd27_power:
rssd27_power_green:
Action: 'On'
led_rssd28_power:
rssd28_power_green:
Action: 'On'
led_rssd29_power:
rssd29_power_green:
Action: 'On'
led_rssd30_power:
rssd30_power_green:
Action: 'On'
led_rssd31_power:
rssd31_power_green:
Action: 'On'
led_rssd32_power:
rssd32_power_green :
Action: 'On'
led_m2_ssb_ssd1_power:
m2_ssb_ssd1_power_green:
Action: 'On'
led_m2_ssb_ssd2_power:
m2_ssb_ssd2_power_green:
Action: 'On'
led_id_dimm_a0:
LED_ID_DIMM_A0:
Action: 'On'
led_id_dimm_a1:
LED_ID_DIMM_A1:
Action: 'On'
led_id_dimm_b0:
LED_ID_DIMM_B0:
Action: 'On'
led_id_dimm_b1:
LED_ID_DIMM_B1:
Action: 'On'
led_id_dimm_c0:
LED_ID_DIMM_C0:
Action: 'On'
led_id_dimm_c1:
LED_ID_DIMM_C1:
Action: 'On'
led_id_dimm_d0:
LED_ID_DIMM_D0:
Action: 'On'
led_id_dimm_d1:
LED_ID_DIMM_D1:
Action: 'On'
led_id_dimm_e0:
LED_ID_DIMM_E0:
Action: 'On'
led_id_dimm_e1:
LED_ID_DIMM_E1:
Action: 'On'
led_id_dimm_f0:
LED_ID_DIMM_F0:
Action: 'On'
led_id_dimm_f1:
LED_ID_DIMM_F1:
Action: 'On'
led_id_dimm_g0:
LED_ID_DIMM_G0:
Action: 'On'
led_id_dimm_g1:
LED_ID_DIMM_G1:
Action: 'On'
led_id_dimm_h0:
LED_ID_DIMM_H0:
Action: 'On'
led_id_dimm_h1:
LED_ID_DIMM_H1:
Action: 'On'
led_id_dimm_j0:
LED_ID_DIMM_J0:
Action: 'On'
led_id_dimm_j1:
LED_ID_DIMM_J1:
Action: 'On'
led_id_dimm_k0:
LED_ID_DIMM_K0:
Action: 'On'
led_id_dimm_k1:
LED_ID_DIMM_K1:
Action: 'On'
led_id_dimm_l0:
LED_ID_DIMM_L0:
Action: 'On'
led_id_dimm_l1:
LED_ID_DIMM_L1:
Action: 'On'
led_id_dimm_m0:
LED_ID_DIMM_M0:
Action: 'On'
led_id_dimm_m1:
LED_ID_DIMM_M1:
Action: 'On'
led_id_dimm_n0:
LED_ID_DIMM_N0:
Action: 'On'
led_id_dimm_n1:
LED_ID_DIMM_N1:
Action: 'On'
led_id_dimm_p0:
LED_ID_DIMM_P0:
Action: 'On'
led_id_dimm_p1:
LED_ID_DIMM_P1:
Action: 'On'
led_id_dimm_q0:
LED_ID_DIMM_Q0:
Action: 'On'
led_id_dimm_q1:
LED_ID_DIMM_Q1:
Action: 'On'
led_id_dimm_r0:
LED_ID_DIMM_R0:
Action: 'On'
led_id_dimm_r1:
LED_ID_DIMM_R1:
Action: 'On'
led_id_dimm_s0:
LED_ID_DIMM_S0:
Action: 'On'
led_id_dimm_s1:
LED_ID_DIMM_S1:
Action: 'On'
led_id_dimm_t0:
LED_ID_DIMM_T0:
Action: 'On'
led_id_dimm_t1:
LED_ID_DIMM_T1:
Action: 'On'
led_id_dimm_u0:
LED_ID_DIMM_U0:
Action: 'On'
led_id_dimm_u1:
LED_ID_DIMM_U1:
Action: 'On'
led_id_dimm_v0:
LED_ID_DIMM_V0:
Action: 'On'
led_id_dimm_v1:
LED_ID_DIMM_V1:
Action: 'On'
led_id_dimm_w0:
LED_ID_DIMM_W0:
Action: 'On'
led_id_dimm_w1:
LED_ID_DIMM_W1:
Action: 'On'
led_id_dimm_x0:
LED_ID_DIMM_X0:
Action: 'On'
led_id_dimm_x1:
LED_ID_DIMM_X1:
Action: 'On'
led_id_dimm_y0:
LED_ID_DIMM_Y0:
Action: 'On'
led_id_dimm_y1:
LED_ID_DIMM_Y1:
Action: 'On'
led_id_dimm_z0:
LED_ID_DIMM_Z0:
Action: 'On'
led_id_dimm_z1:
LED_ID_DIMM_Z1:
Action: 'On'
led_id_rssd01:
LED_ID_RSSD01:
Action: 'On'
led_id_rssd02:
LED_ID_RSSD02:
Action: 'On'
led_id_rssd03:
LED_ID_RSSD03:
Action: 'On'
led_id_rssd04:
LED_ID_RSSD04:
Action: 'On'
led_id_rssd05:
LED_ID_RSSD05:
Action: 'On'
led_id_rssd06:
LED_ID_RSSD06:
Action: 'On'
led_id_rssd07:
LED_ID_RSSD07:
Action: 'On'
led_id_rssd08:
LED_ID_RSSD08:
Action: 'On'
led_id_rssd09:
LED_ID_RSSD09:
Action: 'On'
led_id_rssd10:
LED_ID_RSSD10:
Action: 'On'
led_id_rssd11:
LED_ID_RSSD11:
Action: 'On'
led_id_rssd12:
LED_ID_RSSD12:
Action: 'On'
led_id_rssd13:
LED_ID_RSSD13:
Action: 'On'
led_id_rssd14:
LED_ID_RSSD14:
Action: 'On'
led_id_rssd15:
LED_ID_RSSD15:
Action: 'On'
led_id_rssd16:
LED_ID_RSSD16:
Action: 'On'
led_id_rssd17:
LED_ID_RSSD17:
Action: 'On'
led_id_rssd18:
LED_ID_RSSD18:
Action: 'On'
led_id_rssd19:
LED_ID_RSSD19:
Action: 'On'
led_id_rssd20:
LED_ID_RSSD20:
Action: 'On'
led_id_rssd21:
LED_ID_RSSD21:
Action: 'On'
led_id_rssd22:
LED_ID_RSSD22:
Action: 'On'
led_id_rssd23:
LED_ID_RSSD23:
Action: 'On'
led_id_rssd24:
LED_ID_RSSD24:
Action: 'On'
led_id_rssd25:
LED_ID_RSSD25:
Action: 'On'
led_id_rssd26:
LED_ID_RSSD26:
Action: 'On'
led_id_rssd27:
LED_ID_RSSD27:
Action: 'On'
led_id_rssd28:
LED_ID_RSSD28:
Action: 'On'
led_id_rssd29:
LED_ID_RSSD29:
Action: 'On'
led_id_rssd30:
LED_ID_RSSD30:
Action: 'On'
led_id_rssd31:
LED_ID_RSSD31:
Action: 'On'
led_id_rssd32:
LED_ID_RSSD32:
Action: 'On'
@@ -0,0 +1,4 @@
{
"eth0":"ethernet0",
"eth1":"ethernet1"
}
@@ -0,0 +1,12 @@
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
PACKAGECONFIG:append = " sync-mac"
SRC_URI += " \
file://config.json \
"
FILES:${PN} += "${datadir}/network/*.json"
do_install:append() {
install -d ${D}${datadir}/network/
install -m 0644 ${WORKDIR}/config.json ${D}${datadir}/network/
}
@@ -0,0 +1,50 @@
RDEPENDS:${PN}-extras:append = " \
phosphor-software-manager \
phosphor-ipmi-flash \
phosphor-post-code-manager \
phosphor-host-postd \
phosphor-state-manager-chassis \
"
RDEPENDS:${PN}-devtools:append = " \
entity-manager \
webui-vue \
ldd \
ethtool \
net-tools \
lmsensors-sensors \
screen \
ipmitool \
"
PACKAGES += " \
${PN}-chassis \
${PN}-fans \
${PN}-system \
"
PROVIDES += " \
virtual/obmc-chassis-mgmt \
virtual/obmc-fan-mgmt \
virtual/obmc-system-mgmt \
"
RPROVIDES:${PN}-system += "virtual-obmc-system-mgmt"
RPROVIDES:${PN}-fans += "virtual-obmc-fan-mgmt"
RPROVIDES:${PN}-chassis += "virtual-obmc-chassis-mgmt"
SUMMARY:${PN}-chassis = "IBM Chassis"
RDEPENDS:${PN}-chassis += " \
phosphor-post-code-manager \
phosphor-host-postd \
phosphor-state-manager-chassis \
"
SUMMARY:${PN}-flash = "IBM Flash"
RDEPENDS:${PN}-flash = " \
phosphor-software-manager \
phosphor-ipmi-flash \
"
SUMMARY:${PN}-fans = "IBM Fans"
RDEPENDS:${PN}-fans = " \
phosphor-pid-control \
"