From: Gordon McNutt <gmcnutt@ridgerun.com>
To: linux-mips@oss.sgi.com
Subject: sgiserial.c
Date: Mon, 09 Oct 2000 14:32:26 -0600 [thread overview]
Message-ID: <39E22B5A.66587B5A@ridgerun.com> (raw)
I'm trying to get the Indy's serial port to drive a peripheral card at
115200 baud. It appears to work OK at 9600 baud (the serial port that is
-- the card expects 115200 baud).
First of all, it lookslike the baud_table (in sgiserial.c) used to
convert termios.c_cflag bits to a numeric baud rate was outdated so I
fixed it up. Didn't help. It looks like transmit interrupts are
occurring and the driver is trying to write them to the chip (one byte
per interrupt..? ok, whatever works), but the other end usually isn't
getting anything. When reading, the Indy seems to get bytes but they
don't look good.
BTW, I've tried compiling the kernel without console support on the
serial line but I still get some console messages during boot (at 9600
baud). Haven't looked too hard at that yet... When I force everybody to
use 115200 baud (via a hack) I don't see the console messages (yes, I
changed minicom to expect 115200 in this case). It just seems like the
chip is not correctly being set to operate at 115200 -- even when
I force it to try.
Has anybody else tried to make the serial port speak 115200?
Thanks,
--Gordon
next reply other threads:[~2000-10-09 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-09 20:32 Gordon McNutt [this message]
2000-10-10 3:13 ` sgiserial.c Marcus Herbert
2000-10-10 3:19 ` sgiserial.c Keith Owens
2000-10-10 3:45 ` sgiserial.c Ralf Baechle
2000-10-10 9:41 ` sgiserial.c Alan Cox
2000-10-10 9:41 ` sgiserial.c Alan Cox
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=39E22B5A.66587B5A@ridgerun.com \
--to=gmcnutt@ridgerun.com \
--cc=linux-mips@oss.sgi.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.