linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: enneper <cesli@ewetel.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Booting 2.3.48 (devel) kernel problems?
Date: Wed, 8 Mar 2000 16:27:46 +0100	[thread overview]
Message-ID: <20000308162745.A381@gmx.li> (raw)
In-Reply-To: <20000308151946.024345@mailhost.mipsys.com>; from Benjamin Herrenschmidt on Wed, Mar 08, 2000 at 03:19:46PM +0100



 Benjamin Herrenschmidt }  I think it worked with OF because we inherit from OF SDR1 and, by luck,
 Benjamin Herrenschmidt }  OF page tables are high enough in memory to not have been damaged by the

yes, 2.3.48 works with 3400-OF

there are three things so far:
-OF complains past the standart
	ok
	copying OF device tree ...done
 about:
	Initialising fake screen
	Failed to get address
 but lets linux make its way

-in something like mutt in aterm, colours and fonts scramble for their rights at the bottom of the window with a very useless result, a bit annoying.

-pcmcia compiles with:
i82365.c:110: warning: `do_scan' defined but not used
i82365.c:553: warning: `test_irq' defined but not used
i82365.c:737: warning: `add_socket' defined but not used
i82365.c:748: warning: `add_pcic' defined but not used
i82365.c:1499: warning: `init_i82365' defined but not used
i82365.c:1543: warning: `exit_i82365' defined but not used
but gets massive pci problems, so no driver is loaded.

greetings
Claus

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

  reply	other threads:[~2000-03-08 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-08 14:19 Booting 2.3.48 (devel) kernel problems? Benjamin Herrenschmidt
2000-03-08 15:27 ` enneper [this message]
2000-03-08 15:41 ` Michael Schmitz
  -- strict thread matches above, loose matches on Subject: below --
2000-03-08  3:51 Robert Shaw
2000-03-08  7:25 ` enneper
2000-03-08 10:10   ` Michael Schmitz
2000-03-08 12:34     ` enneper
2000-03-08 13:14       ` Michael Schmitz

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=20000308162745.A381@gmx.li \
    --to=cesli@ewetel.net \
    --cc=enneper@gmx.net \
    --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).