| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The ordering of the values in MACHINEOVERRIDES is wrong:
MACHINEOVERRIDES="witherspoon-128:witherspoon"
This means that:
FOO_witherspoon = "bar"
will override:
FOO_witherspoon-128 = "baz"
which is the opposite of expectation. The ordering is a function of
config file include order and choice of the predot vs postdot operator.
Use the same include ordering and dot operators as meta-fsl-arm to get
the overrides to appear in MACHINEOVERRIDES in the correct order such
that the expected semantics are provided and:
FOO_witherspoon-128 = "bar"
will override:
FOO_witherspoon = "baz"
(From meta-ibm rev: a12ff8392546591d8b52927da983dd76d2c0f1bd)
Change-Id: I823e236bd0147cc058052d85778b522e74fabb28
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Replace "witherspoon-128" with ${MACHINE} for the device tree file name
as it's better practice to use bitbake variables instead of hard-coding
values.
Tested:
Output of "bitbake obmc-phosphor-image -e":
# pre-expansion value:
# "${KMACHINE}-bmc-opp-${MACHINE}.dtb"
KERNEL_DEVICETREE="aspeed-bmc-opp-witherspoon-128.dtb"
(From meta-ibm rev: 8bbd213225ea5d6e3d1eb8537308f398dc85b6a2)
Change-Id: I46e72947ddf47d3cbc20ab04f2b949ee717423cf
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The witherspoon and witherspoon-128 machines are mostly the same.
Add "witherspoon" as a MACHINEOVERRIDES to witherspoon-128 so that
machine-specific features that apply only to witherspoon, including
file paths, can be added to both flavors of witherspoon automatically.
Tested: Built witherspoon and witherspoon-128, flashed images on
HW and verified witherspoon powered on.
(From meta-ibm rev: 6f44bb26247289aa46c6d21f04617838e596294a)
Change-Id: I18ce6dd799cb0ab52b37f1f1f3d64c6189af4cd8
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create a machine/witherspoon-128.conf file to model a witherspoon
system with 128MB flash chips.
* New kernel device tree (witherspoon-128.dts).
* Bigger read-write filesystem. Remove the default from the
witherspoon layer (not needed as 6MB is the default) so that the
size value can be overwritten by the witherspoon-128.conf.
- To build this machine:
export MACHINE="witherspoon-128"; \
export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE"; \
bitbake obmc-phosphor-image
Witherspoon-128 is a system based on Witherspoon but with 128MB
flash chips. Create a device tree for this configuration.
Since this system is just a bringup vehicle, the device tree will
be carried as a patch instead of merging it in upstream linux.
(From meta-ibm rev: 903fd3532aaa967ddc7124095304f50cd4c9557c)
Change-Id: If02e8ad32fc2bff336d16c18513f2c238b28c28a
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
