public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] 83xx: Put the version (and magic) after the HRCW.
Date: Fri, 08 Dec 2006 10:33:52 -0600	[thread overview]
Message-ID: <457993F0.9040203@freescale.com> (raw)
In-Reply-To: <4578D2D5.9010401@comcast.net>

Jerry Van Baren wrote:

> Arrgh, I forgot about the 8260 master + 7 slaves mode, which fills the 
> first 256 bytes with HRCWs.  As a result, we cannot put the magic number 
> and version at offset 0x40 like I did with the 8360 (well, we could do 
> it, but only if the system doesn't have slaves).  We could, however, put 
> the magic number and version in a different vector area that has room 
> (e.g. offset 0x240).

Or, you could tag the version string with a checksum and a signature, then have 
the application scan memory until it finds it.  That way, you could put it 
wherever you want, even in different places on different systems, and it would 
still work.

Joakim asked me to ack or nack this patch, but at this point I can't tell who 
wants what.  Can someone summarize the status of this patch for me?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2006-12-08 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  2:23 [U-Boot-Users] [PATCH] 83xx: Put the version (and magic) after the HRCW Jerry Van Baren
2006-12-07  2:55 ` Jerry Van Baren
2006-12-07  3:16 ` [U-Boot-Users] Re: " Sam Song
2006-12-07  3:45   ` [U-Boot-Users] " Jerry Van Baren
2006-12-08  2:49     ` Jerry Van Baren
2006-12-08 16:33       ` Timur Tabi [this message]
2006-12-08 16:50         ` Jerry Van Baren
2006-12-08 21:13           ` Timur Tabi
2006-12-08 21:36             ` Jerry Van Baren
2006-12-08 21:38               ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2006-12-07  8:32 Joakim Tjernlund
2006-12-07 13:22 ` Jerry Van Baren
2006-12-07 17:05 Joakim Tjernlund

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=457993F0.9040203@freescale.com \
    --to=timur@freescale.com \
    --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