From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about Automatic Updates
Date: Mon, 08 Apr 2013 07:30:38 +0200 [thread overview]
Message-ID: <20130408053038.B3ABA2003F6@gemini.denx.de> (raw)
In-Reply-To: <FE7ADED5C2218B4786C09CD97DC4C49F812619@exchbj02.viatech.com.bj>
Dear TigerLiu at viatech.com.cn,
In message <FE7ADED5C2218B4786C09CD97DC4C49F812619@exchbj02.viatech.com.bj> you wrote:
>
> I found an Automatic Updates digest in this web page:
> http://www.denx.de/wiki/view/U-Bootdoc/AutomaticUpdates
>
> So, my question is:
> 1. Can uboot support this feature now?
This has been implemented (actually in a number of veriants) for
several boards in U-Boot.
> I could not find key word "firmware.img" etc in u-boot source code
> package.
Most of this is usually done as shell scripts run by U-Boot. These
scripts are usually proprietary code ant not part of the U-Boot
distribution.
Mainline U-Boot contains all the needed features, and implementing
such an update mechanism is relatively straightforward.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
While most peoples' opinions change, the conviction of their correct-
ness never does.
next prev parent reply other threads:[~2013-04-08 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 10:06 [U-Boot] which u-boot build config to choose for kirkwood? JPT
2013-04-07 19:21 ` [U-Boot] problem building uboot JPT
2013-04-07 19:31 ` Wolfgang Denk
2013-04-08 1:03 ` [U-Boot] Question about Automatic Updates TigerLiu at viatech.com.cn
2013-04-08 5:30 ` Wolfgang Denk [this message]
2013-04-08 17:40 ` Jagan Teki
2013-04-08 18:28 ` Wolfgang Denk
2013-04-08 9:01 ` [U-Boot] build succeeded, what now? JPT
2013-04-08 9:05 ` [U-Boot] how to troubleshoot when u-boot is stuck JPT
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=20130408053038.B3ABA2003F6@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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