From: Jeff Garzik <jeff@garzik.org>
To: jameshsu <jameshsu@acard.com>
Cc: linux-scsi@vger.kernel.org, 'David Miller' <davem@davemloft.net>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Matti Aarnio <postmaster@vger.kernel.org>,
tytso@us.ibm.com,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Should be Acard ATP8620 2SATA / 1 IDE driver
Date: Tue, 30 Oct 2007 06:24:22 -0400 [thread overview]
Message-ID: <47270656.7080205@garzik.org> (raw)
In-Reply-To: <00b501c81ace$ece895f0$6200a8c0@jameshsu>
jameshsu wrote:
> Should be in TEXT/PLAIN mode. --- resend
>
> ************************
> Hello,
>
> This driver has nothing changed since last time submit.
> However recently we download 2.6.23.1 kernel and found Acard ATP8620 SATA
> driver is still not there.
> Resend this message to submit the same driver again.
> Please help Acard to build in this SATA driver with latest Linux kernel.
> If any reason not able to add in, please let us know.
We would be glad to help!
This driver is an ATA driver, which duplicates the existing SCSI<->ATA
translation code we already have. It also fails to work around the
problems ("quirks") found in a large number of ATA devices.
As such, it would be preferred that this ATA hardware use the existing
ATA driver API.
You can see example drivers for advanced controllers such a
drivers/ata/ahci.c and drivers/ata/sata_sil24.c, which are both
FIS-based controllers with full NCQ support, hotplug support, port
multiplier support, and many others.
It is important in Linux that we do not duplicate effort by merging
drivers that duplicate the existing SCSI<->ATA translation layer, or
fail to use our existing ATA API.
Overall, we wish to avoid adding another ATA driver inside the SCSI
layer, without using the existing ATA<->SCSI code.
Is your hardware documentation public? I can help provide a sample
driver for your hardware, or help guide your engineers in this effort.
Regards,
Jeff, the Linux ATA maintainer
next parent reply other threads:[~2007-10-30 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00b501c81ace$ece895f0$6200a8c0@jameshsu>
2007-10-30 10:24 ` Jeff Garzik [this message]
2007-11-01 8:47 ` Should be Acard ATP8620 2SATA / 1 IDE driver jameshsu
[not found] ` <025c01c82016$fbcf3810$d400a8c0@laurence>
[not found] ` <025001c82067$d76c04c0$6200a8c0@jameshsu>
2007-11-07 22:13 ` Jeff Garzik
2007-11-07 22:16 ` Jeff Garzik
[not found] ` <001f01c821b0$20b6c9f0$6200a8c0@jameshsu>
[not found] ` <02d301c821e2$25dc01c0$d400a8c0@laurence>
2007-11-08 11:34 ` Re:Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 jameshsu
2007-11-08 16:22 ` Acard " Jeff Garzik
2007-11-08 19:52 ` Mark Lord
2007-11-08 20:09 ` Jeff Garzik
2007-11-08 20:19 ` Mark Lord
2007-11-08 20:31 ` Jeff Garzik
2007-11-08 20:49 ` SATA Target mode & libata Mark Lord
2007-11-08 21:05 ` Jeff Garzik
2007-11-27 10:18 ` Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 jameshsu
2007-11-07 22:30 ` [PATCH] Re: Should be Acard ATP8620 2SATA / 1 IDE driver Jeff Garzik
[not found] ` <005801c821fa$892827f0$6200a8c0@jameshsu>
2007-11-08 16:18 ` 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=47270656.7080205@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jameshsu@acard.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=postmaster@vger.kernel.org \
--cc=tytso@us.ibm.com \
/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).