From: Justin Wojdacki <justin.wojdacki@analog.com>
To: linux-kernel@vger.kernel.org
Subject: Serial Port Speed Change, 2.4.10->2.4.16
Date: Thu, 31 Oct 2002 12:37:46 -0800 [thread overview]
Message-ID: <3DC1949A.B1B862A1@analog.com> (raw)
Probably a dumb question, but I have a MIPS-based system that I'm
running Linux on, and when moving from 2.4.10 kernel to 2.4.16 kernel,
the # of characters per second on the serial console has dropped
significantly.
The serial port used is a 16450 clone (it's built in to the processor,
so no, I can't upgrade it). It's programmed to run at 9600 baud, 8N1.
There's clearly no problem with the characters themselves. But while I
can push ~1000 CPS under 2.4.10, I can only push ~100 CPS under
2.4.16. I've noticed that the CPS of the console is constant in
2.4.16, regardless of serial port speed.
Can anyone lend any insight into why I would've lost 90% of my serial
port throughput moving between these two revs of the kernel?
--
-------------------------------------------------
Justin Wojdacki
justin.wojdacki@analog.com (408) 350-5032
Communications Processors Group -- Analog Devices
reply other threads:[~2002-10-31 20:31 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=3DC1949A.B1B862A1@analog.com \
--to=justin.wojdacki@analog.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome