From: Jeff Garzik <jgarzik@pobox.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA ATAPI UDMA - first in Linux
Date: Fri, 14 May 2004 16:35:53 -0400 [thread overview]
Message-ID: <40A52DA9.6040200@pobox.com> (raw)
In-Reply-To: <1084565990.3084.36.camel@patibmrh9>
Pat LaVarre wrote:
> Perhaps I should blame my Silicon Image 3611CT80 1.4 bridge, and buy
> another?
This is very possible.
Silicon Image has introduced an addition to ATA called the "DMADIR" bit.
Their bridges require this bit in order to use DMA.
If your OS driver does not know about DMADIR (read: most OS drivers),
then it will fall back _unconditionally_ to PIO.
Try a Marvell bridge, maybe.
> Do we all agree SATA ATAPI UDMA is missing from Linux-2.6.6 `make
> defconfig`?
No. No need for new options, if you are using the IDE driver.
Once libata ATAPI support is working, it can simply be turned on. No
need for a config option there, either.
> Can any of us suggest other .config options to try?
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_IDE_TASK_IOCTL=y
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_SCSI_SATA is not set
next prev parent reply other threads:[~2004-05-14 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 19:43 SATA ATAPI UDMA - first in Linux Pat LaVarre
2004-05-14 20:05 ` Jeff Garzik
2004-05-14 20:19 ` Pat LaVarre
2004-05-14 20:35 ` Jeff Garzik [this message]
2004-05-15 13:27 ` Pat LaVarre
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=40A52DA9.6040200@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=p.lavarre@ieee.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).