Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 1/1] package/swupdate: new package
Date: Sat, 03 Oct 2015 17:07:52 +0200	[thread overview]
Message-ID: <871tdc56t3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1438375543-28208-1-git-send-email-joerg.krause@embedded.rocks> ("Jörg Krause"'s message of "Fri, 31 Jul 2015 22:45:43 +0200")

>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:

 > swupdate provides a reliable way to update the software on an embedded system.
 > Note that swupdates has a reworked Kbuild/Kconfig system. It has now support
 > for the 'option' and 'env' symbols as well for the 'savedefconfig' target.
 > This makes dependency handling much easier. We're now able to pass which
 > dependencies are available through the environment, as suggested by Arnout
 > Vandecappelle [1].

 > In previous version of this patch we had a configuration setting where all
 > package dependencies except Lua were selected by default. This has changed with
 > v7 as we are now able to pass dependencies to the swupdate build system through
 > the environment. For useful operation swupdate requires a parser which depends
 > by default on libconfig, but can be replaced by a json-c or Lua parser.

 > To provide a reasonable firmware update system we enable the embedded webserver
 > based on mongoose (also see notes about mongoose below), a parser as stated
 > above and a handler for raw NAND or NOR flash.

 > The user can modify this configuration by selecting the appropriate dependencies
 > before running `make swupdate-menuconfig`. The help text contains information
 > about which packages may be of interest for the user.

 > The embedded web server requires a website for proper operation. We install the
 > included website by default, however the user may choose to install a custom
 > website on the post-build scripts.

 > Note, swupdate includes some old versions of mongoose and lsqlite3:
 >   - mongoose is version 3.8 from year 2013
 >   - lsqlite3 is version 0.8 from year 2011

 > Currently, swupdate does not provide a way to replace these with external
 > packages.

 > This patch is based on a WIP version submitted by Romain Naour, commented by
 > Arnout Vandecappelle [2].

 > [1]
 > http://lists.busybox.net/pipermail/buildroot/2015-March/122981.html

 > [2]
 > https://patchwork.ozlabs.org/patch/401270/

 > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
 > Cc: Romain Naour <romain.naour@openwide.fr>
 > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 > Cc: Arnout Vandecappelle <arnout@mind.be>
 > Cc: Yann E. MORIN <yann.morin.1998@free.fr>
 > Tested-by: Mike Williams <mike@mikebwilliams.com>
 > ---
 > Changes v7 -> v8:
 > [Romain Naour:
 >   - bump to release 2015.07
 >   - add target (MMU) and toolchain (THREAD) dependencies]
 >   - rewrite commit log

Committed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2015-10-03 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 20:45 [Buildroot] [PATCH v8 1/1] package/swupdate: new package Jörg Krause
2015-07-31 21:58 ` Romain Naour
2015-08-01  6:40   ` Jörg Krause
2015-10-03 15:07 ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871tdc56t3.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox