public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/RFC] unify version_string
Date: Fri, 24 Jun 2011 22:07:34 +0200	[thread overview]
Message-ID: <20110624200734.560B620155D@gemini.denx.de> (raw)
In-Reply-To: <BANLkTim-gWWs+5ktKPTR+08uoQM-oZuwEw@mail.gmail.com>

Dear Mike Frysinger,

In message <BANLkTim-gWWs+5ktKPTR+08uoQM-oZuwEw@mail.gmail.com> you wrote:
>
> > On PowerPC systems, the core is carefully consructed such that the

s/core/code/, s/consructed/constructed/

> > U-Boot image starts with the magic number, followed immediately by
> > the version string. That means, you can trivially identify any binary
> > image, be it as file on the host or on the target, or programmed into
> > flash, but just dumping the first bytes of it, for example:
> 
> cant you do this with a linker script update ?

Insert strings in the middle of code?  Sonds more complicated that
what it's worth.

I don't see the real problem.  I mean, we can provide the definition
of the string in some common header file, and then just use it where
needed.

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
Nothing ever becomes real until it is experienced.       - John Keats

  parent reply	other threads:[~2011-06-24 20:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  8:47 [U-Boot] [PATCH/RFC] unify version_string Andreas Bießmann
2011-06-24 12:18 ` Wolfgang Denk
2011-06-24 17:43   ` Mike Frysinger
2011-06-24 19:48     ` Andreas Bießmann
2011-06-24 20:10       ` Wolfgang Denk
2011-06-29 22:32         ` [U-Boot] [PATCH/RFC v4] " Andreas Bießmann
2011-06-29 23:18           ` Mike Frysinger
2011-06-30 21:27             ` [U-Boot] [PATCH/RFC v5] " Andreas Bießmann
2011-06-30 22:27               ` Mike Frysinger
2011-07-18 18:24               ` [U-Boot] [PATCH v6] " Andreas Bießmann
2011-07-18 18:27                 ` Mike Frysinger
2011-07-28  7:30                 ` Andreas Bießmann
2011-07-28 15:23                 ` Wolfgang Denk
2011-07-28 15:30                   ` Wolfgang Denk
2011-07-28 16:19                 ` [U-Boot] [PATCH v7] " andreas.devel at googlemail.com
2011-07-28 20:21                   ` Wolfgang Denk
2011-07-28 21:09                   ` Wolfgang Denk
2011-07-29  7:05                     ` Andreas Bießmann
2011-07-29  8:24                       ` Wolfgang Denk
2011-07-31 10:35                       ` [U-Boot] [PATCH] linkstation: fix warning: "CONFIG_IDENT_STRING" redefined Wolfgang Denk
2011-09-05  7:43                         ` Wolfgang Denk
2011-07-29 12:42                   ` [U-Boot] [PATCH] Constify getenv(), setenv() and hash code functions Wolfgang Denk
2011-07-29 23:38                     ` Wolfgang Denk
2011-06-24 20:07     ` Wolfgang Denk [this message]
2011-06-24 20:52       ` [U-Boot] [PATCH/RFC] unify version_string Mike Frysinger
2011-06-24 12:34 ` [U-Boot] [PATCH/RFC v2] " Andreas Bießmann
2011-06-24 13:37   ` Wolfgang Denk
2011-06-24 20:01 ` [U-Boot] [PATCH/RFC v3] " Andreas Bießmann

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=20110624200734.560B620155D@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