linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: "Laurent Mohin" <laurent.mohin@acterna.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405GPr support in linux2.4.18
Date: Wed, 19 Feb 2003 00:54:45 -0800	[thread overview]
Message-ID: <5.1.0.14.2.20030219004853.00b12e08@mail.ebshome.net> (raw)
In-Reply-To: <OFA7B6F432.6CF96B48-ONC1256CD1.00372BF7@eng.eni.wago.de>


At 02:11 AM 2/18/2003, Laurent Mohin wrote:
>I'm designing a board with 405GP processor. I'm now trying to have it
>working with a 405GPr version.
>I've started to configure it working in legacy mode and made the necessary
>changes in PPCBoot.
>
>Once downloaded, my kernel hung in early_init function when it called the
>memset_io to zero the BSS. Using a BDI2000 debugger, I saw that I've
>reached the bad_page_fault function.
>
>The only difference I know between 405GP and 405GPr in legacy mode is data
>cache size. How does the kernel manage it?

We successfully run 405GPr based board (in legacy mode) with the _same_
kernel we used for 405GP.
We don't use any 405GPr specific features though.

As far as I understand, the only function which depends on the data cache
size is flush_dcache_all in (arch/ppc/kernel/misc.S).
But it already handles the worst case which is 440GP (32K), so no change is
needed for 405GPr.

Eugene


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

  reply	other threads:[~2003-02-19  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 10:11 405GPr support in linux2.4.18 Laurent Mohin
2003-02-19  8:54 ` Eugene Surovegin [this message]
2003-02-19  9:15   ` Eugene Surovegin
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 10:53 Laurent Mohin

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=5.1.0.14.2.20030219004853.00b12e08@mail.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=laurent.mohin@acterna.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).