From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "Stephen Torri" <storri@ameritech.net>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Serial Ports
Date: Thu, 6 Sep 2001 10:12:05 -0400 [thread overview]
Message-ID: <014201c136dd$e8a6c380$294b82ce@connecttech.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109051603160.2980-100000@base.torri.linux>
From: "Stephen Torri" <storri@ameritech.net>
> Should serial ports be assigned interrupts on start up or are they
> assigned when they are used? I have been tracking the serial ports on my
> Supermicro Dual P3 Board for a few days now. At times I cannot get them to
> work so I can syncronize a Palm Pilot via the serial port.
On-board serial ports are given either the standard irqs, or the
irqs that you specify in the bios. ISA and other non-self-identifying-
bus-based ports will be given the irqs you specify in the configuration
of the device. PCI and other self-identifying-bus-based ports will
be assigned free or sharable irqs by the bios/os. All serial hardware
is assigned an irq. This is the hardware level.
I think what you're asking is "When I cat /proc/irq, should I see the
serial ports listed at boot, or only after I've used them?" The answer
to that is that the standard serial driver only registers to use the
irq that has been assigned, when it needs to use it. So if you check
before usage, you won't see your ports.
..Stu
next prev parent reply other threads:[~2001-09-06 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 20:04 Serial Ports Stephen Torri
2001-09-06 14:12 ` Stuart MacDonald [this message]
[not found] <3B96C783.8BC8E29B@idcomm.com>
2001-09-06 20:27 ` Stephen Torri
2001-09-07 14:12 ` Stuart MacDonald
2001-09-22 16:33 ` Ian D . Stewart
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='014201c136dd$e8a6c380$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--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