From: David Edelsohn <dje@watson.ibm.com>
To: Cort Dougan <cort@fsmlabs.com>
Cc: Christian Zankel <chris@mvista.com>,
linuxppc-dev@lists.linuxppc.org,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: bootloader & head.S weirdness & restructuring
Date: Tue, 23 Nov 1999 11:17:57 -0500 [thread overview]
Message-ID: <9911231617.AA25176@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Cort Dougan <cort@fsmlabs.com> of "Mon, 22 Nov 1999 16:55:35 MST." <19991122165535.A13360@hq.fsmlabs.com>
Why not have the kernel define, or at least reserve space for, the
interrupt vectors? If one specifies the correct padding and/or alignment,
the interrupt vector code will appear at the correct offsets when the
kernel is loaded at 0. The kernel can start at 0, not its entry point or
normal code.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-23 16:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 11:04 bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-22 21:37 ` Cort Dougan
1999-11-22 23:17 ` bootloader & head.S weirdness & restructuring Christian Zankel
1999-11-22 23:55 ` Cort Dougan
1999-11-23 3:31 ` Christian Zankel
1999-11-23 3:40 ` Cort Dougan
1999-11-23 6:37 ` Dan Malek
1999-11-23 18:22 ` Christian Zankel
1999-11-23 20:20 ` Dan Malek
1999-11-25 17:13 ` Geert Uytterhoeven
1999-11-25 19:49 ` Dan Malek
1999-11-26 9:06 ` Geert Uytterhoeven
1999-11-26 9:42 ` Michael Schmitz
1999-11-26 12:06 ` Wolfgang Denk
1999-11-28 22:41 ` Dan Malek
1999-11-29 7:12 ` Geert Uytterhoeven
1999-11-23 16:12 ` Michael Schmitz
1999-11-23 16:17 ` David Edelsohn [this message]
1999-11-23 17:46 ` Cort Dougan
1999-11-23 16:15 ` Gabriel Paubert
1999-11-23 16:52 ` Marcus Sundberg
1999-11-23 17:01 ` Gabriel Paubert
1999-11-23 17:45 ` Cort Dougan
1999-11-23 10:35 ` bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-23 10:50 ` Momchil Velikov
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=9911231617.AA25176@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=chris@mvista.com \
--cc=cort@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).