All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: Fw: [Patch] Some updates to serial-5.05
Date: Thu, 15 Nov 2001 00:10:16 +0000	[thread overview]
Message-ID: <20011115001016.C19575@flint.arm.linux.org.uk> (raw)
In-Reply-To: <00df01c16d23$b409ab20$294b82ce@connecttech.com>
In-Reply-To: <00df01c16d23$b409ab20$294b82ce@connecttech.com>; from stuartm@connecttech.com on Wed, Nov 14, 2001 at 10:47:44AM -0500

On Wed, Nov 14, 2001 at 10:47:44AM -0500, Stuart MacDonald wrote:
> Same patches, attached inline to avoid OE mangling.

I've merged the simple bits of this by hand with my serial CVS.  As I
said in a previous mail here, I'm not taking on the maintainence of the
existing serial.c driver.  Therefore, these comments apply to the
new serial driver, not the existing drivers.

> > patch-kernel: Adds 485 ioctls to the kernel proper

Not applied.

> > patch-serial-485: Adds 485 line mode switiching functionality to the
> > serial driver. Note: this is not 485 protocol-level support, but
> > electrical-level support.

Not applied.

These two I'd rather waited until we've got the driver merged into 2.5,
at which point I'd rather have a patch against the new driver.

> > patch-serial-16850: Adds detection of the XR16C2850.

Applied.

> > patch-serial-fctr: Fixes a bug where serial-5.05 wasn't preserving an
> > important bit in the fctr register when setting fifo triggers.

Applied.

> > patch-serial-devfs: Driver now reports the /dev entries in a manner
> > consistent with how they are created. Yes, we have had customers who
> > were thrown off by the discrepancy between ttyS00 and ttyS0.

I don't actually printk() the serial ports that have been discovered at
boot time in the new serial CVS.  If people scream enough, I could be
persuaded.  I'm currently of the opinion that they're noise, and if
we're really interested in them, we've got a userspace tool to do it
for us: setserial -bg /dev/ttyS* 

> > patch-serial-24x: serial-5.05 now finds our MULTISERIAL class boards.
> > Also adds serial_compat.h for all 2.4.x kernels I've tested it with.
> > This is necessary to compile in 2.4.x kernels.

Only the MULTISERIAL support applied - 2.4 has the PCI class definitions,
so when the new driver is merged, we already have the definitions.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2001-11-15  0:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 15:47 Fw: [Patch] Some updates to serial-5.05 Stuart MacDonald
2001-11-14 15:57 ` Jeff Garzik
2001-11-14 16:30   ` Stuart MacDonald
2001-11-14 16:35     ` Jeff Garzik
2001-11-14 18:46       ` Stuart MacDonald
2001-11-14 18:57         ` Jeff Garzik
2001-11-14 19:24           ` Stuart MacDonald
2001-11-14 17:04 ` Roman Kurakin
2001-11-15  0:10 ` Russell King [this message]
2001-11-15  0:25   ` Jeff Garzik
2001-11-15 15:23   ` 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=20011115001016.C19575@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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 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.