From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Hancock <hancockrwd@gmail.com>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: update Kconfig text to mark as deprecated
Date: Thu, 29 Oct 2009 21:47:58 -0400 [thread overview]
Message-ID: <4AEA45CE.2060708@garzik.org> (raw)
In-Reply-To: <20091030003232.6db3f8b8@lxorguk.ukuu.org.uk>
On 10/29/2009 08:32 PM, Alan Cox wrote:
> IDE will self correct in time anyway - new hardware doesn't work with it,
> newer embedded devices are also moving away from compact flash, so it'll
> die of its own accord.
>
> As such while things like pmac support in libata will be nice I don't
> think there is any need to go around obsoleting it or pressuring people
> to move stacks.
This has been my general policy... people will continue moving away
from IDE over time. Not much need to do anything but let sleeping dogs lie.
libata definitely needs pmac support, that is the really only big
missing driver piece, IMO.
On compatibility: while a compat ATA block device would be nice --
having a native Linux block driver for ATA disks has been a longstanding
"want" since Day One -- a compat block device purely for these
situations would be quite a bit of work for a tiny-and-shrinking
userbase. And that totally ignores an idea of attempting compatibility
with IDE's ATAPI setup, another huge can-o-worms.
Jeff
prev parent reply other threads:[~2009-10-30 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 1:41 [PATCH] ide: update Kconfig text to mark as deprecated Robert Hancock
2009-10-29 10:13 ` David Miller
2009-10-30 0:19 ` Robert Hancock
2009-10-30 0:30 ` David Miller
2009-10-30 0:33 ` Alan Cox
2009-10-30 0:39 ` David Miller
2009-10-30 8:15 ` Martin Steigerwald
2009-10-30 8:18 ` Martin Steigerwald
2009-10-30 8:39 ` David Miller
2009-10-30 8:38 ` David Miller
2009-10-30 0:32 ` Alan Cox
2009-10-30 1:47 ` Jeff Garzik [this message]
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=4AEA45CE.2060708@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=hancockrwd@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).