From: Alan Cox <alan@redhat.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@redhat.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: IDE hackery: lock fixes and hotplug controller stuff
Date: Thu, 12 Aug 2004 14:56:14 -0400 [thread overview]
Message-ID: <20040812185614.GC866@devserv.devel.redhat.com> (raw)
In-Reply-To: <200408121912.35507.bzolnier@elka.pw.edu.pl>
On Thu, Aug 12, 2004 at 07:12:35PM +0200, Bartlomiej Zolnierkiewicz wrote:
> It is a correct analysis for /proc/ide/hdx/settings:ide-scsi but not
> for /proc/ide/hdx/driver which works just fine (modulo being racy)
> and your patch removes both interfaces...
I see no viable way to fix it, and I see nobody using it so it should
die. If someone does want to keep it then they can rewrite the ide layer
to make it work.
BTW I've been over the proc stuff and fixed that up including all the
locking. I can now happily insmod it8212, rmmod it8212, insmod it8212 etc
and the /proc files behave. I did have to make a couple of tweaks to cover
the locking cases not covered.
I also have the it8212 working in smart but non raid now. Seems issuing an
LBA 48 cache flush (0xEF) crashes the firmware which is why it died on load
for some users. To do that I've added hwif->raw_taskfile() so that an
interface can filter commands.
Next stop disk hot plugging.
Alan
next prev parent reply other threads:[~2004-08-12 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 16:19 IDE hackery: lock fixes and hotplug controller stuff Alan Cox
2004-08-10 17:16 ` Bartlomiej Zolnierkiewicz
2004-08-10 18:23 ` Alan Cox
2004-08-12 17:12 ` Bartlomiej Zolnierkiewicz
2004-08-12 18:56 ` Alan Cox [this message]
2004-08-12 19:46 ` Bartlomiej Zolnierkiewicz
2004-08-12 20:37 ` Alan Cox
2004-08-10 20:48 ` Ian Hastie
2004-08-10 21:06 ` Alan Cox
2004-08-11 0:36 ` Ian Hastie
2004-08-12 19:55 ` Alan Cox
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=20040812185614.GC866@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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