From: "Ian D . Stewart" <idstewart@compuvative.com>
To: Stephen Torri <storri@ameritech.net>
Cc: "D . Stimits" <stimits@idcomm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial Ports
Date: Sat, 22 Sep 2001 12:33:24 -0400 [thread overview]
Message-ID: <20010922123324.A4677@localhost.ameritech.net> (raw)
In-Reply-To: <3B96C783.8BC8E29B@idcomm.com> <Pine.LNX.4.33.0109061624320.1443-100000@base.torri.linux>
In-Reply-To: <Pine.LNX.4.33.0109061624320.1443-100000@base.torri.linux>; from storri@ameritech.net on Thu, Sep 06, 2001 at 16:27:06 -0400
On 2001.09.06 16:27:06 -0400 Stephen Torri wrote:
>
> 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.
As I understand it, /dev/ttyS0-3 are set to industry standard values on
startup (they are not probed). The values can be changed using the
command-line utility setserial. You can specify non-standard values in an
rc.serial conf file which will be read on startup.
The setserial manpage covers this is some detail.
HTH,
Ian
--
"God may have mercy. We will not."
--Senator John S. McCain (R-AZ)
next prev parent reply other threads:[~2001-09-22 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B96C783.8BC8E29B@idcomm.com>
2001-09-06 20:27 ` Serial Ports Stephen Torri
2001-09-07 14:12 ` Stuart MacDonald
2001-09-22 16:33 ` Ian D . Stewart [this message]
2001-09-05 20:04 Stephen Torri
2001-09-06 14:12 ` Stuart MacDonald
-- strict thread matches above, loose matches on Subject: below --
1999-12-10 19:09 Serial ports Naushit Sakarvadia
1999-12-10 12:18 Grant Carter
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=20010922123324.A4677@localhost.ameritech.net \
--to=idstewart@compuvative.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stimits@idcomm.com \
--cc=storri@ameritech.net \
/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.