From: "Frank Torres" <frank@ingecom.net>
To: "Stephen Torri" <storri@ameritech.net>
Cc: "Linux-Kernel \(Lista Correo\)" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8-ac7: all serial ports not setup
Date: Thu, 23 Aug 2001 09:50:16 +0200 [thread overview]
Message-ID: <004501c12ba8$42f04ff0$66011ec0@frank> (raw)
In-Reply-To: <Pine.LNX.4.33.0108221201210.8546-100000@base.torri.linux>
----- Original Message -----
From: "Stephen Torri" <storri@ameritech.net>
> I am using 2.4.8-ac7 on a Dual P3@450Mhz. The machine has two serial
> ports. ttyS0 & ttyS2 are covered by the first with ttyS1 & ttyS3 covered
> by the second. Now typically in /proc/interrupts only one serial port is
> configured. The IRQs 3 & 4 are shared by the two ports. Its not consistent
> which one gets which IRQ. Sometimes the first has 3 and the second 4.
> Today the situation is reversed. This ofcourse is wreaking havoc on
> setting my pilot for synchronization.
>
Usually, IRQs are assigned when de device is used. So the serial port you
see in /proc/interrupts is the one you're using. If sometimes it takes an
IRQ and sometimes the other it means that the system is using another
device/process which takes one of the two serial ports IRQs.
ttyS0 and ttyS2 usually take IRQ3 and ttyS1 and ttyS3 most of the times take
the IRQ4. You can "force" the serial port to use one IRQ but that's not
recommended because the dinamyc IRQ assignment is one of the advantages of
the modules and drivers. That way one device doesn't own the IRQ if it is
not using it so the other devices can use that IRQ. (I don't know if I make
myself understand, but it's that way). And if you have a device using that
IRQ and tell Linux to assing -only- that IRQ to your serial device (the
"pilot" perhaps?) you could have a conflict between the devices -or- the
system could show you a message telling you the IRQ is being used. I don't
really know exactly.
Any way, to force the serial port to use one IRQ, do it using setserial (man
setserial) or using the serial port config. files (rc.serial and
serial.conf -check inside /etc/rc.d/rc.sysinit where to copy those files-)
but the script rc.serial have errors in some kernel versions so it's better
the first option.
frank
fcnatra@yahoo.com
frank@ingecom.net
prev parent reply other threads:[~2001-08-23 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 16:05 2.4.8-ac7: all serial ports not setup Stephen Torri
2001-08-22 20:42 ` Richard B. Johnson
2001-08-23 7:50 ` Frank Torres [this message]
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='004501c12ba8$42f04ff0$66011ec0@frank' \
--to=frank@ingecom.net \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox