From: LiuTao <tliu@ict.ac.cn>
To: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: problem on MPC8xx
Date: Mon, 28 Feb 2000 21:24:50 +0800 [thread overview]
Message-ID: <38BA7722.7730C0E3@ict.ac.cn> (raw)
Hi:
I am debugging Linux on my customized board.
The messages in log_buf are all right. The shell in RAM disk
also runs. But I can't see anything on serial port.
I want to know:
1. May I use ramdisk.image.gz of mbx as my ramdisk?
2. Need I modify the uart.c? If I need, which part I should modify?
3. Is there any meathod to test if the serial port is OK?
Thanks!
LiuTao
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-02-28 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 13:24 LiuTao [this message]
[not found] <NCBBKJKKGDLPHKDPAFFMGEBGCDAA.jsw-embedded@mindspring.com>
2000-02-28 14:11 ` problem on MPC8xx LiuTao
[not found] <NCBBKJKKGDLPHKDPAFFMKEBMCDAA.jsw-embedded@mindspring.com>
2000-03-02 10:26 ` LiuTao
[not found] <NCBBKJKKGDLPHKDPAFFMIECLCDAA.jsw-embedded@mindspring.com>
2000-03-06 13:37 ` LiuTao
[not found] <200003061503.KAA21814@hoover.gilbarco.com>
2000-03-07 2:17 ` 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=38BA7722.7730C0E3@ict.ac.cn \
--to=tliu@ict.ac.cn \
--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 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.