From: Tom Rini <trini@kernel.crashing.org>
To: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Allow ns16550.c to get base baud from rs_table instead of BAUD_BASE
Date: Wed, 24 Aug 2005 11:35:20 -0700 [thread overview]
Message-ID: <20050824183520.GC15735@smtp.west.cox.net> (raw)
In-Reply-To: <20050823224702.GA3864@siegfried.thelikelysolution.ca>
On Tue, Aug 23, 2005 at 04:47:02PM -0600, Grant Likely wrote:
> [PATCH] Allow ns16550.c to get base baud from rs_table instead of BAUD_BASE
>
> REPOST: fixed formating problems in original patch
>
> Modifies serial_init to get base baud rate from the rs_table entry instead
> of BAUD_BASE. Will default back to BAUD_BASE if base_baud is not set.
>
> This patch eliminates duplication between the SERIAL_PORT_DFNS macro and
> BAUD_BASE. Without the patch, if a port set the baud rate in
> SERIAL_PORT_DFNS, but did not update BASE_BAUD, the BASE_BAUD value
> would still be used.
>
> Rather; serial_init() should look first in SERIAL_PORT_DFNS and use
> BASE_BAUD as a backup.
>
> Signed-off-by: Grant Likely <grant.likely@gdcanada.com>
With everything in-tree, this is fine as baud_base is always set to
BASE_BAUD, but I'm wondering why this was done. Did you do a port and
not follow on this? It looks like today you could get away without
defining BASE_BAUD correctly (8250_early uses and needs this to be
correct, but I don't think this is frequently used, yet). But I'm not
sure what we gain here. Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-08-24 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 22:47 [PATCH] Allow ns16550.c to get base baud from rs_table instead of BAUD_BASE Grant Likely
2005-08-24 18:35 ` Tom Rini [this message]
2005-08-24 21:35 ` Grant Likely
2005-08-24 21:47 ` Tom Rini
2005-08-24 22:17 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 22:07 Grant Likely
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=20050824183520.GC15735@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@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 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.