public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Serial: updated serial drivers
Date: Sun, 7 Jul 2002 10:01:48 +0000 (UTC)	[thread overview]
Message-ID: <ag93ic$hcb$1@ncc1701.cistron.net> (raw)
In-Reply-To: 20020707010009.C5242@flint.arm.linux.org.uk

In article <20020707010009.C5242@flint.arm.linux.org.uk>,
Russell King  <rmk@arm.linux.org.uk> wrote:
> - remove callout functionality, which has been marked as such for
>   a few years now.  tytso mentions that the only program this
>   might break is minicom, which should be fixed.

Minicom doesn't care which port you use. It might be that some
people have saved configs of 6 years old that still contain
references to a cua device, but that's a problem any serial
program has.

>From the manpage of any recent minicom:

       Serial port setup
          *A - Serial device
               /dev/tty1   or   /dev/ttyS1   for   most   people.
               /dev/cua<n> is still possible under linux, but not
               recommended  any  more  because  these devices are
               obsolete and many  newly  installed  systems  with
               kernel  2.2.x  don't  have them.  Use /dev/ttyS<n>
               instead.

Mike.


  reply	other threads:[~2002-07-07  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-07  0:00 Serial: updated serial drivers Russell King
2002-07-07 10:01 ` Miquel van Smoorenburg [this message]
2002-07-15 10:03 ` William Lee Irwin III
2002-07-15 11:01   ` William Lee Irwin III
2002-07-15 11:24     ` Russell King
2002-07-15 18:17       ` William Lee Irwin III
2002-07-15 14:25   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2002-07-07 14:15 Marko Kohtala

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='ag93ic$hcb$1@ncc1701.cistron.net' \
    --to=miquels@cistron.nl \
    --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