From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@lists.ozlabs.org>
Subject: Curious serial slowdown
Date: Tue, 11 May 2010 08:18:25 +0200 [thread overview]
Message-ID: <44001372909D4EAD8181655EEA5E416C@LPSC0173W> (raw)
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Hello all,
I'm looking for hints on a curious problem.
I have a working kernel on a custom embedded device and it works fine.
We came up with a variation of the device with a few hardware changes, one
of them being the number of serial ports that goes from 4 to 2.
In order to save time I tried my current kernel. When I boot the custom
bootlader behaves the same, then the kernel boot behaves the same, but then
once usermode is reached (the message "init started: BusyBox..."), the new
card console display crawls to a halt (about one character per second
instead of 115000 bauds !!!). But the card goes at normal speed as an ssh
connection shows.
So my question is: is it caused by the fact that there are 2 missing serial
ports ? Will making a new kernel with the correct hardware definition solve
it ?
--
Guillaume Dargaud
http://www.gdargaud.net/
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3562 bytes --]
reply other threads:[~2010-05-11 7:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44001372909D4EAD8181655EEA5E416C@LPSC0173W \
--to=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.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