Açıklama Yok

Jan Vermaete e67f35c949 Fix for Yocto deprecation issue on MIT license file. 7 yıl önce
classes 5a169fbaa5 use sstate staging to copy update image to deploy directory 8 yıl önce
conf 5be64aebb2 layer.conf: do not force early expansion of BBFILES 7 yıl önce
recipes-bsp 36075a1136 u-boot-fw-utils: fix build with 2017.05 8 yıl önce
recipes-core e67f35c949 Fix for Yocto deprecation issue on MIT license file. 7 yıl önce
recipes-devtools e4b0fb27e4 Updated to mtd-utils 2.x 8 yıl önce
recipes-extended 65fb4cfe45 Fix 'swuupdate' typo in swupdate-image.bb 8 yıl önce
recipes-support a2edc174cf SWUpdate: Added recipe for 2018.03 7 yıl önce
COPYING.MIT 020c327419 Receipes to generate a swupdate image 12 yıl önce
README 0fb115e971 typo fixes 8 yıl önce

README

meta-swupdate, Yocto layer for deploy tool
==========================================

This layer's purpose is to add support for a deployment
mechanism of Yocto's images based on swupdate project.

Layer dependencies
------------------

This layer depends on:

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe

Image hashing
-------------

During creation of the update file, occurrences of @IMAGE (where IMAGE is an
image filename) are replaced with the sha256 hash of the image.

SWU image signing
------------

There are 3 signing mechanisms supported by meta-swupdate at the moment:

1. RSA signing:

* Set variable: `SWUPDATE_SIGNING = "RSA"`

* Set `SWUPDATE_PRIVATE_KEY` to the full path of private key file

2. CMS signing:

* Set variable: `SWUPDATE_SIGNING = "CMS"`

* Set `SWUPDATE_CMS_CERT` to the full path of certificate file

* Set `SWUPDATE_CMS_KEY ` to the full path of private key file

3. Custom signing tool:

* Set variable: `SWUPDATE_SIGNING = "CUSTOM"`

* Set variable `SWUPDATE_SIGN_TOOL' to custom string that needs to be
executed in order to perform the signing

sw-description is signed and the signature is written to sw-description.sig
which is included in the SWU file.

Encrypted private keys are not currently supported since a secure
mechanism must exist to provide the passphrase.

Maintainer
----------

Stefano Babic

Submitting patches
------------------

You can submit your patches (or post questions reagarding
this layer to the swupdate Mailing List:

swupdate@googlegroups.com

When creating patches, please use something like:

git format-patch -s --subject-prefix='meta-swupdate][PATCH'

Please use 'git send-email' to send the generated patches to the ML
to bypass changes from your mailer.