public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark Lord <lkml@rtr.ca>
Cc: Chris Rankin <rankincj@yahoo.com>,
	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 23:21:41 +0100	[thread overview]
Message-ID: <1150755701.2871.49.camel@localhost.localdomain> (raw)
In-Reply-To: <44971C95.7050700@rtr.ca>

Ar Llu, 2006-06-19 am 17:52 -0400, ysgrifennodd Mark Lord:
> > This is not the case for ISA bus. Most ISA hardware is physically unable
> > to share and the drivers for such hardware intentionally grab the IRQ at
> > load time to avoid it being mis-reused.
> 
> Eh?  The vast majority of ISA bus devices have open-collector IRQ lines,

Not in my experience. In the network work at least very few are, they
all drive the chip lines all the time. Thats why Don Becker made sure
such drivers grab the lines at startup. Those which can share IRQ or
move IRQ grab at open

Alan


  reply	other threads:[~2006-06-19 22:06 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
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 [this message]
     [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=1150755701.2871.49.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --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