public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Caleb Tennis <caleb@aei-tech.com>
To: "Stuart MacDonald" <stuartm@connecttech.com>,
	<linux-kernel@vger.kernel.org>, <tytso@mit.edu>
Subject: Re: [PATCH] serial.c to support ConnectTech Blueheat PCI
Date: Fri, 10 Aug 2001 12:21:31 -0500	[thread overview]
Message-ID: <01081012213100.08017@pete.aei-tech.com> (raw)
In-Reply-To: <01081010190800.03758@pete.aei-tech.com> <017801c121b5$e254f3e0$294b82ce@connecttech.com>
In-Reply-To: <017801c121b5$e254f3e0$294b82ce@connecttech.com>

On Friday 10 August 2001 11:02, Stuart MacDonald wrote:

> This patch is maintained by me; it applies to 5.05. I'm not sure how
> 5.05[abc] are different from vanilla 5.05 though.

I'm quite pleased at the support ConnectTech has for this product.  We are 
planning on purchasing more in the future.

>
> The reason this patch hasn't been seen on lkml is that I prefer
> to have all the serial driver patches go through Ted (T'so the
> serial driver maintainer) first. He's rejected this patch once
> already on the basis that it adds specific board functionality to
> the driver, which he's trying to avoid. I resubmitted it Jun 27 2001
> with a lengthy explanation that all boards with half duplex and slave
> multiplex functionality would have to have some method of doing the
> switching between the modes, and that this isn't specific to our
> products. I haven't heard back from him since.

I originally applied the ConnectTech patch a few months ago to a 2.2.19 
kernel.  I ran into a lot of problems related to the serial driver 5.05 
having some errors in it.  it would compile just fine as as module, but not 
when integrated into the kernel.  There were almost 20 patches to the serial 
driver up on sourceforge fixing most of these problems - and they took care 
of the situation.  After looking at the sourceforge site, it seemed like Ted 
Tso isn't actively maintaining the serial driver anymore (though I noticed 
activity from him on other projects he supports, like e2fsprogs) and my 
assumption was that he was busy.  I had noticed that in the 2.4 series, some 
modifications had been made to the serial driver (hence the "abc" 
progression), and thought it may be valuable to submit a patch related to the 
latest kernel.

There really isn't a good way around this patch - I understand Ted's concern 
on board specific functionality, but it is quite extendable to other 485/232 
combination boards as well.  I sure hope it makes it into the kernel at some 
point, but if not I'll continue hand patching away :)

> Caleb: I appreciate the effort, thanks.

Not a problem - it was a fun way to spend a day upgrading to 2.4.  In fact, 
the serial driver was the only snag I ran into during the upgrade process.

-- 
Caleb Tennis
Analytical Engineering
2555 Technology Blvd
Columbus, IN 47201

  parent reply	other threads:[~2001-08-10 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10 15:19 [PATCH] serial.c to support ConnectTech Blueheat PCI Caleb Tennis
2001-08-10 16:02 ` Stuart MacDonald
2001-08-10 16:09   ` Russell King
2001-08-10 17:21   ` Caleb Tennis [this message]
2001-08-10 17:45     ` Stuart MacDonald

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=01081012213100.08017@pete.aei-tech.com \
    --to=caleb@aei-tech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuartm@connecttech.com \
    --cc=tytso@mit.edu \
    /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