public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, Mathias Adam <a2@adamis.de>
Subject: Re: make 16C950 UARTs work
Date: Wed, 2 Aug 2006 16:31:46 -0400	[thread overview]
Message-ID: <20060802203146.GB23389@redhat.com> (raw)
In-Reply-To: <20060802201723.GC7173@flint.arm.linux.org.uk>

On Wed, Aug 02, 2006 at 09:17:23PM +0100, Russell King wrote:
 > On Wed, Aug 02, 2006 at 03:49:38PM -0400, Dave Jones wrote:
 > > This patch has been submitted a number of times, and doesn't seem
 > > to get any upstream traction, which is a shame, as it seems to work
 > > for users, and I keep inadvertantly dropping it from the Fedora
 > > kernel everytime I rebase it.
 > 
 > As I've said, I'm ignoring all 950 patches because I don't know what
 > works and what doesn't

Well, thanks for the reply.

 > , and it's highly likely that applying one fix
 > for one card breaks already working fixes for other cards because
 > they have different crystals fitted, thereby requiring different
 > register settings.

FWIW, we've had that patch in Fedora (most of the time), since 2.6.13,
and I don't recall seeing any other serial breakage ports (on this,
or any UART for that matter).

 > My requests for the broken BT hardware which dwmw2 promised me which
 > the original requests were based upon have consistently resulted in
 > promise of action but no real action.
 > 
 > Basically, either I need 950 based hardware so I can at least validate
 > that new fixes don't break existing setups, or someone else needs to
 > be in this position and take on the responsibility for reviewing and
 > testing future 950 based patches.
 > 
 > I don't believe that there are sufficient users out there who follow
 > the kernel to allow the "dump in -mm and wait a bit to see if anyone
 > complains" solution will work.

Still, leaving a patch out in the cold for 11 months, when we know it
at least makes things work for some users strikes me as wrong.
If we took this approach with every driver, we'd end up not supporting
the majority of things we support today.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-08-02 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 19:49 make 16C950 UARTs work Dave Jones
2006-08-02 20:17 ` Russell King
2006-08-02 20:31   ` Dave Jones [this message]
2006-08-02 20:47     ` Russell King
2006-08-02 22:59   ` Theodore Tso
2006-08-07 23:20     ` Mathias Adam
2006-08-09  8:31       ` Russell King
2006-08-02 22:08 ` Alan Cox
2006-08-02 21:59   ` Russell King
2006-08-02 23:28     ` Petr Vandrovec

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=20060802203146.GB23389@redhat.com \
    --to=davej@redhat.com \
    --cc=a2@adamis.de \
    --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