From: Daniel Ann <ktdann@gmail.com>
To: JohnsonCheng <johnsoncheng@qnap.com.tw>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: A PPC kernel issue with UART ??
Date: Wed, 3 Aug 2005 09:21:57 +0900 [thread overview]
Message-ID: <9b7ca6570508021721773d06f0@mail.gmail.com> (raw)
In-Reply-To: <20050802114145.36B2667D77@ozlabs.org>
Johnson,
You know what? I've had the exact same problem only day or two ago. I
think the mail subject was "serial console" or something similar. Have
a read at it.
BTW, My problem was with interrupt setting.
Daniel.
On 8/2/05, JohnsonCheng <johnsoncheng@qnap.com.tw> wrote:
>=20
>=20
> Dear All,
>=20
> =20
>=20
> I meet a wired UART problem on linux-2.6 with MPC8241 chip.
>=20
> =20
>=20
> My Environment is as following:=20
>=20
> CPU: MPC8241
>=20
> Linux: 2.6.12.3
>=20
> COM1 offset: 0x4500, COM2 offset: 0x4600
>=20
> =20
>=20
> When I booting my rootfs, it hangs at following message:
>=20
> RAMDISK: Compressed image found at block 0
>=20
> VFS: Mounted root (ext2 filesystem) readonly.
>=20
> Freeing unused kernel memory: 104k init
>=20
> EXT2-fs warning: checktime reached, running e2fsck is recommended
>=20
> =20
>=20
> I had add printk in tty_write() of drivers/char/tty_io.c, the message fro=
m
> rootfs have printed.
>=20
> The conclusion is that message can be printed by printk() in linux kernel=
,
> but can't be printed by printf() in user mode. I think it must be somethi=
ng
> wrong for my UART configurations, does anybody know it??
>=20
> =20
>=20
> =20
>=20
> Best Regards,
>=20
> Johnson Cheng
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
--=20
Daniel
next prev parent reply other threads:[~2005-08-03 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 11:41 A PPC kernel issue with UART ?? JohnsonCheng
2005-08-03 0:21 ` Daniel Ann [this message]
2005-08-03 3:11 ` JohnsonCheng
[not found] ` <42f035f0.13006336.4667.1893SMTPIN_ADDED@mx.gmail.com>
2005-08-03 5:15 ` Daniel Ann
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=9b7ca6570508021721773d06f0@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=johnsoncheng@qnap.com.tw \
--cc=linuxppc-embedded@ozlabs.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).