From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix a problem with 8250 UARTs on PPC
Date: Fri, 12 Dec 2003 19:35:57 +0000 [thread overview]
Message-ID: <20031212193557.A12873@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031212190012.GT23731@stop.crashing.org>; from trini@kernel.crashing.org on Fri, Dec 12, 2003 at 12:00:12PM -0700
On Fri, Dec 12, 2003 at 12:00:12PM -0700, Tom Rini wrote:
> Hello. As part of the patch I sent that went into 2.6.0-test7 (Nat Semi
> SuperI/O chips on PPCs at least have a number of different divisors),
> the following should have been done as well, but wasn't. If we don't
> change the divisor, we don't want to change what we claim as the uart
> clock either. Without this I don't get a usable serial console on my
> Motorola Sandpoint.
Thanks, applied.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2003-12-12 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 19:00 [PATCH] Fix a problem with 8250 UARTs on PPC Tom Rini
2003-12-12 19:35 ` Russell King [this message]
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=20031212193557.A12873@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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