From: Martin Dalecki <dalecki@evision-ventures.com>
To: Paul Bristow <paul@paulbristow.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5.22] simple ide-tape.c and ide-floppy.c cleanup
Date: Tue, 09 Jul 2002 14:28:30 +0200 [thread overview]
Message-ID: <3D2AD6EE.6020303@evision-ventures.com> (raw)
In-Reply-To: 3D29F70D.6020001@paulbristow.net
Użytkownik Paul Bristow napisał:
> OK. I kept quiet while the IDE re-write went on so that when it was
> over I could fix up ide-floppy and start adding some of the requested
> features that were only really possible with the taskfile capabilities.
> But I have to jump in with the latest statements from Martin...
> Martin Dalecki wrote:
>
>> Użytkownik Eduard Bloch napisał:
>>
>>
>>> Why not another way round? Just make the ide-scsi driver be prefered,
>>> and hack ide-scsi a bit to simulate the cdrom and adv.floppy devices
>>> that are expected as /dev/hd* by some user's configuration?
>>>
>>
>>
>> This is the intention.
>>
> Since when? I thought Jens was in the process of getting rid of the
> ide-scsi kludge with his moves to support cd/dvd writing directly in
> ide-cd?
Well code decides. And in reality I have tried the much simpler goal
to unify the ide-floppy ide-tape and ide-cd parts which
should be common. Like for example a simple SCSI multi media command set
preparation library. Admittedly I have failed. Therefore and in
fact of the 2.6 release schedule it's simple not practical to
persue this road further. It makes much more sense to just
1. Scrap the specific atapi drivers.
2. Try to make ide-scsi independant from SCSI subsystem from users view.
3. Replicate some of the workarounds in the previous ide-xxxx drivers.
>
> The current system may be ugly, but if we have to break it in the name
> of progress we have at least to make the new, improved version work as
> well (and hopefully better) than the old one.
>
>>> Other operating systems did switch to constitent (scsi-based) way of
>>> accessing all kinds of removable media drivers. Why does Linux have to
>>> keep a kludge, written years ago without having a good concept?
>>>
>>>
>>
> If we can address all these issues I will be extremely happy to helping
> create a sensible removeable media subsystem.
That's a deal.
next prev parent reply other threads:[~2002-07-09 12:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 15:51 [PATCH 2.5.22] simple ide-tape.c and ide-floppy.c cleanup Eduard Bloch
2002-07-03 18:03 ` Bartlomiej Zolnierkiewicz
2002-07-08 4:23 ` Martin Dalecki
2002-07-08 20:33 ` Paul Bristow
2002-07-08 21:41 ` Andre Hedrick
2002-07-08 21:56 ` Bartlomiej Zolnierkiewicz
2002-07-09 12:28 ` Martin Dalecki [this message]
2002-07-09 12:46 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2002-07-03 22:21 James Bottomley
[not found] <mailman.1025711581.26152.linux-kernel2news@redhat.com>
2002-07-03 20:18 ` Pete Zaitcev
2002-07-03 22:09 ` Andre Hedrick
2002-06-19 21:45 Bartlomiej Zolnierkiewicz
2002-06-20 5:42 ` Jens Axboe
2002-06-20 9:16 ` Martin Dalecki
2002-06-20 9:19 ` Jens Axboe
2002-06-20 9:22 ` Martin Dalecki
2002-06-20 16:37 ` Bartlomiej Zolnierkiewicz
2002-06-20 16:41 ` Martin Dalecki
2002-06-20 16:44 ` Jens Axboe
2002-06-20 16:50 ` Bartlomiej Zolnierkiewicz
2002-06-20 17:26 ` Jens Axboe
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=3D2AD6EE.6020303@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paulbristow.net \
/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