linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Yeh <jimyeh98@acard.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "jason wu" <jason_wu@acard.com>,
	"\"莊文舉(Jason Chuang)\"" <jason@acard.com>,
	"\"陳力誠(Richard Chen)\"" <rchern@acard.com>,
	"\"翁茂賀(Daniel Weng)\"" <dweng@acard.com>,
	"\"吳佳璋(Laurence Wu)\"" <laurence@acard.com>,
	"\"陳德威(Derwei Chen)\"" <derwei@acard.com>,
	"\"陳金清(GeingChing Chen)\"" <geingching@acard.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	akpm@linux-foundation.org, "Tejun Heo" <htejun@gmail.com>
Subject: Re: Fw: [PATCH] ahci: add ACard 8620 support (rough draft)
Date: Tue, 14 Apr 2009 10:28:00 +0800	[thread overview]
Message-ID: <49E3F4B0.1080909@acard.com> (raw)
In-Reply-To: <49E323E1.90907@garzik.org>

Dear Jeff,

Thanks for your explanation. We agree with you.

 I'll prepare the hardware for your testing. The form factor of PCB will 
be a 32bit PCI-base add-on card. Please advise the address for both of 
yours. It is expected to be sent by next week.

Regards,
 
Jim Yeh
Product Manager
Marketing Dept.
ACARD Technology Corp.
TEL:886-2-85122290#3244



Jeff Garzik 提到:
> Jim Yeh wrote:
>> Dear Jeff,
>>
>> This is Jim,an IC PM from ACARD Technology. Thanks for your effort on 
>> building Linux driver for ACARD ATP8620. Since ACARD already have a 
>> verified AHCI driver for ATP8620, we'd like to submit this one for 
>> the kernel built-in driver (please see attachment). This driver 
>> support Linux Kernel 2.6.29 AHCI mode for ATP8620 (2ch SATA IC) and 
>> ATP8624 (4ch SATA IC). It already passed our own stability and 
>> compatibility test with SATA devices like HDD, ODD, or 
>> PortMultiplier. If you have any question or need the hardware for 
>> testing, please don't hesitate to contact me. Thanks again for your 
>> help.
>
> Thank you for your email.
>
> We understand you have verified your driver, but it is standard Linux 
> driver policy to avoid code duplication.  Multiple implementations of 
> AHCI drivers implies several negative factors:
>
> * each bug fix must be reviewed across multiple AHCI drivers, to 
> determine if the bug fix must be copied
>
> * non-uniform user experience, depending on AHCI platform
>
> * Shared AHCI code gets much more testing and verification.
>
> * When a hardware vendor's AHCI chip reaches End Of Life, or the 
> company goes out of business, users are not abandoned.
>
> So, for the official Linux kernel drivers that are shipped by Red Hat, 
> Novell/SuSE, Canonical and other vendors, we will need to modify the 
> existing Linux AHCI driver to support ATP8620 and ATP8624.
>
>
> And yes -- test hardware would be greatly appreciated!  If you could 
> send these, that would be appreciated:
>
>     To Tejun Heo
>     ------------
>     1 x ATP8620
>     1 x ATP8624
>
>     To Jeff Garzik
>     --------------
>     1 x ATP8620
>     1 x ATP8624
>
> I assume this is PCI, PCI-X or PCI-Express form factor?
>
> Regards and thanks,
>
>     Jeff
>
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4005 (20090413) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>

  reply	other threads:[~2009-04-14  3:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000d01c9b815$73006700$b500a8c0@JasonWuNB>
     [not found] ` <49E31219.1000301@acard.com>
2009-04-13 11:37   ` Fw: [PATCH] ahci: add ACard 8620 support (rough draft) Jeff Garzik
2009-04-14  2:28     ` Jim Yeh [this message]
2009-04-14  3:40       ` Tejun Heo
     [not found]         ` <49EC56F6.5000602@acard.com>
2009-04-20 14:40           ` 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=49E3F4B0.1080909@acard.com \
    --to=jimyeh98@acard.com \
    --cc=akpm@linux-foundation.org \
    --cc=derwei@acard.com \
    --cc=dweng@acard.com \
    --cc=geingching@acard.com \
    --cc=htejun@gmail.com \
    --cc=jason@acard.com \
    --cc=jason_wu@acard.com \
    --cc=jeff@garzik.org \
    --cc=laurence@acard.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rchern@acard.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).