From: David Hinds <dhinds@sonic.net>
To: "Bhavesh P. Davda" <bhavesh@avaya.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
fischer@norbit.de, dahinds@users.sourceforge.net,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] AHA152x driver hangs on PCMCIA card eject, kernel2.4.22-pre6
Date: Thu, 17 Jul 2003 10:55:40 -0700 [thread overview]
Message-ID: <20030717105540.D6720@sonic.net> (raw)
In-Reply-To: <003201c34c6d$e62386a0$6e260987@rnd.avaya.com>
On Thu, Jul 17, 2003 at 08:15:39AM -0600, Bhavesh P. Davda wrote:
> > Right - scsi_unregister should not be called on a timer event, instead
> > it needs to kick off a task queue
The removal timers need to be taken out from most *_cs drivers; they
are a holdover from when card removal events were delivered in
interrupt context, and when that was changed to an event handler
thread, drivers were not changed accordingly. The removal routine
should now just be called in-line instead of firing up a timer.
> 2. What happens if there is no physical device hanging off an I/O port
> address? I am guessing, that on an i386 host, the inb returns 0xFF, but am
> not sure what happens on other architectures. I have a question outstanding
> to Intel for this.
On most but not all x86 systems floating ports return 0xff. Checking
for that or other "impossible" register values should be at least
harmless on other architectures.
-- Dave
next prev parent reply other threads:[~2003-07-17 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 21:56 [PATCH] AHA152x driver hangs on PCMCIA card eject, kernel 2.4.22-pre6 Bhavesh P. Davda
2003-07-16 13:16 ` Alan Cox
2003-07-17 14:15 ` [PATCH] AHA152x driver hangs on PCMCIA card eject, kernel2.4.22-pre6 Bhavesh P. Davda
2003-07-17 17:55 ` David Hinds [this message]
2003-07-17 20:29 ` Bhavesh P. Davda
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=20030717105540.D6720@sonic.net \
--to=dhinds@sonic.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bhavesh@avaya.com \
--cc=dahinds@users.sourceforge.net \
--cc=fischer@norbit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).