From: Alexander Beregalov <a.beregalov@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sata_sx4: refresh and convert to new EH
Date: Mon, 13 Apr 2009 06:23:50 +0400 [thread overview]
Message-ID: <a4423d670904121923l391d67cake297c5a71ca49ace@mail.gmail.com> (raw)
In-Reply-To: <49E1CE26.9050401@garzik.org>
2009/4/12 Jeff Garzik <jeff@garzik.org>:
> Alexander Beregalov wrote:
>>
>> 2009/4/9 Jeff Garzik <jeff@garzik.org>:
>>>
>>> I reviewed and refreshed libata-dev.git#new-eh, now renamed to #sx4.
>>>
>>> Several bugs and missing pieces in the new-EH conversion were addressed
>>> (often by copying highly similar code from sata_promise, a highly
>>> similar chip)
>>>
>>> The only thing left is some "it still works" testing... any takers?
>>>
>>
>> Hi Jeff
>>
>> I have SX4000 card, it is based on the same PDC20621 chip, but has PATA
>> ports
>> (without PATA-SATA bridges).
>> Can I help?
>>
>> I am newbie here, but I will try to modify the driver to support PATA
>> card as well
>> and test your patch.
>
> It's unknown how well, or what is needed, to support the SX4000. You are
> welcome to dive in and figure out what is needed, but you'd be asking
> questions to which we wouldn't have answers.
I found Promise provided docs for FreeBSD team.
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/performance/2003-07/0043.html
>I do have the sx4000 in the works (thanks to Promise who has provided docs
>and HW to make this happen)..
Can we ask them too? :)
Interesting, I cut off all unrelated lines from freebsd/ata/ata-chipset.c
and it seems SX4/SX4000 driver is only about 700 lines long.
next prev parent reply other threads:[~2009-04-13 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 20:05 Jeff Garzik
2009-04-12 2:46 ` Alexander Beregalov
2009-04-12 11:19 ` Jeff Garzik
2009-04-13 2:23 ` Alexander Beregalov [this message]
2009-04-13 9:09 ` 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=a4423d670904121923l391d67cake297c5a71ca49ace@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=jeff@garzik.org \
--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®