From: Tejun Heo <htejun@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Leigh <nabble@theanthonys.net>, linux-ide@vger.kernel.org
Subject: Re: [COORDINATE] INIC-1620TA/1622TA2/1623TA2 SATA controllers from initio
Date: Wed, 13 Dec 2006 10:44:47 +0900 [thread overview]
Message-ID: <457F5B0F.9040201@gmail.com> (raw)
In-Reply-To: <20061212120332.4457768d@localhost.localdomain>
Hi,
Alan wrote:
>>
>> How did this go? I doubt I'm the only one who fell afoul of the "has linux
>> drivers" implication on initio's website...
>>
>> I know its early days, but any idea when this might be ready for production?
>
> I sent Tejun the data book but we've yet to succeed in cloning him or
> getting him a time machine.
>
> I had a look at it. The chip is a little weird so it'll take someone a
> while to write a driver for it and they'll need the hardware handy.
The chip really is weird. For some reason, I can't do ATA PIO from mmio
TF but can do so using BAR{0,2}. It does have sff-compliant BAR0-3 but
no BMDMA at BAR4. And it can't do more than 256 sects at a time. Ah...
also, SRST nor phy reset via SControl doesn't give valid device
signature. Only hardreset via IDMA_CTRL works. Bah...
Anyways, I'm getting there. My 1622 is happily transferring 76M file
without problem in and out of a seagate harddrive using pio mode. So,
please standby.
--
tejun
prev parent reply other threads:[~2006-12-13 1:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 15:24 [COORDINATE] INIC-1620TA/1622TA2/1623TA2 SATA controllers from initio Tejun Heo
2006-01-24 16:27 ` Bartlomiej Zolnierkiewicz
2006-01-24 16:33 ` Jeff Garzik
2006-02-01 22:29 ` Francois Romieu
2006-11-30 18:09 ` Matthias Urlichs
2006-12-01 0:57 ` Tejun Heo
2006-12-01 12:13 ` Alan
2006-12-01 13:48 ` Alan
2006-12-01 14:01 ` Tejun Heo
2006-12-01 17:20 ` Matthias Urlichs
2006-12-12 4:33 ` Leigh
2006-12-12 12:03 ` Alan
2006-12-13 1:44 ` Tejun Heo [this message]
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=457F5B0F.9040201@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=nabble@theanthonys.net \
/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).