linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tnt.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on MPC5200 - LITE5200EVAL & New bestcomm code ?
Date: Wed, 03 Mar 2004 08:34:36 +0100	[thread overview]
Message-ID: <40458A8C.8020009@246tNt.com> (raw)
In-Reply-To: <402E633A.2040009@246tNt.com>

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

Hi every one.


A little update on my problems. Apparently the problem was the u-boot
command I used to boot :

I used :
     tftp 100000 mpc5200/uImage; tftp 300000 mpc5200/pRamdisk;bootm
100000 300000

And now I use :
     tftp 200000 mpc5200/uImage; tftp 400000 mpc5200/pRamdisk;bootm
200000 400000

and it works just fine ... Apparently when the kernel was too big, the
area near 100000 is probably used by u-boot in some way, maybe during
decompression and it doesnt work. I've check with multiple different
memory tests that the concerned memory region is fine. So it is a
software issue. Maybe u-boot should give some warning about that ( if
it's the cause, not yet sure ). But that's off topic here.



Now, I'm just looking forward for new BestComm code, to get AC97 and IDE
DMA running ( quite slow and CPU intensive right now ... ).



Sylvain Munaut



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2004-03-03  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <402E0D8C.4080801@246tNt.com>
2004-02-14 14:53 ` Linux on MPC5200 - LITE5200EVAL Wolfgang Denk
2004-02-14 18:04   ` Sylvain Munaut
2004-03-03  7:34     ` Sylvain Munaut [this message]
2004-03-03  8:03       ` Linux on MPC5200 - LITE5200EVAL & New bestcomm code ? Wolfgang Denk
2004-02-17  1:08   ` Linux on MPC5200 - LITE5200EVAL Dale Farnsworth

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=40458A8C.8020009@246tNt.com \
    --to=tnt@246tnt.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).