All of lore.kernel.org
 help / color / mirror / Atom feed
From: DENX Support System <support@denx.de>
To: u-boot@lists.denx.de
Subject: [DNX#2006040142001098] [U-Boot-Users] Safe firmware updates
Date: Sat, 1 Apr 2006 00:50:13 +0200	[thread overview]
Message-ID: <1143845413.894729.324819733@castor.denx.de> (raw)

Hello list,

inside the automatic U-Boot patch tracking system a new ticket
[DNX#2006040142001098] was created:

<snip>
> In message <Pine.WNT.4.61.0602161324350.1692@holyoke.labs.mot.com> you
> wrote:
> >
> > Just to make sure you're considering all options -- the problem could also
> > be addressed solely with Linux.
> 
> No, it cvannot. For any *reliable* update method you need a constant,
> known to be working piece of software.
> 
> > kexec() seems to be the current recommendation for kernel upgrades, though
> 
> That's something completely different.
> 
> > I think it's only in 2.6.
> 
> The method is not new. It has been used a long, long time before. See
> Magnus Damm's relf.
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> It is undignified for a woman to play servant to a man who is not
> hers.
> 	-- Spock, "Amok Time", stardate 3372.7
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
</snip>

Your U-Boot support team

                 reply	other threads:[~2006-03-31 22:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1143845413.894729.324819733@castor.denx.de \
    --to=support@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 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.