mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Torri <storri@ameritech.net>
To: "D. Stimits" <stimits@idcomm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial Ports
Date: Thu, 6 Sep 2001 16:27:06 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0109061624320.1443-100000@base.torri.linux> (raw)
In-Reply-To: <3B96C783.8BC8E29B@idcomm.com>

On Wed, 5 Sep 2001, D. Stimits wrote:

> Make sure your bios is set to "not plug-n-play aware". I have a
> Supermicro Dual P3 board that works fine (actually, 2) with serial mice.
> In the case of the modem serial port, I have to use setserial to get the
> characteristics I want, plus the setserial options seem to require
> speed_normal and skip_test to work correctly. Incidentally, if your
> board is based on the i840 chipset, you'll have to run noapic or it will
> die under some circumstances, such as heavy disk load, or rapid
> mount/umount of any filesystem (even a cdrom).
>
> D. Stimits, stimits@idcomm.com

I have noticed that serial ports change IRQ to either 3 or 4. There is no
reason for this behavior. I have created a perl script to create a log
containing the irqs assigned and their ioports. Is there anything else I
could log that might unmask the problem?

So far if the serials are assigned to IRQ 4 then the sync with the palm
pilot doesn't work (/dev/pilot = /dev/ttyS0). If its IRQ 3 then it does.

Stephen


       reply	other threads:[~2001-09-07  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B96C783.8BC8E29B@idcomm.com>
2001-09-06 20:27 ` Stephen Torri [this message]
2001-09-07 14:12   ` Stuart MacDonald
2001-09-22 16:33   ` Ian D . Stewart
2001-09-05 20:04 Stephen Torri
2001-09-06 14:12 ` 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=Pine.LNX.4.33.0109061624320.1443-100000@base.torri.linux \
    --to=storri@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stimits@idcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®