From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Firmware update for Buildroot
Date: Mon, 20 Oct 2014 16:30:51 +0200 [thread overview]
Message-ID: <20141020163051.1f4b05eb@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VnM21MSTZ0HnWM_u+uSgLSzUj1=PhYfOFTfn6H7aMK_oQ@mail.gmail.com>
Dear Angelo Compagnucci,
On Mon, 20 Oct 2014 15:17:06 +0200, Angelo Compagnucci wrote:
> I'm looking for the best tool to prepare and apply firmware images
> based on Buildroot. I know that is a complex matter, but what I'm
> asking here is an advice.
>
> After several hours of searching, I finally found what seems a good
> piece of software:
>
> https://github.com/fhunleth/fwup
>
> It's maintained and it has a good integration with Buildroot.
> I know that Thomas Petazzoni wrote this one:
>
> https://www.gitorious.org/embedded-linux-firmware-upgrade-tool
>
> But It seems not maintained anymore.
>
> Any advice on this matter?
There is also https://github.com/sbabic/swupdate, which was presented
last week at ELCE, see
http://events.linuxfoundation.org/sites/events/files/slides/SoftwareUpdateForEmbedded.pdf.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-20 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:17 [Buildroot] Firmware update for Buildroot Angelo Compagnucci
2014-10-20 14:30 ` Thomas Petazzoni [this message]
2014-10-20 14:42 ` Angelo Compagnucci
2014-10-20 14:48 ` Thomas Petazzoni
2014-10-20 21:49 ` Romain Naour
2014-10-21 6:07 ` Angelo Compagnucci
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=20141020163051.1f4b05eb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.