Age | Commit message (Collapse) | Author | Files | Lines |
|
FLASH_SIZE was previously defaulted in a few bbclasses and bbappends,
but this can result in it not being defined in all recipes if the
machine has not overridden the FLASH_SIZE. openbmc/openbmc#3876
reported one such case where the u-boot-fw-utils recipe does not
receive the correct FLASH_SIZE and ends up erasing the wrong flash
region as if it were the u-boot enviroment. Specify it in the common
include so it is available everywhere.
Resolves openbmc/openbmc#3876.
Change-Id: Iacdde1a5d0081b54321110d655da18bb3846cd14
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
The script was comparing string with `==` that works in bash but not in
`dash`.
Change it to `=` so that it is more POSIX compliant.
Tested: Verify the build passes with SIGNING_PUBLIC_KEY defined with
both `bash` and `dash`.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Id825cd111adeae5b1e50ea4f25603728cc122375
|
|
For NO TIP mode there is no need for signatures at all.
Expected result:
| TIP_IMAGE = True | TIP_IMAGE = False
| |
SECURED_IMAGE = True | Need sign | No need sign
| |
SECURED_IMAGE = False | No need sign | No need sign
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Ia48960732f9090f46f1944ee6bd51c1f0b121abe
|
|
The switch enables AF_MCTP and adds the `mctp` tool and `mctpd` so we
can setup and manage an in-kernel MCTP network.
Enable it for p10bmc and also add CONFIG_TUN so we can use a tun device
to transport packets between the kernel and the astlpc interface
implemented in libmctp.
Change-Id: I21d0af9e751f91975c760b4b4708b3b401b95417
Signed-off-by: Rashmica Gupta <rashmica@linux.ibm.com>
|
|
Add sign images feature according customer's requirement.
Set "SECURED_IMAGE" to "True" and enable sign images feature.
When sign images feature be enabled. Use default keys to sign
images if customer didn't point their own local keys path.
Note: "SECURED_IMAGE" default is "True".
Tested:
Use default keys sign:
That will use default path and keys from igps to sign.
Use local keys sign:
That will use local path and keys to sign.
When KEY_FOLDER and KEY definition both are valid.
However, when KEY_FOLDER and KEY definition are invalid either,
that will output sign images failed then stop build full images.
Tested: build pass and boot up successfully with signed
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: If2b793906ab338aec391062d9bfeae2b1e790078
|
|
The 32MB images (AST2400/AST2500) need more space than I originally
left for holding the U-Boot binary. Reduce the manifest on those
systems to 4KB instead of 8KB in order to leave enough space for
U-Boot.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I980f2989782577bab4e2560dfb70a1f5fcbf018b
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5cd3cf7cbec87b32ee07f08cae27b534c3cf7bd2
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id89782274717a4fdcabb10df19510cbd05571ec1
|
|
Support SIGNING_PUBLIC_KEY so that it generates an unsigned tarball.
Such tarball will be signed by separate tools as needed.
Tested:
* Do not define both SIGNING_KEY and SIGNING_PUBLIC_KEY, it generates
the tarball as before with the dev key.
* Define SIGNING_PUBLIC_KEY and do not define SIGNING_KEY, it generates
tarballs without signature.
* Define SIGNING_KEY and do not define SIGNING_PUBLIC_KEY, it generates
the tarball signed with the SIGNING_KEY.
* Define both SIGNING_KEY and SIGNING_PUBLIC_KEY, it gets error on
building phosphor-image-signing recipe.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: If6cffc477c1aa76674af758e0154b21b7b88c099
|
|
It is desirable to have a single image for both manufacturing and
updates instead of the separate MTD and tarball. Define a JSON
format and populate it, based on a combination of the current MANIFEST
data and learnings from the Meta verified-boot metadata format[1,2].
This JSON file is then embedded into the image itself, so that update
tools can determine the compatibility and correctness of the image
before applying.
An example manifest JSON can be found at [3].
[1]: https://github.com/facebook/openbmc/blob/eda9e95e2d94feaa2749f2a8e97e237bfe7b38e3/tools/flashy/lib/validate/partition/p_fbmeta.go
[2]: https://github.com/facebook/openbmc/blob/eda9e95e2d94feaa2749f2a8e97e237bfe7b38e3/meta-facebook/classes/fbobmc-image.bbclass#L200
[3]: https://gist.github.com/williamspatrick/9bd5e39909df2a3cad4894dc926d5c1c
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iff0b7a37194297d49ca4f3d6077d5995452d7c72
|
|
The previous static-image building code only confirmed that the
u-boot image was smaller than the offset for the kernel image, but
most systems place the u-boot environment after the u-boot image.
It is possible that we have a u-boot image bigger than the u-boot
partition, which is then overwritten on boot by the u-boot env.
Check for this at image build time and prevent it from happening.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3a1e6654272cedb3e840bbea4771ae4e464c4ecd
|
|
The configparser library has deprecated the `readfp` function since
Python 3.2. I observed that the `log.do_generate_phosphor_manifest`
had the following warning:
```
meta-phosphor/classes/image_version.bbclass:17: DeprecationWarning: This method will be removed in Python 3.12. Use 'parser.read_file()' instead.
```
The `read_file` is an identical replacement for `readfp` and has been
present since Python 3.2.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifd2f6ca5b1ff46bb351a024186515da28f13304d
|
|
Most repositories now put their dbus and phosphor-logging YAML into
a `yaml` subdirectory. Enhance the bbclass to support either in the
root or in the `yaml` subdirectory.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I30a104088d4ac9696e9072b33ec8e91c4a718f10
|
|
When the image generation fails due to file size, print out the amount
by which the input file overflows the available size.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I866f97994688671c247b9fe05c59b30b3d6eebd7
|
|
Define a new image type 'static-norootfs' that takes the entire
rootfs and places it as the initramfs for the kernel's FIT image,
so that the BMC is entirely running from a ramdisk.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0163f5be0a1b176e0db5f89b85f34e4feae8a588
|
|
Extract relevant functions from upstream's kernel-fitimage.bbclass
in order to be able to create a FIT image containing the rootfs
as the initramfs. This will let us generate MTD images with a single
rootfs-as-initramfs.
My intention is to ensure this is working in meta-phosphor and then
work at moving the bbclass upstream.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9b996f32be718a69da863aa2f14a8fe8278c84f9
|
|
Lakshmi Yadlapati (1):
u-boot mirroring support
moni kumar (1):
Removed reset of the interface ActivationProgress
Change-Id: Ia817b6af5e0b2ef3312e5b05c05ca0a38d4f39de
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
|
|
Patrick Williams (3):
linter: disable python2 scripts
prettier: re-format
black: re-format
Change-Id: Id9cec191bd488dfc93ab9abb50dff6803b5365a1
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Before do_pad_binary be exectued, those binaries need to be ready for
padding. Otherwise there are errors about "No such file or directory"
for those binaries.
Tested: build pass and boot up successfully
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I602ad0fdd95f207978b7dd2ed492ff7ef40573fb
|
|
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I9bfe4ed6065c7f031bfd2bedc2c6eaedc7a5ee62
|
|
Tested: buid pass and boot up successful when loading BB at 0x80000 for example
Verified by bootblock log as below:
==========
Load bootblock
==========
tip_firmware_image_init fiu0 cs0 BOOTBLOCK
tag U. scan from 0x80000000 to 0x88000000
tip_firmware_image_scan_flash BOOTBLOCK found addr 0x80080000 dst 0xfffd0000
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I62eced6d80b48d488348d43468f8f01edf83d79a
|
|
Adriana Kobylak (1):
OWNERS: update
Change-Id: Iddd600111f0ee5f719266f8429f1c0c20075d039
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I580a38f66d4c6185dae803c70fd050eeae3d1437
|
|
Brad Bishop (1):
OWNERS: update
Change-Id: I6e69290af5814d86def2c4838421905fc32003d5
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Big cleanups to the phosphor-mapper/phosphor-objmgr recipe.
- Remove all "mapper-config-native" constructs as the underlying
repository has no such support.
- Remove all mapper-related bbclasses as they are no longer relevant.
- Remove environment support in service file as the mapper executable
no longer supports any arguments.
- Greatly simplify the 'libmapper' packaging to avoid stray python
in the recipe.
- Update all recipes to use `DEPENDS += "libmapper"` where appropriate
for clarity if they use libmapper.
- Rename the recipe from phosphor-mapper to phosphor-objmgr to match
the repository name, which allows simpler devtool invocations.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5a64e2feddd1a7919813e007411f9c28b6c9a330
|
|
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I2d1ed130d2db71ba0ae4446a9380d7c9e8ad95fd
|
|
Nuvoton's npcm8xx full flash image includes TIP FW, Bootblock,
ATF, OPTEE and UBOOT with headers. Generating headers and merging
images are being done by Nuvoton's binary generator tool (Bingo)
which uses external parameters from XML files for that.
Thus, we need to add related fitimage and image type for npcm8xx.
However, before merge this commit, we must wait for below commits were merged.
meta-nuvoton: arm-trusted-firmware: add arm trusted firmware recipe
https://gerrit.openbmc.org/c/openbmc/openbmc/+/55234
meta-nuvoton: add npcm8xx-bootblock recipe
https://gerrit.openbmc.org/c/openbmc/openbmc/+/55117
meta-nuvoton: add npcm8xx-igps recipe
https://gerrit.openbmc.org/c/openbmc/openbmc/+/55099
meta-nuvoton: npcm7xx-bingo: upgrade latest version 0.0.5 support Arbel
https://gerrit.openbmc.org/c/openbmc/openbmc/+/55128
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I4599e39d3873f07cde6904d0f10161964fc45c7a
|
|
Patrick Williams (1):
MAINTAINERS: remove file
Change-Id: If77b163abb0fcba66bb9746d3c63135389c1a099
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
The EXTENDED_VERSION in the os-release file was an optional field.
Initialize it to a default since there will be a Redfish property for
extended version information that can be mapped to the ExtendedVersion
D-Bus property, choose the VERSION_ID value as the default since that's
what's used for the Version D-Bus property, and set it to a weak
variable so it can still be overwritten.
Need a new function to get the EXTENDED_VERSION from the os-release file
instead of just from a bitbake variable. It is still possible to
overwrite the default value in a conf or bbappend file, same as
BUILD_ID.
Note that the extended version was and still is surrounded by quotes,
since this is a free-format string that may contain spaces.
Tested:
- Verified the extended version string was the same as version in:
- os-release:
VERSION_ID=2.13.0-dev-613-g1e16157845
EXTENDED_VERSION="2.13.0-dev-613-g1e16157845"
- MANIFEST:
version=2.13.0-dev-613-g1e16157845
ExtendedVersion="2.13.0-dev-613-g1e16157845"
- D-Bus properties:
.ExtendedVersion property s "2.13.0-dev-613-g1e16157845"
.Version property s "2.13.0-dev-613-g1e16157845"
- Verified that extended version could be set from a conf file, example:
in meta-ibm/conf/machine/witherspoon.conf:
EXTENDED_VERSION = "My Extended Version"
- Verified that extended version could be set from a bbappend, example:
in meta-ibm/recipes-core/os-release/os-release.bbappend:
EXTENDED_VERSION:witherspoon = "My_Extended_Version_from_bbappend"
Change-Id: I74adf08239c9cd08768be9c5d9cd3384e703da95
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The logic to get an os-release value was duplicated. Move this logic to
a single function to remove the duplication. This can also help to avoid
further duplication if additional values need to be parsed.
Tested: Verified the contents of the MANIFEST file were the same after
this change.
Change-Id: Iacdb2c7e644103d76b73f32b15a089d352f40001
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Patrick Williams (2):
python: reformat using black
OWNERS: switch 'matches' to 'matchers'
Change-Id: Ic9d38c92c0bed8ad093ad6235e0433ebcfbc7f3f
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
geissonator
ensure no space in script type string
utilize "/usr/bin/env perl" in perl scripts
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib32a3aa374a3d5e7661ec0a815bebdfe1104a2da
|
|
Previously when u-boot code was changed inside a devtool modify repo, the
u-boot artifacts were updated but they could not be picked up by the
final image-bmc. The reason was that the sstate version of u-boot was
used because the dependency between u-boot and obmc-phosphor-image was
not set up properly.
Fix the issue by adding the proper inter-task dependency between the
two.
Tested:
The image-bmc md5sum changes as expected when u-boot code is changed.
Change-Id: Ic98d3097f66e351c774ced4ee435149b5441cf67
Signed-off-by: Yong Zhao <yozhao@google.com>
|
|
This adds CompatibleNames field to the manifest file which can contain
compatibility strings as described in the Software interface.
The field is set by the OBMC_COMPATIBLE_NAMES variable in the
machine.conf file, e.g.
OBMC_COMPATIBLE_NAMES = "\
foo.bar \
baz.bim \
"
Also omit ExtendedVersion from the manifest file if it is not set.
Signed-off-by: Justin Ledford <justinledford@google.com>
Change-Id: Id27b4d6ec25ec7c3d3d5942368f40e618535eafe
|
|
Per [1], Yocto is going to start requiring both branch names and
`protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to
automatically fix our URIs.
1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
|
|
Some products have requirements for the source license info to
be made available to users. This adds a bbclass that copies
the license info stored in /usr/share/common-licenses to
/usr/share/www/common-licenses. From there it is served to
users by bmcweb in the existing webassets.hpp functionality.
File paths will show users the file content, but directories will
only display content in an index.* file. So, the bbclass also
creates an index.json for each directory so that directory paths
will show users the directory contents.
Tested:
Navigated to /common-licenses and common-licenses/ and confirmed
that the directory listing was displayed.
Navigated to /common-licenses/bmcweb and common-licenses/bmcweb/
and confirmed that the directory listing was displayed.
Navigated to /common-licenses/bmcweb/LICENSE and confirmed that
the license text was displayed.
Navigated to /common-licenses/../../network/config.json and
it returned "Not Found".
Navigated to /common-licenses/../ipmi-providers/channel_access.json
and it returned "Not Found".
Change-Id: I286b0cf53a9520087b1a57b17ea66f408f08ed3b
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
|
|
It was reported that after 5a5f33c729e6b5869362172b63595422eb84a418 the
qemu images are not buildable. Treat qemu systems like an 'evb' so that
the obmc-system-mgmt package is not included. Make a minor change to
how evb is specified so that it is treated as a MACHINEOVERRIDE that can
be leveraged in multiple recipes.
Tested by ensuring that `evb-ast2600` still successfully resolves all
package dependencies (with `bitbake -p`).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iff4573aa3d4aac30a6681ed75741a6e351bda982
|
|
Add the BUILD_ID value to the MANIFEST so that it can be used alongside
the VERSION value to generate a version id during firmware updates.
Add a function to read BUILD_ID from the os-release file instead of
reading it from a variable because the BUILD_ID value could be set via a
os_release.bbappend file instead of a .conf file.
Tested: Verified the BUILD_ID value was added to the MANIFEST by
default, and when BUILD_ID was specified in a .conf file, and on a
os-release.bbappend. Ex:
$ cat MANIFEST
purpose=xyz.openbmc_project.Software.Version.VersionPurpose.BMC
version=2.11.0-dev-566-g263df7f852
BuildId=20211025151654
ExtendedVersion=
KeyType=OpenBMC
HashType=RSA-SHA256
MachineName=p10bmc
Change-Id: I3b7beaccbbd47d8820d499180ccdf021b004cf85
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
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>
|
|
Manojkiran Eda (1):
Add OWNERS file
Change-Id: I7baeec6ca85478efeee3ee8ef80536527abc6890
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
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 logic was broken due to lack of quotes around the semicolon
delimiters inside subshell commands. It did not work for single keys nor
multiple keys provided in SSH_KEYS.
This commit adds proper quotes, and also refactors the loop a bit to
reduce repeated commands, reduce indentation, and clarify variables.
Tested:
- Added INHERIT/SSH_KEYS to local.conf as described in script comments.
- Tested with 1 key: "root:/path/to/key.pub" and 2 keys
"root:/path/to/key.pub;root:/path/to/key2.pub".
- Verified that in all cases keys were added to authorized_keys files
exactly once by checking rootfs output:
(build/tmp/work/<machine>/<image>/<version>/rootfs/home/root/.ssh/authorized_keys)
Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
Change-Id: I58af4e8107daa6447b8276a66fc7c91e346c7dd5
|
|
As a follow up to 400d9dab03e25d992429f94296caa4938c281fbd, fix the
deprecated SafeConfigParser to ConfigParser across the tree.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iabf941889eed97a996b739d77c8107f1f35ce5bf
|
|
There is a warning message in the obmc-phosphor-systemd.bbclass file
when using bitbake to build image-bmc:
```
DeprecationWarning: The SafeConfigParser class has been renamed to
ConfigParser in Python 3.2. This alias will be removed in future
versions. Use ConfigParser directly instead.
parser = configparser.SafeConfigParser(strict=False)
```
Use the class name `ConfigParser` directly in the configparser module.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I6168d9d1100ac846cc31be837a20b7dedb6d7910
|
|
Move static dbus config directory to be `/usr/share` instead of `/etc`,
which is recommended by `dbus-daemon`.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifd210a262e1c8025dc9e3037c9970ec66ebb085b
|
|
In the spirit of consistency with the new upstream override
syntax, change phosphor-discovery-service.bbclass to use it
and make tree-wide changes as appropriate.
After the change checked on Witherspoon on QEMU:
```
root@witherspoon:/etc/avahi/services# ls
obmc_console.service obmc_redfish.service obmc_rest.service
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib1fe3cce57a0130378af789abd83b457e0c3a318
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
It was observed that we have different approaches to modifying the
EXTRA_OEMESON variable across our recipes. The bitbake manual
implies that override syntax (":append") is slightly better and the
poky meson bbclass also prefers it:
meta/classes/meson.bbclass:EXTRA_OEMESON:append = " ${PACKAGECONFIG_CONFARGS}"
Switch all recipes to use the ":append" override syntax for the
EXTRA_OEMESON variable.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I24e9a27a87c61f374acfb03a63955821fce0dd20
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Add an addition override for 64MiB static flash layout.
The existing 32MiB layout are unchanged:
partition: size: offset
u-boot: 384 KiB (0 KiB)
u-boot-env: 128 KiB (384 KiB)
kernel/FIT: 4352 KiB (512 KiB)
rootfs: 23808 KiB (4864 KiB)
rwfs: 4MiB (28672 KiB)
The existing 128MiB layout are unchanged:
partition: size: offset
u-boot: 896 KiB (0 KiB)
u-boot-env: 128 KiB (896 KiB)
kernel/FIT: 9 MiB (1 MiB)
rootfs: 86 MiB (10 MiB)
rwfs: 32MiB (96 MiB)
The new layout for 64MiB is as follows:
partition: size: offset
u-boot: 896 KiB (0 KiB)
u-boot-env: 128 KiB (896 KiB)
kernel/FIT: 9 MiB (1 MiB)
rootfs: 32 MiB (10 MiB)
rwfs: 22 MiB (42 MiB)
Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
Change-Id: I001cf2e9bc30edc34e43c0c4503684050e2a764f
|