linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	Daniel Ritz <daniel.ritz@gmx.ch>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@diego.com>
Subject: Re: [bug 2.5.69] xirc2ps_cs, irq 3: nobody cared, shutdown hangs
Date: 11 May 2003 18:20:50 +0100	[thread overview]
Message-ID: <1052673649.29921.15.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3EBE8768.4000007@pobox.com>

On Sul, 2003-05-11 at 18:24, Jeff Garzik wrote:
> If netif_device_present() returns false, we think the hardware has 
> disappeared.  So that implies a bug in calling netif_device_detach() no 
> a bug in the irq handler return value.

Not really. The IRQ can be outstanding from the hardware unplug,
especially on PCMCIA. Its an edge triggered IRQ so the unplug is very
likely to latch an IRQ for delivery as the connector unplugs.

>   If pcmcia hardware disappears on you, you _really_ don't want to be 
> bitbanging its ports.

Its quite safe to do so. What we must do is ensure we don't reallocate
the ports until they are truely freed. The current PCMCIA seems to get
that right, (the current PCI locking for cardbus and hotplug is still
terminally broken of course)

Alan


  reply	other threads:[~2003-05-11 18:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 14:47 [bug 2.5.69] xirc2ps_cs, irq 3: nobody cared, shutdown hangs Daniel Ritz
2003-05-11 16:13 ` Zwane Mwaikambo
2003-05-11 17:24   ` Jeff Garzik
2003-05-11 17:20     ` Alan Cox [this message]
2003-05-11 22:08       ` David Woodhouse
2003-05-11 21:40         ` Alan Cox
2003-05-11 22:55           ` David Woodhouse
2003-05-11 17:31     ` Zwane Mwaikambo
2003-05-12 19:59   ` Daniel Ritz
2003-05-13  7:43     ` Zwane Mwaikambo

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=1052673649.29921.15.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@diego.com \
    --cc=daniel.ritz@gmx.ch \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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;
as well as URLs for NNTP newsgroup(s).