| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Latest bitbake gives a QA warning for "lack of whitespace around the
assignment". Clean these up.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iff0618dacb6afcece814b2b307fef5fc82bc1324
|
|
Yocto rebase build reports QA Issue: Missing Upstream-Status in patch
Added simple fix by amending patch commit message "Upstream-Status: Pending"
now to unblock rebase.
Change-Id: I753c2c7faa4dcede7dd2b5e6eaba79580ce5e2a1
Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
|
|
The upstream meta-security added a new package to the tpm2
packagegroup, which introduced a dependency on python3. This
package isn't necessary so we can remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I53344425a3893c17d62ddd5687dd84ee112ee707
|
|
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>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id89782274717a4fdcabb10df19510cbd05571ec1
|
|
The previous 'dynamic-layers' content has been fixed so that it is
functional on both aspeed and nuvoton (and likely any system that
exposes the same sysfs class entries). Promote this content out
of dynamic-layers and make it common to reduce the hardware-specific
duplication.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8f8247098ef8f8b035269815ebe77dedb2e8a441
|
|
In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.
This commit runs oe-stylize.py on all of our files. The types of
changes being made can be seen in the commit, but amount to:
1. Setting an explicit key ordering
2. Sectioning the files appropriately
3. Applying rules checking to our files
At some point in the near future, we would turn this on as part of
repotest, but some minor changes need to be upstreamed to meta-oe (WIP)
to make that happen.
Looking for input on whether this is something we'd like to do, and
whether the diffs below look reasonable to folks.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf
|
|
The LICENSE string 'GPLv2+' is considered obsolete by Yocto and raises a
warning. Switch them too the accepted tag 'GPL-2.0-or-later'.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I88c639dbb45762e2e019a3503f1f1930b65c09d6
|
|
We don't need pkcs11 support on the BMC by default and it ends up
causing a dependency chain that brings in Rust.
This packagegroup can only be pulled in when meta-security/meta-tpm is
used, so hook into BBFILES_DYNAMIC to use it when appropriate.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iff12f641e57ace313ad64a402091444edba74ea4
|
|
The proper way to add extensions to another layer is with
BBFILES_DYNAMIC rather than adding to BBFILES based on
BBFILE_COLLECTIONS. Move nuvoton-layer to a dynamic-layers subdirectory
and hook into layer.conf using BBFILES_DYNAMIC.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic1b1f0ce837a899c5060531735c75c73cf51f1f5
|
|
The proper way to add extensions to another layer is with
BBFILES_DYNAMIC rather than adding to BBFILES based on
BBFILE_COLLECTIONS. Move aspeed-layer to a dynamic-layers subdirectory
and hook into layer.conf using BBFILES_DYNAMIC.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I26e5093d469ce0a57c0b93bcc6b3383dd7bcf264
|
