From: Kate Alhola <kate@iti.fi>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_mpc5200 / 5200lite zImage continued
Date: Sun, 02 Nov 2003 17:31:39 +0200 [thread overview]
Message-ID: <3FA5235B.7080007@iti.fi> (raw)
In-Reply-To: <3FA50B32.4010400@iti.fi>
Kate Alhola wrote:
>
>
> and in this case the mgt5100_tty.c look a like have one dependence
> to ppcboot, it took the ibp bus clock frequency from ppcboot bd struct
> even
> not ppc-boot configuration. I replaced it with just plain #define .
> Now just i should do testing ...
I just fixed it by comenting out setting baudrate, then it will leave it as
it was after dBug. Now i get kernel booting up and initial strings
coming out
but kernel crashes after initMMU ( early boot prit enabled ),
I think that i have something wrong in .config.
I did not find goog example gor 5200lite from denx tree so i made
my best quess and it seems not to bee so good.
Kate
-- continues hacking ....
dBUG> dn -i zImage.icecube
Address: 0x00020000
Downloading Image 'zImage.icecube' from 195.218.81.140
..............
939645 bytes read via TFTP
dBUG> go 20000
loaded at: 00020000 001071B8
relocated to: 00800000 008E71B8
zimage at: 00805830 008E3C88
avail ram: 00400000 00800000
Linux/PPC load: console=ttyS0,9600 root=/dev/sda2
Uncompressing Linux...done.
Now booting the kernel
id mach(): doneMMU:enterMMU:hw initMMU:mapin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-02 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 12:08 linuxppc_2_4_mpc5200 / 5200lite zImage Kate Alhola
2003-11-02 13:35 ` Wolfgang Denk
2003-11-02 13:48 ` Kate Alhola
2003-11-02 15:31 ` Kate Alhola [this message]
2003-11-02 15:55 ` linuxppc_2_4_mpc5200 / 5200lite zImage continued Wolfgang Denk
2003-11-02 19:12 ` linuxppc_2_4_mpc5200 / 5200lite zImage now working Kate Alhola
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=3FA5235B.7080007@iti.fi \
--to=kate@iti.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.