From: Tom Rini <trini@kernel.crashing.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: dwmw2@shinybook.infradead.org, Linuxppc-embedded@ozlabs.org
Subject: Re: Possible CPM2 SMC bug
Date: Thu, 4 Nov 2004 11:56:30 -0700 [thread overview]
Message-ID: <20041104185629.GD13456@smtp.west.cox.net> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B06DBA1@ismail.innsys.innovsys.com>
On Mon, Oct 25, 2004 at 06:25:20PM -0500, Rune Torgersen wrote:
> The output from INIT (sysvinit 2.85) is garbled when runninn on kernel 2.6.9 and using SMC1 as the console port
> When runnign SCC1 as console port, no garbling occurs.
> Only the output from INIT seems to be garbled. And only output that does not show up on netconsole.
>
> The problem was not present in 2.6.7, which used the old smc/scc uart drivers.
It sounds like the clock rate isn't quite right on SMC1. Any chance
you've worked this problem out more? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-11-04 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 23:25 Possible CPM2 SMC bug Rune Torgersen
2004-11-04 18:56 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 20:57 Rune Torgersen
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=20041104185629.GD13456@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=dwmw2@shinybook.infradead.org \
--cc=runet@innovsys.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 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).