From: LiuTao <tliu@ict.ac.cn>
To: "Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>,
LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problem on MPC8xx
Date: Tue, 07 Mar 2000 10:17:25 +0800 [thread overview]
Message-ID: <38C466B5.8C832308@ict.ac.cn> (raw)
In-Reply-To: 200003061503.KAA21814@hoover.gilbarco.com
Hi:
> Hmmmm... Well, I remember when I got to this point it took a week or so to
> get the bash prompt to actually come out. It was rather irritating being
> 95% of the way and stumped. Try this, since bash is the first real process
> that runs it really stresses the board and the memory timings, etc. Make
> sure that the libraries are being loaded and it isn't hanging half-way. Try
> modifying fs/namei.c and put a printk at the top of open_namei to print the
> pathname.... that should dump which files are being loaded... email me the
> results of that.
I added printk() in open_namie(), the output is:
pathname:/dev/conle
pathname:/sbin/init
pathname:/etc/init
pathname:/bin/initstarting /bin/sh...
pathname:/bin/sh
pathname:/lib/ld.so.1
pathname:/etc/ld.so.preload
pathname:/etc/ld.so.cache
pathname:/lib/libtermcap.so.2
pathname:/lib/libdl.so.2
pathname:/lib/libc.so.6
Is that all right?
Another question, I don't have a PowerPC box, I build Linux on a x86 box
with cross compile environment, can I make a ramdisk? The ramdisk I am
using
is a little large, I want to make a smaller one.
Thanks!
LiuTao
> Hi Jason:
>
> I am sorry that another problem appeared.
> After the /bin/sh ran, I can't see anything from console.
> I open the compile switch "SERIAL_DEBUG_INTR" in uart.c,
> then I can see the following message on console:
>
> THRE...rs_interrupt_single(0, 2)...end.
> THRE...rs_interrupt_single(0, 2)...end.
> .
> .
> .
>
> It means that the transmit interrupt is triggered, right?
> But why I can't see anything?
> And can you tell me that when shell outputs message to console,
> which function it uses in uart.c? I think it should be
> rs_8xx_write(), right? But I found that this function was not
> called before interrupt happened.
>
> Thanks!
>
> LiuTao
>
> >
> > I'm glad to hear you resolved your problem. If I can lend you any other
> > assistance, let me know, I have gone all the way through porting the
> kernel
> > to a custom 860 board now and are familiar with solutions to some
> stumbling
> > blocks.
> >
> > Jason
> >
> > -----Original Message-----
> > From: LiuTao [mailto:tliu@ict.ac.cn]
> > Sent: Thursday, March 02, 2000 5:24 AM
> > To: Jason Wohlgemuth
> > Subject: Re: problem on MPC8xx
> >
> > Hi Jason:
> >
> > Thanks for your attention!
> > I found the problem in uart.c, the BRG is setup incorrectly.
> > I have resolved the problem.
> > Now, I can see message from console port.
> >
> > Thanks.
> >
> > LiuTao
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-03-07 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200003061503.KAA21814@hoover.gilbarco.com>
2000-03-07 2:17 ` LiuTao [this message]
[not found] <NCBBKJKKGDLPHKDPAFFMIECLCDAA.jsw-embedded@mindspring.com>
2000-03-06 13:37 ` problem on MPC8xx LiuTao
[not found] <NCBBKJKKGDLPHKDPAFFMKEBMCDAA.jsw-embedded@mindspring.com>
2000-03-02 10:26 ` LiuTao
[not found] <NCBBKJKKGDLPHKDPAFFMGEBGCDAA.jsw-embedded@mindspring.com>
2000-02-28 14:11 ` LiuTao
2000-02-28 13:24 LiuTao
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=38C466B5.8C832308@ict.ac.cn \
--to=tliu@ict.ac.cn \
--cc=jason_wohlgemuth@gilbarco.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--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).