mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: JosMHinkle@netscape.net
To: linux-kernel@vger.kernel.org
Subject: Linux kernel 2.4.19 failure to access a serial port
Date: Fri, 16 Aug 2002 03:01:45 -0400	[thread overview]
Message-ID: <257D72E0.2F5D0681.0BD32098@netscape.net> (raw)

Summary: In an i586 system with two serial ports and a modem,
Linux fails to access the modem

IRQ 3 and 4 are used by ttyS1 and ttyS0, and IRQ 10 is used by the modem.
There are no conflicts.

I previously mentioned disabling CONFIG_SERIAL_SHARE_IRQ in serial.c
to make it work. (The disabling of CONFIG_SERIAL_MANY_PORTS is an
artifact of no importance).

Stuart, you suggest:
> "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."

CONFIG_PCI must be on because the video card is on that bus.  There is no
conflict between that and the serial ports.

How can this "break the driver in a fundamental way?" This is not
a system that "generally has a multiport board", it is a specific
machine that specifically does not have a multiport board.  To try
to configure it as if it might because some other machines do is just stupid.  I am sure there are many other machines built just like it in
this way, two serial ports and a plugin hardware modem card.

The consideration that the PCI drivers must share interrupts does not
apply here because this patch to make Linux work on this machine is
only in serial.c, nowhere else, and besides, on this system there seems
to be no interrupt sharing elsewhere; correct me if I'm wrong.  The four
items on the PCI bus are:
Host bridge: Silicon Integrated Systems [SiS] 5571
ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX]

Perhaps the IDE controllers share an interrupt, but that is hardly
anything near serial.c

Again, it is very poor practice to offer a configuration item which is 
needed on a system only to silently defeat it internally because "some
systems need that".  I had to waste several days to discover this and
fix it.  If I were not technically adept enough to do it, I would simply
have told the customer that "Linux cannot be installed on your machine".




__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/


             reply	other threads:[~2002-08-16  6:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16  7:01 JosMHinkle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-14 22:43 JosMHinkle
2002-08-15 14:47 ` Stuart MacDonald
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=257D72E0.2F5D0681.0BD32098@netscape.net \
    --to=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

all inboxes | Powered by JetHome®