linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David N. Welton" <davidw@linuxcare.com>
To: Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Cc: ajoshi@shell.unixbox.com
Subject: Re: again 2.3.28
Date: Wed, 17 Nov 1999 11:53:40 -0800	[thread overview]
Message-ID: <19991117115340.D4281@bassano.linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9911171141110.5126-100000@shell.unixbox.com>; from Ani Joshi on Wed, Nov 17, 1999 at 11:43:40AM -0800


On Wed, Nov 17, 1999 at 11:43:40AM -0800, Ani Joshi wrote:

> On Wed, 17 Nov 1999, David N. Welton wrote:

> > So, we can't use prom_print to print checkpoints and we can't use
> > printk yet.
 
> you can use prom_print to print until start_kernel, 

This is from arch/ppc/kernel/prom.c :

 * Because OF may have mapped I/O devices into the area starting at
 * KERNELBASE, particularly on CHRP machines, we can't safely call
 * OF once the kernel has been mapped to KERNELBASE.  Therefore all
 * OF calls should be done within prom_init(), and prom_init()
 * and all routines called within it must be careful to relocate
 * references as necessary.

This is indeed a CHRP machine, an RS6K F50, to be precise.

So, according to the people who wrote this code, you cannot do that.

> then you can use printk because console_init() is done very early
> (unless its dieing before that which would really suck), but i'm
> pretty sure you should be able to prom_print until then.  how are
> you calling your prints?

I was calling them with 'bl myfunc', which was defined as void myfunc
() and contained a call to prom_print.

Thanks,
-- 
David N. Welton, Developer, Linuxcare, Inc.
415.354.4878 x241 tel, 415.701.7457 fax
davidw@linuxcare.com, http://www.linuxcare.com/
Linuxcare. At the center of Linux.

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

  reply	other threads:[~1999-11-17 19:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-17 18:53 again 2.3.28 Andreas Tobler
1999-11-17 19:01 ` David N. Welton
1999-11-17 19:43   ` Ani Joshi
1999-11-17 19:53     ` David N. Welton [this message]
1999-11-17 20:06       ` Ani Joshi
1999-11-17 20:09         ` Mac specific code David N. Welton
1999-11-18  4:03   ` again 2.3.28 David N. Welton
1999-11-18  4:26     ` David Edelsohn
1999-11-18  6:45       ` David N. Welton
1999-11-17 19:39 ` Ani Joshi
1999-11-17 19:49   ` Geert Uytterhoeven
1999-11-17 20:15     ` Ani Joshi
1999-11-17 20:18       ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
1999-11-18 10:01 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=19991117115340.D4281@bassano.linuxcare.com \
    --to=davidw@linuxcare.com \
    --cc=ajoshi@shell.unixbox.com \
    --cc=linuxppc-dev@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).