All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH][FOR 1.3.4] 85xx: Don't move interrupt vector to low memory
Date: Wed, 06 Aug 2008 15:41:47 -0400	[thread overview]
Message-ID: <4899FE7B.80508@ge.com> (raw)
In-Reply-To: <20080806193205.GA3975@ld0162-tx32.am.freescale.net>

Scott Wood wrote:
> On Wed, Aug 06, 2008 at 04:42:51PM +0200, Wolfgang Denk wrote:
>> In message <41F2F68F-34F5-4D3B-8AA1-294589B48033@kernel.crashing.org> you wrote:
>>>> Oops? This is expected and normal behaviour. Did anybody complain
>>>> about this?
> 
> It's hit me before when I foolishly try to load something at address
> zero -- why do we put u-boot at the end of RAM, and put up with the
> relocation weirdness, if not to allow loading things at zero?
> 
>>> Real, any reason why?  I understand on classic PPC this might be the  
>>> case but I see no reason for it to be so on book-e parts.
>> Well, one reason might be to have identical code for all PPC systems ?
> 
> It's already 85xx-specific code.
> 
>>> Any they are.  I'm just removing a second relocation that is a hold  
>>> over from how 6xx PPC exception vectors work.
>> Not only 6xx. Actually all PPC.
> 
> No, not all PPC.  Book-E exceptions are different.
> 
> -Scott

One nice thing about not relocating the exception vectors to 0 is that 
it would allow us to recover from a failed bootm all the way up to the 
jump to linux (or whomever) rather than having to reset the board to 
recover from a failure late in the bootm sequence.

Unfortunately, it would be Book-E specific and probably not worth coding 
Yet Another Special Case in the already overcomplex bootm code.

Best regards,
gvb

  reply	other threads:[~2008-08-06 19:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  6:28 [U-Boot-Users] [PATCH][FOR 1.3.4] 85xx: Don't move interrupt vector to low memory Kumar Gala
2008-08-06  6:50 ` Wolfgang Denk
2008-08-06 12:58   ` Kumar Gala
2008-08-06 14:42     ` Wolfgang Denk
2008-08-06 19:32       ` Scott Wood
2008-08-06 19:41         ` Jerry Van Baren [this message]
2008-08-06 19:46         ` Wolfgang Denk
2008-08-06 19:49           ` Kumar Gala
2008-08-06 20:17             ` Wolfgang Denk
2008-08-06 20:34               ` Kumar Gala
2008-08-06 20:41                 ` Wolfgang Denk
2008-08-06 20:46                   ` Kumar Gala

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=4899FE7B.80508@ge.com \
    --to=gerald.vanbaren@ge.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 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.