linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: machael <dony.he@huawei.com.cn>
Cc: Wolfgang Denk <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Does linux-2.4.0-test1 support 8260?
Date: Mon, 02 Apr 2001 14:43:50 -0400	[thread overview]
Message-ID: <3AC8C866.AE9CDA83@mvista.com> (raw)
In-Reply-To: 000b01c0a2e5$c499d400$8021690a@huawei.com


machael wrote:

>       Does linux-2.4.0-test1 support 8260?

I haven't tried it recently, but it used to work.  I just used
the linuxppc_2_5 baseline to port a couple of new 8260s I received.
It worked fine.  I don't recall anything (except probably the I2C
stuff) that is in this baseline and not in 2.4.  You may want to
get a newer kernel, like 2.4.2, and from someplace like FSM Labs.
There are some uart driver hacks for SCC console that don't seem
to be working, but I can't think of anything else.

> Note that there is an error  when showing "Freeing initrd memory: 4194300k
> freed" .

That's just a stupid 'printk' problem printing a bogus variable (that
I think several people, including me, have checked in a fix).
There isn't any bug associated with that.

I know it's very hard, but have you verified your memory timing
parameters with some simple test programs?  Once Linux starts
running with MMU and caches enabled, it pushes the limits of the
hardware and nasty things like this start to appear.


	-- Dan

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

           reply	other threads:[~2001-04-02 18:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <000b01c0a2e5$c499d400$8021690a@huawei.com>]

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=3AC8C866.AE9CDA83@mvista.com \
    --to=dan@mvista.com \
    --cc=dony.he@huawei.com.cn \
    --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).