From: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "James Bottomley" <James.Bottomley@hansenpartnership.com>,
ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>
Subject: Re: Kernel Summit request for Discussion of future of ATA (libata) and IDE
Date: Sun, 3 Aug 2008 22:19:40 +0200 [thread overview]
Message-ID: <58cb370e0808031319o748e570bo700873365ba22aa1@mail.gmail.com> (raw)
In-Reply-To: <20080803201719.576f85f6@lxorguk.ukuu.org.uk>
On Sun, Aug 3, 2008 at 9:17 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> I don't envisage anything in terms of code changes (or removal) coming
>> out of this. What I would like is a nice roadmap of where to start for
>> people contemplating writing IDE drivers.
>
> For the vendors I've talked with the answer is usually "both". A libata
> driver for the future and current distributions, and an old IDE driver
> for older RHEL and SLES releases. Fortunately the driver specific parts
> for those that are capable of running under old IDE are not too hard to
> plug into libata.
The contrary is also true, for modern drivers/ide conversion of libata PATA
driver to use drivers/ide should usually be a matter of an hour or two.
I think that the conversion of libata drivers for PATA hardware that is not
supported by drivers/ide currently should be doable by somebody knowing
both subsystems in less than 24h. I'm not doing it only because it will make
me a maintainer of even more host drivers than currently and I don't have a
time for it. I'll happily accept patches though.
Thanks,
Bart
next prev parent reply other threads:[~2008-08-03 20:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 15:57 James Bottomley
2008-08-03 16:39 ` Alan Cox
2008-08-03 17:10 ` James Bottomley
2008-08-03 18:45 ` Alan Cox
2008-08-03 19:21 ` James Bottomley
2008-08-03 19:17 ` Alan Cox
2008-08-03 20:19 ` Bartlomiej Zolnierkiewicz [this message]
2008-08-03 22:07 ` Alan Cox
2008-08-03 17:32 ` Willy Tarreau
2008-08-03 17:45 ` Rafael J. Wysocki
2008-08-03 17:57 ` Willy Tarreau
2008-08-03 20:22 ` [Ksummit-2008-discuss] " David Woodhouse
2008-08-04 5:35 ` Benjamin Herrenschmidt
2008-08-04 13:16 ` Kumar Gala
2008-08-04 13:07 ` Alan Cox
2008-08-03 20:09 ` Bartlomiej Zolnierkiewicz
2008-08-03 22:01 ` Alan Cox
2008-08-03 23:10 ` Jeff Garzik
[not found] <fa.OGeO7gZvBG4obEzRbVltjSebgTQ@ifi.uio.no>
[not found] ` <fa.KtvYE2B2yrJqUleolhtMPN9ljAQ@ifi.uio.no>
[not found] ` <fa.AqEKTvguYFAzDFHy/We/8MpOqmo@ifi.uio.no>
2008-08-04 20:07 ` Robert Hancock
2008-08-04 19:55 ` Alan Cox
2008-08-04 21:17 ` Robert Hancock
2008-08-04 21:06 ` Alan Cox
2008-08-04 21:48 ` Robert Hancock
2008-08-06 0:21 ` Robert Hancock
2008-08-06 0:44 ` Tejun Heo
2008-08-06 2:30 ` Robert Hancock
2008-08-06 11:27 ` Sergei Shtylyov
2008-08-06 8:51 ` Alan Cox
2008-08-04 21:55 ` Sergei Shtylyov
2008-08-04 21:43 ` Alan Cox
2008-08-04 22:45 ` Sergei Shtylyov
2008-08-04 22:52 ` Sergei Shtylyov
2008-08-06 11:17 ` Sergei Shtylyov
2008-08-04 22:12 ` Mark Lord
2008-08-04 22:00 ` Alan Cox
2008-08-04 20:37 ` Jeff Garzik
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=58cb370e0808031319o748e570bo700873365ba22aa1@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--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
Powered by JetHome