From: Ralf Baechle <ralf@linux-mips.org>
To: Ricardo Mendoza <ricmm@kanux.com>
Cc: Martin Michlmayr <tbm@cyrius.com>, linux-mips@linux-mips.org
Subject: Re: IP32: serial console broken with current git
Date: Wed, 26 Sep 2007 13:02:37 +0100 [thread overview]
Message-ID: <20070926120237.GB24426@linux-mips.org> (raw)
In-Reply-To: <46F93692.4050801@kanux.com>
On Tue, Sep 25, 2007 at 12:25:54PM -0400, Ricardo Mendoza wrote:
> Martin Michlmayr wrote:
> > With current git (and 2.6.23-rc1), nothing shows up on the serial
> > console on IP32. Ricardo Mendoza commented on this on IRC:
> >
> >> I think it was that using iobase member in the plat_serial8250_port
> >> struct was not working, swapping to membase gave console messages
> >> but kind of stopped printing messages at some point (further in than
> >> first line of C tho)
> >
> > He also sent me a patch to test. With this patch, I get serial
> > console output - but only until:
> >
> > | Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> > | serial8250.0: ttyS0 at MMIO 0x0 (irq = 53) is a 16550A
> > | console [ttyS0] enabled
> >
> > Maybe Ricardo can post his patch for comments and someone can look
> > into the second issue.
>
>
> The patch is the following, please ignore the rewrite of the MACE_PORT
> specifications, those are not needed (I don't remember why I did that at
> all).
>
> As Martin said, the output stops on the 'console [ttyS0] enabled'
> message. I don't know much about the serial code internals but I presume
> something is getting trashed on the console setup.. or perhaps it's just
> something really dumb like a missing call or something. Someone
> enlightened in the issue can perhaps shed a light.
The membase part of it looks right.
Ralf
prev parent reply other threads:[~2007-09-26 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 18:24 IP32: serial console broken with current git Martin Michlmayr
2007-09-25 16:25 ` Ricardo Mendoza
2007-09-26 12:02 ` Ralf Baechle [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=20070926120237.GB24426@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ricmm@kanux.com \
--cc=tbm@cyrius.com \
/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.