All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Cort Dougan <cort@fsmlabs.com>,
	linuxppc-dev@lists.linuxppc.org, paulus@linuxcare.com
Subject: Re: bootloader & head.S weirdness (patch)
Date: Tue, 23 Nov 1999 11:44:59 +0100	[thread overview]
Message-ID: <19991123114459.026069@mailhost.mipsys.com> (raw)
In-Reply-To: <19991122150653.A13066@hq.fsmlabs.com>


On Mon, Nov 22, 1999, Cort Dougan <cort@fsmlabs.com> wrote:

>I applied the patch (with some changes necessary to get it into
>2.2.14pre7).  It breaks pmac netboot during the jump from
>__secondary_stat() to clear_bats(). 

You mean netbooting the kernel image directly from OF without going thru
a bootloader ? Or are you talking about the xcoff piggyback bootstrap ?

>There must be some I mappings we need
>to preserve in order to get to non-pc relative code.  It's worth noting
>that OF loads us and gives us mappings for 0xc000000 since that's where
>we're linked at. 

I never managed to get OF load the kernel image directly. How did you
acheive this result (OF setting up such a mapping ?). In this specific
case, it's always possible to ask OF about our physical address and use
it for the return address of mmu_off. It should be returned by prom_init
in r3. This would be cleaner anyway. I'll look into fixing that but I'd
like to know how you did this netboot stuff so I can reproduce it here.
(Could you send me your bootptab ?)

>BootX and Quik don't do that so that's probably why they
>work.  Netboot is really useful so I'd prefer to not break it (definitely
>not in 2.2).  Any ideas for workarounds?

Yes, as I wrote before, OF can tell us the real physical address and we
can return it from prom_init so that mmu_off does the right thing.

>Chrp and prep netboot works fine.  Boot via quik on chrp works, too.

Great.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-11-23 10:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19991122120429.031138>
1999-11-22 11:47 ` bootloader & head.S weirdness (patch) Benjamin Herrenschmidt
1999-11-22 17:07   ` Benjamin Herrenschmidt
1999-11-22 22:06     ` Cort Dougan
1999-11-23 10:44       ` Benjamin Herrenschmidt [this message]
1999-11-23 12:35       ` Benjamin Herrenschmidt
1999-11-22 21:40   ` Cort Dougan
1999-11-23 10:40     ` Benjamin Herrenschmidt
1999-11-23 17:48       ` Cort Dougan
1999-11-23 18:34         ` Geert Uytterhoeven
1999-11-23 19:16           ` Cort Dougan
1999-11-23 19:35             ` Benjamin Herrenschmidt
1999-11-23 20:16             ` Geert Uytterhoeven
1999-11-23 20:21               ` Cort Dougan
1999-11-24  7:32                 ` Geert Uytterhoeven
     [not found] <19991123133536.013861>
1999-11-23 17:07 ` Benjamin Herrenschmidt
1999-11-23 17:52   ` Cort Dougan
1999-11-23 18:08     ` 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=19991123114459.026069@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=cort@fsmlabs.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com \
    /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.