public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Gerd Hoffmann <kraxel@suse.de>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Yinghai.Lu@Sun.COM, bryan.wu@analog.com, dilinger@queued.net,
	kraxel@redhat.com, lethal@linux-sh.org,
	rgetz@blackfin.uclinux.org, vapier.adi@gmail.com
Subject: Re: [PATCH] kernel/printk.c: Concerns about the console handover
Date: Fri, 21 Sep 2007 14:43:32 +0100	[thread overview]
Message-ID: <20070921134331.GC20277@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64N.0709211428300.2724@blysk.ds.pg.gda.pl>

On Fri, Sep 21, 2007 at 02:36:50PM +0100, Maciej W. Rozycki wrote:
> On Fri, 21 Sep 2007, Andrew Morton wrote:
> 
> > It would be useful to have some basic information like: Which kernel
> > version was this found in?  Which kernel version last worked?
> 
>  The kernel used was a 2.6.23-rc5 snapshot from Sep 4th, 2007 taken from 
> the linux-mips.org tree (as stated by the revision of the patch provided).  
> There is no version that can be considered working as the change to add 
> the printk() to register_console() went in before drivers/serial/zs.c was 
> added and the old drivers/tc/zs.c driver might have been to sloppy to 
> handle such bits as the transmitter enable properly.  I may investigate.
> 
>  Chances are nobody tried any version of the kernel from the period 
> between the printk() was added and drivers/tc/zs.c removed with the 
> DECstation; I have not.
> 
>  Anyway, I did confirm keeping the transmitter enabled all the time makes 
> the problem go away.

I suspect the correct fix for this is to take the fix in the ARM tree
for serial_core's console initialisation, and ensure that zs.c handles
the power management of the port (enabling/disabling transmitter)
in the power management callback.

You can find the fix in the mbox archive:

 http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cut/arm:devel.mbox

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

  reply	other threads:[~2007-09-21 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20 17:28 [PATCH] kernel/printk.c: Concerns about the console handover Maciej W. Rozycki
2007-09-21  8:03 ` Andrew Morton
2007-09-21 12:42   ` Gerd Hoffmann
2007-09-21 13:06     ` Russell King
2007-09-21 13:22       ` Gerd Hoffmann
2007-09-21 13:28     ` Maciej W. Rozycki
2007-09-21 13:36   ` Maciej W. Rozycki
2007-09-21 13:43     ` Russell King [this message]
2007-09-21 14:36       ` Maciej W. Rozycki
2007-09-21 14:45         ` Russell King
2007-09-24 17:14           ` Maciej W. Rozycki
     [not found] <95y0Q-7JD-5@gated-at.bofh.it>
2007-09-21  9:24 ` Bodo Eggert

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=20070921134331.GC20277@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=Yinghai.Lu@Sun.COM \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.wu@analog.com \
    --cc=dilinger@queued.net \
    --cc=kraxel@redhat.com \
    --cc=kraxel@suse.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox