All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC 3/3] zImage: Exception vector support
Date: Fri, 23 Feb 2007 18:52:51 +0100	[thread overview]
Message-ID: <38d58173c87668b983e8b5173e4ab3e5@kernel.crashing.org> (raw)
In-Reply-To: <1172250409.1902.4.camel@localhost.localdomain>

>> If this is an ELF file, you can put the exception vectors in a
>> separate segment.  Or if you don't need the entry point to
>> be in the low region, (and you don't need that unless your
>> boot loader ignores the entry point in the ELF header), you can
>> copy the vectors in at startup and have no code linked at 0 at
>> all.
>
> No you cant. When flashed in ROM, the HV expands the bootloader binary
> at 0 and jumps to 0x100

Yeah, I said "if this is an ELF file", and that's not the
case unfortunately.


Segher

  reply	other threads:[~2007-02-23 17:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18  1:17 [RFC 3/3] zImage: Exception vector support Geoff Levand
2007-02-18  1:40 ` Josh Boyer
2007-02-19 15:03   ` Geoff Levand
2007-02-19 19:55     ` Benjamin Herrenschmidt
2007-02-19 20:40       ` Geoff Levand
2007-02-19 20:51         ` Benjamin Herrenschmidt
2007-02-19 21:35     ` Josh Boyer
2007-02-19 21:39       ` Geoff Levand
2007-02-19 21:51         ` Josh Boyer
2007-02-19  0:34 ` Paul Mackerras
2007-02-20  2:25 ` David Gibson
2007-02-20 14:23   ` Geoff Levand
2007-02-20 15:44     ` Geoff Levand
2007-02-20 16:02       ` Segher Boessenkool
2007-02-21  0:16         ` David Gibson
2007-02-23 17:06         ` Benjamin Herrenschmidt
2007-02-23 17:52           ` Segher Boessenkool [this message]
2007-02-21  0:16       ` David Gibson
2007-02-23 17:06       ` Benjamin Herrenschmidt

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=38d58173c87668b983e8b5173e4ab3e5@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    /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.