linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: "David N. Welton" <davidw@linuxcare.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: again 2.3.28
Date: Thu, 18 Nov 1999 11:01:19 +0100	[thread overview]
Message-ID: <19991118110119.020630@mailhost.mipsys.com> (raw)


On Wed, Nov 17, 1999, David N. Welton <davidw@linuxcare.com> wrote:

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

if using BootX, you can use prom_print after mmu_init provided that you
make sure the fb is mapped (look at the function in prom.c for that, it's
called by xmon initialisation).

If you are not using BootX, then you can grab code that make prom_print
available the same way it does with BootX, but with OF. (Basically, it
fills a fake boot_info structure for use by the display code from infos
returned by OF). The code for that is in my iBook patches, look at the
prom.c patches.

In both case, you have to take care of mapping the fb.


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

             reply	other threads:[~1999-11-18 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-18 10:01 Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
1999-11-17 20:06       ` Ani Joshi
1999-11-18  4:03   ` 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

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=19991118110119.020630@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=davidw@linuxcare.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).