From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Dave Lawrence <dgl@integrinautics.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: compact flash IDE hot-swap summary please
Date: 23 Jul 2003 23:15:11 +0100 [thread overview]
Message-ID: <1058998510.6890.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030723221525.A3397@flint.arm.linux.org.uk>
On Mer, 2003-07-23 at 22:15, Russell King wrote:
> Ok, I see a couple of problems here.
>
> Firstly, how does ide_cs in 2.6.0-test1 know that ide_unregister has
> failed? In my copy of 2.6.0-test1, it doesn't return any values.
It does in 2.4. For 2.6 check with Bart - it may be the need has gone
away or that stuff got "cleaned up" that was needed
> Secondly, 2.4.21 seems to fail with value '1' for two cases:
> - the ide interface wasn't found to be present
> - the drive is in use
> - the shutdown fails
Right. We want multiple fail cases. I know this - ditto it needs to
zap the iops
> not going to complete. Hopefully an in-progress request should time
> out, but we shouldn't try to start a new request.
Once we've flipped the iops it wont matter if we accidentally queue
new requests.
> So, in short, I think that IDE unplug is broken in the core IDE driver
> and needs significant work in _both_ 2.4 and 2.6 before we can think
> about getting PCMCIA-based IDE cards to work sufficiently well. Yes,
> ide-cs.c may need some work, but ide.c also requires work.
You need a call in it to zap the iops, 3 return codes so you can tell
the difference - anything else ? If not I'll fix those.
next prev parent reply other threads:[~2003-07-23 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 18:11 compact flash IDE hot-swap summary please Dave Lawrence
2003-07-23 18:18 ` Alan Cox
2003-07-23 19:49 ` Russell King
2003-07-23 20:13 ` Alan Cox
2003-07-23 21:15 ` Russell King
2003-07-23 22:15 ` Alan Cox [this message]
2003-08-14 0:21 ` Vojtech Pavlik
2003-07-23 19:12 ` Andre Hedrick
2003-07-23 19:51 ` Russell King
2003-07-23 19:48 ` Andre Hedrick
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=1058998510.6890.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dgl@integrinautics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.