All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Any ideas about mechanism of updating software/firmware?
Date: Mon, 27 Apr 2015 14:35:53 +0800	[thread overview]
Message-ID: <553DD8C9.1040602@gmail.com> (raw)

Hi Community,

I am new to Buildroot. I am developing a commercial product based on 
Buildroot 2014.02, and I need the mechanism to update software/firmware 
of the product.

Here are some of my thought:
1) In eMMC, there is a partition which can be exported to PC via USB 
mass storage.
2( Once u-boot detects a special key-combination or new file in 
above-mentioned eMMC partition, u-boot boots a special kernel with 
initramfs.
3) In above-mentioned kernel + initramfs, it compares version buildroot 
distribution kernel (/etc/issue) and version+build number embedded in 
the filename of in the partition above.
3.1) If a new version is found, it updates u-boot / kernel / rootfs.

Is it a good practice to update 'system/skeleton/etc/issue' when a new 
version will be 'git tag'ed and built?

Thanks.

-- 
Xuebing

             reply	other threads:[~2015-04-27  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  6:35 Xuebing Wang [this message]
2015-04-27 15:24 ` [Buildroot] Any ideas about mechanism of updating software/firmware? Vivien Didelot

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=553DD8C9.1040602@gmail.com \
    --to=xbing6@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.