linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "James Dougherty" <jfd@broadcom.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: "bhupinder sahran" <bhup_sah@yahoo.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problems with mount system call -- cannot mount procfs!
Date: Wed, 31 Jul 2002 12:53:35 -0700	[thread overview]
Message-ID: <3D48403F.B761E1D3@broadcom.com> (raw)
In-Reply-To: 20020731194907.0224D1087A@denx.denx.de


Wolfgang Denk wrote:
>
> In message <3D483468.CB6DAE54@broadcom.com> you wrote:
> >
> > I checked out my ppcboot early_init.S and the ppcboot startup files.
> > In ppcboot-1.1.4/cpu/mpc824x/start.S
> ...
> > I remove this code with an ifdef:
> >
> > #if !defined(CONFIG_MUSENKI) && !defined(CONFIG_BMW)
> >
> > And then rebuilt and boot linux-2.4.19-rc3 (latest rsync from mvista.com yesterday)!
>
> Well, and what was the result?
>

Life is good :-) Everything is working perfectly.


> > Does the setup code above work on Sandpoint, or another MPC824x system?
>
> Sure. It works here on SP8240, and on CU824 boards (both with 8240 CPUs).

It would appear that the memory/cache architecture is different on those boards.
Do you have an external cache? I believe the Sandpoint modules have an option
for L2 cache...

--
James F. Dougherty, III
Broadcom Corporation
jfd@broadcom.com
(408) 501-8273


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

  reply	other threads:[~2002-07-31 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020731033106.39762.qmail@web20705.mail.yahoo.com>
2002-07-31 19:03 ` Problems with mount system call -- cannot mount procfs! James Dougherty
2002-07-31 19:49   ` Wolfgang Denk
2002-07-31 19:53     ` James Dougherty [this message]
2002-07-29 18:45 James Dougherty
2002-07-29 19:03 ` James Dougherty

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=3D48403F.B761E1D3@broadcom.com \
    --to=jfd@broadcom.com \
    --cc=bhup_sah@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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).