From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autotest infrastructure (a bit of off-topic: git repo URL)
Date: Fri, 9 Nov 2012 11:47:50 +0100 [thread overview]
Message-ID: <20121109114750.6a4dc53a@skate> (raw)
In-Reply-To: <509C224B.8000405@mind.be>
Hello,
On Thu, 08 Nov 2012 22:21:15 +0100, Arnout Vandecappelle wrote:
> Pretty off-topic indeed... but I don't mind :-)
>
> On 11/08/12 17:21, Javier Viguera wrote:
> > I attended the other day to your talk on "upgrading without bricking" (congrats for that, i learned a lot) and you
> > mentioned a repo where you have started collecting some tools/scripts to do the job.
> >
> > Could you remind me that repo URL? I shouldn't have trust i would remember it some days after.
>
> https://gitorious.org/gupies
>
> But as I mentioned, it's still pretty empty... I expect to really start
> committing something in a week or two.
>
> I've also created a mailing list, but it's on google groups which sucks
> somewhat: https://groups.google.com/group/gupies/subscribe
> If you have a better idea, I'd welcome that.
On a related topic (firmware upgrade), I have:
https://gitorious.org/embedded-linux-firmware-upgrade-tool/embedded-linux-firmware-upgrade-tool
It has a:
* A host utility to prepare firmware images composed of multiple parts
(usually a kernel image + root filesystem image, but there could be
more)
* A target utility that can run either on the command line or as a CGI
script. This utility does the firmware upgrade itself by fiddling
with the U-Boot environment.
The tool assumes that the flash has two partitions for each component
been upgraded (one active partition, one to upgrade).
The documentation at
https://gitorious.org/embedded-linux-firmware-upgrade-tool/embedded-linux-firmware-upgrade-tool/blobs/master/fwupgrade-doc.txt
has a few details.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-09 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 15:00 [Buildroot] Autotest infrastructure Arnout Vandecappelle
2012-11-08 16:21 ` [Buildroot] Autotest infrastructure (a bit of off-topic: git repo URL) Javier Viguera
2012-11-08 21:21 ` Arnout Vandecappelle
2012-11-09 10:47 ` Thomas Petazzoni [this message]
2012-11-09 12:13 ` Peter Korsgaard
2012-11-09 13:18 ` Thomas Petazzoni
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=20121109114750.6a4dc53a@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox