From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Parallel ATA with libata status with the patches I'm working on
Date: Thu, 03 Nov 2005 15:56:38 +0000 [thread overview]
Message-ID: <1131033398.18848.68.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0511030702hb06a5f3qc2dfe465ee1d784c@mail.gmail.com>
On Iau, 2005-11-03 at 16:02 +0100, Bartlomiej Zolnierkiewicz wrote:
> IMO porting/rewriting host-drivers to libata now is just
> counter-productive waste of time...
Face it, drivers/ide/ is beyong saving, it has entered the software
engineering twilight zone that follows 'maintainable'.
Shifting a non-complex driver to libata with a few libata improvements
is not a difficult process. Figuring out the extra hooks and bits to
make it clean is the difficult bit. Each time another PATA horror is
supported by libata it becomes easy for other cards with that horror to
be moved over.
Also drivers/ide contains detailed support for things that just aren't
worth moving over - like SWDMA.
Once the core support is done then quite frankly I'll be able to port a
PATA driver to libata faster than sherlock holmes could deduce the
drivers/ide locking "rules" let alone fix them.
Alan
next prev parent reply other threads:[~2005-11-03 15:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 14:54 Parallel ATA with libata status with the patches I'm working on Alan Cox
2005-11-03 14:48 ` Russell King
2005-11-03 15:02 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:28 ` David S. Miller
2005-11-03 15:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 16:27 ` Alan Cox
2005-11-03 15:56 ` Alan Cox [this message]
2005-11-03 20:55 ` Krzysztof Halasa
2005-11-03 21:29 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:29 ` Krzysztof Halasa
2005-11-03 22:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:54 ` Alan Cox
2005-11-04 1:30 ` Rogério Brito
2005-11-04 13:38 ` Alan Cox
2005-11-04 13:41 ` Alan Cox
2005-11-04 23:10 ` Russell King
2005-11-04 23:19 ` Benjamin Herrenschmidt
2005-11-03 15:58 ` Alan Cox
2005-11-03 15:30 ` Russell King
2005-11-03 16:23 ` Alan Cox
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 8:43 ` Xavier Bestel
2005-11-03 14:58 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:49 ` Alan Cox
2005-11-03 15:34 ` Bartlomiej Zolnierkiewicz
2005-11-04 0:14 ` Mark Lord
2005-11-04 0:17 ` Mark Lord
2005-11-04 1:18 ` Alan Cox
2005-11-04 3:49 ` Jeff Garzik
2005-11-05 22:31 ` Mark Lord
2005-11-04 6:43 ` Benjamin Herrenschmidt
2005-11-04 7:00 ` Jeff Garzik
2005-11-04 13:34 ` Alan Cox
2005-11-04 21:50 ` Benjamin Herrenschmidt
2005-11-06 20:41 ` 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=1131033398.18848.68.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--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