linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 14:15:45 +0900	[thread overview]
Message-ID: <9b7ca65705080222154ec23c2e@mail.gmail.com> (raw)
In-Reply-To: <42f035f0.13006336.4667.1893SMTPIN_ADDED@mx.gmail.com>

A Ha. That's the question I've asked kumar earlier today. Having
inserted that myself it worked also. Still wondering why tho...

On 8/3/05, JohnsonCheng <johnsoncheng@qnap.com.tw> wrote:
> Actually, I had reviews all article about "serial console", just know I h=
ave
> to use LEVEL for interrupt, not EDGE. Unfortunately the default interrupt
> setting for kernel is with LEVEL, IRQ_SENSE_LEVEL, I think I don't need t=
o
> modify it.
> But I found I add ASYNC_SKIP_TEST flag to UART in sandpoint.h can fix my
> problem.
>=20
> Thanks,
> Johnson Cheng
>=20
> -----Original Message-----
> From: linuxppc-embedded-bounces@ozlabs.org
> [mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Daniel Ann
> Sent: Wednesday, August 03, 2005 8:22 AM
> To: JohnsonCheng
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: A PPC kernel issue with UART ??
>=20
> Johnson,
>=20
> 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.
>=20
> BTW, My problem was with interrupt setting.
> Daniel.
>=20
> On 8/2/05, JohnsonCheng <johnsoncheng@qnap.com.tw> wrote:
> >
> >
> > Dear All,
> >
> >
> >
> > I meet a wired UART problem on linux-2.6 with MPC8241 chip.
> >
> >
> >
> > My Environment is as following:
> >
> > CPU: MPC8241
> >
> > Linux: 2.6.12.3
> >
> > COM1 offset: 0x4500, COM2 offset: 0x4600
> >
> >
> >
> > When I booting my rootfs, it hangs at following message:
> >
> > RAMDISK: Compressed image found at block 0
> >
> > VFS: Mounted root (ext2 filesystem) readonly.
> >
> > Freeing unused kernel memory: 104k init
> >
> > EXT2-fs warning: checktime reached, running e2fsck is recommended
> >
> >
> >
> > I had add printk in tty_write() of drivers/char/tty_io.c, the message f=
rom
> > rootfs have printed.
> >
> > The conclusion is that message can be printed by printk() in linux kern=
el,
> > but can't be printed by printf() in user mode. I think it must be
> something
> > wrong for my UART configurations, does anybody know it??
> >
> >
> >
> >
> >
> > Best Regards,
> >
> > Johnson Cheng
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> >
>=20
>=20
> --
> Daniel
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20


--=20
Daniel

      parent reply	other threads:[~2005-08-03  5:15 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
2005-08-03  3:11   ` JohnsonCheng
     [not found]   ` <42f035f0.13006336.4667.1893SMTPIN_ADDED@mx.gmail.com>
2005-08-03  5:15     ` Daniel Ann [this message]

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=9b7ca65705080222154ec23c2e@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).