From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [sata] new libata-dev-2.6 queue created (AHCI, SATA bridges)
Date: Wed, 15 Sep 2004 12:10:26 -0400 [thread overview]
Message-ID: <20040915161026.GA31360@havoc.gtf.org> (raw)
"libata-dev-2.6" is a new patch queue for SATA features which are under
development, or need additional testing before being deployed into the
upstream-bound libata-2.[46] queues.
It currently contains:
1) A workaround for problems on multiple SATA controllers when using
PATA disks attached via SATA bridges.
2) New driver AHCI. This should currently be considered a technology
preview or early beta test. Simply because it is a young driver on
complicated hardware, using a new "FIS-based" delivery method (read:
brand new hotpath), caution is advised. Do not use in production yet.
I have updated my SATA status page to reflect these updates:
http://linux.yyz.us/sata/sata-status.html
BK users:
bk pull bk://gkernel.bkbits.net/libata-dev-2.6
Patch (NOTE: relative to 2.6.9-rc2-bk1-libata1.patch):
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.9-rc2-bk1-libata1-dev1.patch.bz2
This will update the following files:
drivers/scsi/Kconfig | 8
drivers/scsi/Makefile | 1
drivers/scsi/ahci.c | 973 +++++++++++++++++++++++++++++++++++++++++++++
drivers/scsi/libata-core.c | 37 +
include/linux/ata.h | 1
include/linux/libata.h | 1
6 files changed, 1018 insertions(+), 3 deletions(-)
through these ChangeSets:
<jgarzik@pobox.com> (04/09/15 1.1905)
[libata] add AHCI driver
<brad@wasp.net.au> (04/09/15 1.1902.1.1)
[PATCH] libata basic detection and errata for PATA->SATA bridges
This patch works around an issue with WD drives (and possibly others) over SiL PATA->SATA Bridges on SATA controllers locking up with transfers > 200 sectors.
Signed-off-by: Brad Campbell <brad@wasp.net.au>
next reply other threads:[~2004-09-15 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 16:10 Jeff Garzik [this message]
2004-09-15 22:47 ` Andre Tomt
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=20040915161026.GA31360@havoc.gtf.org \
--to=jgarzik@pobox.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
all inboxes | Powered by JetHome®