From: "Stuart MacDonald" <stuartm@connecttech.com>
To: Ulrich Hertlein <u.hertlein@sandbox.in-berlin.de>,
linux-serial@vger.kernel.org
Subject: Re: UART not generating MSR-change (or any) interrupt
Date: Tue, 25 Jun 2002 09:01:28 -0400 [thread overview]
Message-ID: <003b01c21c48$6b543920$294b82ce@connecttech.com> (raw)
In-Reply-To: 200206242137.12029.u.hertlein@sandbox.in-berlin.de
From: "Ulrich Hertlein" <u.hertlein@sandbox.in-berlin.de>
> UART of the requested port. For I/O base and IRQ 'setserial' reports the
> expected standard values (COM1=0x3f8,IRQ=4 COM2=0x2f8,IRQ=3 ...) and I'm
[snip]
> IRQ=3,COM2.
Motherboard serial ports are generally still handled as ISA devices;
they cannot share interrupts. I suspect that your uart is generating
interrupts that are getting caught by the serial driver, which is
ignoring them since it doesn't know about your hardware. Try
# setserial uart none /dev/ttyS1
(synatx may be off slightly), to remove the conflict.
..Stu
prev parent reply other threads:[~2002-06-25 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 19:37 UART not generating MSR-change (or any) interrupt Ulrich Hertlein
2002-06-25 13:01 ` Stuart MacDonald [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='003b01c21c48$6b543920$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=linux-serial@vger.kernel.org \
--cc=u.hertlein@sandbox.in-berlin.de \
/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