All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, alex.williamson@hp.com,
	Will Newton <will.newton@gmail.com>
Subject: Re: [PATCH] serial 8250: tighten test for using backup timer
Date: Tue, 26 Aug 2008 10:58:45 -0700	[thread overview]
Message-ID: <20080826105845.6ddf1107.akpm@linux-foundation.org> (raw)
In-Reply-To: <200808261045.34699.david-b@pacbell.net>

On Tue, 26 Aug 2008 10:45:34 -0700
David Brownell <david-b@pacbell.net> wrote:

> > > Also, how serious is the problem which is being fixed here?  It
> > > _sounds_ like it's of the "fatal for people who have that hardware"
> > > variety, in which case we should get this into 2.6.27 and probably
> > > 2.6.26.x.  Not sure about 2.5.26.x though - the patch doesn't apply
> > > there, but I didn't check whether this is due to functional changes.
> >
> > For users of this version of this particular UART IP it is fatal. From
> > looking at the git history it looks like the original patch went into
> > 2.6.26 so it might also affect that kernel.
> 
> Second that:  serial-8250-tighten-test-for-using-backup-timer.patch
> (from MMOTM) in mainline sooner-not-later seems right.

ok, if you think so...

I still have an unanswered question out there about the init_timer()
handling in that area of the driver but afaict this patch didn't make any
of it worse than it already is.

> My own exposure to this is that the UART on DaVinci hardware, which
> TI allegedly derived from its original 16550 logic, has periodically
> gone from working to unusable with the mainline 8250.c ... and back
> and forth a bunch.  Currently it's "unusable", a regression from some
> previous versions.  With this patch from Alex, it's usable.
> 
> Of course there are a bunch of arch/arm/mach-davinci patches needed
> to make that platform more functional in mainline.  I expect they'll
> probably merge in the 2.6.28-rc0 window.  Meanwhile, running out of
> ramdisk with a serial console should at least work right!  :)
> 


  reply	other threads:[~2008-08-26 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 17:45 [PATCH] serial 8250: tighten test for using backup timer David Brownell
2008-08-26 17:58 ` Andrew Morton [this message]
2008-08-26 18:10   ` Will Newton
2008-09-01 13:36   ` Will Newton
2008-09-01 17:56     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-03-19 16:50 Alex Williamson
2008-08-05 11:44 ` Will Newton
2008-08-05 20:06   ` Alex Williamson
2008-08-06 10:53     ` Will Newton
2008-08-11 21:32       ` Andrew Morton
2008-08-12  8:32         ` Will Newton

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=20080826105845.6ddf1107.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alex.williamson@hp.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will.newton@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 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.