From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Albert Lee <albertcc@tw.ibm.com>
Subject: PATA drivers in libata?
Date: Sun, 13 Feb 2005 13:51:37 -0500 [thread overview]
Message-ID: <420FA1B9.6030100@pobox.com> (raw)
I wanted to open a discussion on libata and PATA.
libata-dev now has two drivers that support PATA, pata_pdc2027x and
ata_piix, and the core is getting close (DMA blacklist in, C/H/S support
close).
What are the opinions on issues relating to making PATA libata support
available in the upstream kernel? Here's my random list.
* I think CONFIG_IDE should continue to be the default answer for "what
driver do I use for PATA?"
* Should there be a config option similar to CONFIG_BLK_DEV_IDE_SATA,
called CONFIG_SCSI_ATA_PATA? A runtime 'pata' module option? Should we
include 'DANGER DANGER conflicts with CONFIG_IDE' in the Kconfig
description?
* With ATA passthru (in libata-dev currently), libata supports SMART and
the HDIO_CMD/HDIO_TASK generalized ioctls. Should I care about
supporting other ioctls?
* pci_enable_device() issues?
* power management differences?
next reply other threads:[~2005-02-13 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 18:51 Jeff Garzik [this message]
2005-02-13 21:12 ` PATA drivers in libata? Mark Hahn
2005-02-13 22:01 ` Jeff Garzik
2005-02-14 0:19 ` Doug Maxey
2005-02-14 0:25 ` Jeff Garzik
2005-02-13 22:38 ` Alan Cox
2005-02-14 0:16 ` Jeff Garzik
2005-02-14 20:42 ` Alan Cox
2005-02-17 1:13 ` Benjamin Herrenschmidt
2005-02-17 1:11 ` Benjamin Herrenschmidt
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=420FA1B9.6030100@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.