Sen descrición

Cedric Hombourger e3c05e4c9d layer.conf: do not force early expansion of BBFILES %!s(int64=7) %!d(string=hai) anos
classes 81cd6f7e54 use sstate staging to copy update image to deploy directory %!s(int64=8) %!d(string=hai) anos
conf e3c05e4c9d layer.conf: do not force early expansion of BBFILES %!s(int64=7) %!d(string=hai) anos
recipes-bsp 5a97be4e1d u-boot-fw-utils: fixes for 2017.01 %!s(int64=8) %!d(string=hai) anos
recipes-core 3d4c926a82 Added tiny init %!s(int64=10) %!d(string=hai) anos
recipes-devtools e4b0fb27e4 Updated to mtd-utils 2.x %!s(int64=8) %!d(string=hai) anos
recipes-extended 345be2fc18 swupdate-image: remove image_types_uboot image class %!s(int64=8) %!d(string=hai) anos
recipes-support 0c7dc974e7 Fix build without network %!s(int64=8) %!d(string=hai) anos
COPYING.MIT 020c327419 Receipes to generate a swupdate image %!s(int64=12) %!d(string=hai) anos
README d71b76955f typo fixes %!s(int64=8) %!d(string=hai) anos

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.