public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Phil Oester <kernel@linuxace.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Luca <kronos@kronoz.cjb.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Garbage on serial console after serial driver loads
Date: Sat, 26 Mar 2005 16:37:29 +0000	[thread overview]
Message-ID: <20050326163729.A23306@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050326155549.GA5881@linuxace.com>; from kernel@linuxace.com on Sat, Mar 26, 2005 at 07:55:49AM -0800

On Sat, Mar 26, 2005 at 07:55:49AM -0800, Phil Oester wrote:
> On Sat, Mar 26, 2005 at 03:10:05PM +0000, Russell King wrote:
> > Doesn't matter.  The problem is that dwmw2's NS16550A patch (from ages
> > ago) changes the prescaler setting for this device so we can use the
> > higher speed baud rates.  This means any programmed divisor (programmed
> > at early serial console initialisation time) suddenly becomes wrong as
> > soon as we fiddle with the prescaler during normal UART initialisation
> > time.
> 
> FWIW, I see the same thing here on some Dell Poweredge boxes:
> 
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> <garbage>
> 
> But intererstingly, on identical boxes, the garbage only appears on
> those hooked up to a PortMaster device - those using a Cyclades never
> display this problem. (???)

Sorry, I don't understand your scenarios.  Can you explain the
circumstances under which you see corruption?

>From the kernel messages you've quoted above, I can only think that
you're not using ttyS0 as the serial console - if you were, my
understanding of this issue would indicate that you should get the
garbage immediately after the line starting "Serial:"

Either my understanding of the cause of this problem is wrong, or
I'm not understanding your setup.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-03-26 16:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 20:24 Garbage on serial console after serial driver loads Luca
2005-03-25 20:38 ` Russell King
2005-03-25 21:01   ` Luca
2005-03-26 10:16     ` Jan Engelhardt
2005-03-26 14:35       ` Luca
2005-03-26 15:10       ` Russell King
2005-03-26 15:55         ` Phil Oester
2005-03-26 16:37           ` Russell King [this message]
2005-03-26 17:19             ` Phil Oester
2005-03-26 17:22             ` Phil Oester
2005-04-13 12:45           ` Paul Slootman
2005-04-18 20:21             ` Phil Oester
2005-04-18 23:14             ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2005-03-27 11:11 Jan Engelhardt
2005-03-28 17:36 Phil Oester
2005-03-28 19:02 ` Russell King
2005-03-28 23:57   ` Dave Airlie
2005-05-03 14:17   ` David Woodhouse
2005-05-03 15:04     ` Phil Oester
2005-05-03 15:11     ` Tom Rini
2005-05-03 15:23       ` David Woodhouse
2005-05-03 16:00         ` Tom Rini
2005-05-03 16:16       ` Tom Rini

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=20050326163729.A23306@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kernel@linuxace.com \
    --cc=kronos@kronoz.cjb.net \
    --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