From: "Stuart MacDonald" <stuartm@connecttech.com>
To: <JosMHinkle@netscape.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel 2.4.19 failure to access a serial port
Date: Thu, 15 Aug 2002 10:47:51 -0400 [thread overview]
Message-ID: <007101c2446a$bb20b420$294b82ce@connecttech.com> (raw)
In-Reply-To: 79B43166.1160898F.0BD32098@netscape.net
From: <JosMHinkle@netscape.net>
> Slight expansion: A system with two serial ports on ttyS0 and ttyS1
> and a hardware modem on ttyS2 was not serviced properly in kernel
> 2.4.19 and some earlier ones. The modem at ttyS2 was fairly well
> ignored. The interrupt requests used were ttyS0:irq4 ttyS1:irq3
> ttyS2:irq10
>
> Temporary fix:
> In drivers/char/serial.c at the directive "#ifdef CONFIG_PCI"
> the assumption is made that interrupt requests are shared and
> there are more than four serial ports. That is not necessarily
> true, and the directives defeat the options set in configuration.
> The solution here was to comment out #define CONFIG_SERIAL_SHARE_IRQ
> and CONFIG_SERIAL_MANY_PORTS and recompile.
>
> #ifdef CONFIG_PCI
> #define ENABLE_SERIAL_PCI
> /*** Commented out to allow unshared IRQ's on ttyS0-ttyS3
> #ifndef CONFIG_SERIAL_SHARE_IRQ
> #define CONFIG_SERIAL_SHARE_IRQ
> #endif
> #ifndef CONFIG_SERIAL_MANY_PORTS
> #define CONFIG_SERIAL_MANY_PORTS
> #endif
> ***/
> #endif
This fix breaks the driver in a fundamental way. SHARE_IRQ and
MANY_PORTS are turned on if CONFIG_PCI is on because a) pci drivers
*must* share interrrupts and b) generally serial ports that are behind
a pci bus are multiport boards.
The effect of MANY_PORTS is merely to increase the size of the static
array that holds the serial port state. Whether or not it is on should
not have affected your problem. (I believe the smallest size of the
array is 4, for ttyS0-3.)
SHARE_IRQ should also not have affected your problem, since your modem
is configured at irq 10, and you haven't mentioned that anything else
is also using irq 10. If turning off this option "fixes" your problem
then that should indicate that your setup isn't what you think it is;
either the modem isn't really at irq 10 (unclear from your previous
post, and my lack of isapnp knowledge) and/or something else is also
using the same irq your modem is on.
Please see my previous email, and try some of my suggestions. The one
about reserving the irq in bios for isa-only use is critical.
..Stu
--
We make multiport serial boards.
<http://www.connecttech.com>
(800) 426-8979
next prev parent reply other threads:[~2002-08-15 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 22:43 Linux kernel 2.4.19 failure to access a serial port JosMHinkle
2002-08-15 14:47 ` Stuart MacDonald [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-16 7:01 JosMHinkle
2002-08-14 3:49 JosMHinkle
2002-08-14 13:57 ` 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='007101c2446a$bb20b420$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=JosMHinkle@netscape.net \
--cc=linux-kernel@vger.kernel.org \
/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