mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [RFC, PATCH] barebox-update command support
Date: Fri, 14 Sep 2012 09:45:10 +0200	[thread overview]
Message-ID: <1347608713-10133-1-git-send-email-s.hauer@pengutronix.de> (raw)

Hi All,

The following adds barebox-update command support. This command is
supposed to provide a dedicated command for updating barebox.

The rationale behind this is:

- We can add additional generic, SoC specific, board specific sanity
  checks (Is this really a barebox image? Does the image fit into the
  device?)
- Sometimes SoC or board specific fixups are necessary. For example,
  with Omap Nand boot we have to switch the Nand driver into a different
  ECC mode before flashing barebox. With i.MX MMC card boot we want
  to preserve the partition table. On i.MX28 Nand boot we have to create
  a Boot Control Block. The list does not end here...

The current idea is:

A board can register one or multiple update handlers. The update handlers
themselves are registered by a board because only the board knows where
it actually can boot from. Nevertheless there might be generic handlers
available, the most simple one being: Check image header, check size, write
to device.

This is in an early state, right now there are only dummy handlers, hence the
RFC state.

Sascha

----------------------------------------------------------------
Sascha Hauer (3):
      Add barebox update infrastructure
      ARM: Add dummy update handler
      ARM pcm038: register nor update handler

 arch/arm/boards/pcm038/pcm038.c |    7 +++
 arch/arm/lib/Makefile           |    1 +
 arch/arm/lib/bbu.c              |   56 ++++++++++++++++++++
 commands/Kconfig                |    5 ++
 commands/Makefile               |    1 +
 commands/barebox-update.c       |   80 ++++++++++++++++++++++++++++
 common/Kconfig                  |    3 ++
 common/Makefile                 |    1 +
 common/bbu.c                    |  110 +++++++++++++++++++++++++++++++++++++++
 include/bbu.h                   |   40 ++++++++++++++
 10 files changed, 304 insertions(+)
 create mode 100644 arch/arm/lib/bbu.c
 create mode 100644 commands/barebox-update.c
 create mode 100644 common/bbu.c
 create mode 100644 include/bbu.h

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-09-14  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  7:45 Sascha Hauer [this message]
2012-09-14  7:45 ` [PATCH 1/3] Add barebox update infrastructure Sascha Hauer
2012-09-14 12:15   ` Jan Weitzel
2012-09-15 12:28     ` Sascha Hauer
2012-09-14  7:45 ` [PATCH 2/3] ARM: Add dummy update handler Sascha Hauer
2012-09-14 12:17   ` Jan Weitzel
2012-09-14  7:45 ` [PATCH 3/3] ARM pcm038: register nor " Sascha Hauer
2012-09-14 12:36 ` [RFC, PATCH] barebox-update command support Jan Weitzel
2012-09-15 12:33   ` Sascha Hauer

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=1347608713-10133-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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