From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, miles@gnu.org, dwmw2@redhat.com
Subject: Re: [SERIAL] change_speed -> settermios change
Date: Sun, 05 Jan 2003 23:02:18 -0800 (PST) [thread overview]
Message-ID: <20030105.230218.84729944.davem@redhat.com> (raw)
In-Reply-To: <20030103161916.A19992@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Fri, 3 Jan 2003 16:19:16 +0000
I have one concerns surrounding the three drivers mentioned above.
Currently, they blindly use uart_get_baud_rate() without limiting the
maximum baud rate. Since the baud rate will be limited (by the
hardware), we must limit the resulting baud rate must be reflected
back into the termios c_cflag member.
Hmmm, maybe it's a better idea to store the min/max in the UART port
structure and have the upper layer do the limiting before we call
down into the driver?
next prev parent reply other threads:[~2003-01-06 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:19 [SERIAL] change_speed -> settermios change Russell King
2003-01-06 7:02 ` David S. Miller [this message]
2003-01-06 11:36 ` Russell King
2003-01-06 7:49 ` Miles Bader
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=20030105.230218.84729944.davem@redhat.com \
--to=davem@redhat.com \
--cc=dwmw2@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=rmk@arm.linux.org.uk \
/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.