public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Chris Rankin <rankincj@yahoo.com>, Adam Belay <ambx1@neo.rr.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: Linux 2.6.17: IRQ handler mismatch in serial code?
Date: Mon, 19 Jun 2006 20:44:07 +0100	[thread overview]
Message-ID: <20060619194407.GJ3479@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060619194024.99464.qmail@web52903.mail.yahoo.com>

On Mon, Jun 19, 2006 at 08:40:24PM +0100, Chris Rankin wrote:
> --- Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> > This seems to be an invalid situation - you appear to have an _ISA_
> > NE2000 card using IRQ3, trying to share the same interrupt as a
> > serial port.
> > 
> > ISA interrupts aren't sharable without additional hardware support
> > or specific software support in the Linux kernel interrupt
> > architecture.
> 
> Hmm, I see what you mean. Except that I thought that I'd manually disabled the motherboard's
> serial device on IRQ 3, via the BIOS:
> 
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> pnp: Device 00:07 activated.
> 00:07: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
> pnp: Device 00:08 activated.
> 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> 
> Does Linux reenable all motherboard devices, regardless?

Question for Adam Belay.

>From the messages above, ttyS1 was not accessible when we probed it
via the legacy ISA table, but was in the PnP table and became
accessible when it was activated via PnP.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-06-19 19:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 18:06 Linux 2.6.17: IRQ handler mismatch in serial code? Chris Rankin
2006-06-19 18:47 ` Russell King
2006-06-19 19:40   ` Chris Rankin
2006-06-19 19:44     ` Russell King [this message]
2006-06-20  1:00       ` Adam Belay
2006-06-20  7:50         ` Chris Rankin
2006-06-19 19:45   ` Mark Lord
2006-06-19 21:06     ` Alan Cox
2006-06-19 21:52       ` Mark Lord
2006-06-19 22:21         ` Alan Cox
     [not found] <6pwmi-8mW-1@gated-at.bofh.it>
     [not found] ` <6px8R-Y7-43@gated-at.bofh.it>
     [not found]   ` <6pxV5-2ci-13@gated-at.bofh.it>
     [not found]     ` <6pz12-3Rg-67@gated-at.bofh.it>
     [not found]       ` <6pzX4-5jE-19@gated-at.bofh.it>
     [not found]         ` <6pA6B-5K8-33@gated-at.bofh.it>
2006-06-20 14:39           ` Bodo Eggert
2006-06-20 18:03             ` Russell King
2006-06-20 23:20               ` Bodo Eggert

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=20060619194407.GJ3479@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rankincj@yahoo.com \
    /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