linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
	Dan Malek <dan@mvista.com>
Subject: Re: status of linuxppc_2_4_devel for ppc405gp
Date: Fri, 24 Aug 2001 11:41:54 +1000	[thread overview]
Message-ID: <20010824114153.A790@zax> (raw)
In-Reply-To: <20010823110818.2847@smtp.adsl.oleane.com>


On Thu, Aug 23, 2001 at 01:08:18PM +0200, Benjamin Herrenschmidt wrote:
>
> >>I'm now able to run a very simple binary as init - basically "Hello,
> >>world!" implemented with one write() syscall, and none of the libc
> >>initialisation junk present.  A one write hello world with the normal
> >>crt0 (statically linked) fails.
> >
> >Ok. So this would mean the problem is with the libc junk ? Hrm.
> >I didn't trace that far yet, but I suspect the libc I've been
> >using (the "normal" 6xx one) lacks some cache stuffs. I'm
> >pretty convinced that we must inval the entire instructions cache
> >each time we used to do icbi's (either that or handle the cache
> >aliasing issues specific to the 405GP weird icache design).
> >
> >I'll do more experiments later today.
>
> I found at least one other problem: The kernel is happily doing
> tlbie's on the 405 (which doesn't support them). Among other places,
> calls to flush_HPTE are turned into _tlbie which is not redefined
> to do a tlbia, causing at least ioremap to break.

Ah yes, I ran into that one when I started converting the ppc405_enet
driver to use ioremap() and in_beXX() instead of the godawful mess of
direct access and explicit eieio()s it uses now.

--
David Gibson			| Microsoft: Making the easy things hard
david@gibson.dropbear.id.au	| and the hard things buggy
http://www.ozlabs.org/people/dgibson


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

  reply	other threads:[~2001-08-24  1:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 10:22 status of linuxppc_2_4_devel for ppc405gp Stefan Roese
2001-08-22 12:30 ` Kenneth Johansson
2001-08-22 16:10   ` Dan Malek
2001-08-22 22:29     ` Phillip Lougher
2001-08-22 22:48       ` Dan Malek
2001-08-22 13:41 ` Benjamin Herrenschmidt
2001-08-22 13:32   ` Physically mapped FLASH David Updegraff
2001-08-22 10:32     ` Matt Porter
2001-08-22 16:06   ` status of linuxppc_2_4_devel for ppc405gp Dan Malek
     [not found]     ` <3B83E474.5B906F13@mvista.com>
2001-08-22 19:31       ` Dan Malek
2001-08-22 20:04     ` Benjamin Herrenschmidt
2001-08-23  0:40       ` David Gibson
2001-08-23  7:41         ` Benjamin Herrenschmidt
2001-08-23 11:08           ` Benjamin Herrenschmidt
2001-08-24  1:41             ` David Gibson [this message]
2001-08-24  5:06               ` Dan Malek
2001-08-24  6:03                 ` David Gibson
2001-08-24 10:28                 ` Benjamin Herrenschmidt
2001-08-25  2:53                   ` Dan Malek

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=20010824114153.A790@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=dan@mvista.com \
    --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).