From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: Current sata_inic attempts (was pata_pcmcia: Minor cleanups and support for dual channel cards)
Date: Wed, 28 Nov 2007 20:31:45 +0900 [thread overview]
Message-ID: <474D51A1.1050107@gmail.com> (raw)
In-Reply-To: <20071128093952.77652450@the-village.bc.nu>
lAlan Cox wrote:
> On Wed, 28 Nov 2007 10:56:21 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> Alan Cox wrote:
>>> setup and it821x fixes can go to mainstream for 2.6.25 I think - no bad
>>> reports yet.
>>>
>>> BTW so we don't duplicate work right now I'm working on a full DMA engine
>>> based driver for the INIC162x. Dunno if I'll ever get it to work as the
>>> docs are a bit minimal but we shall see.
>> Great, are you gonna use the ADMA interface?
>
> This is the plan. I have the driver trying to do this but right now I get
> a single unsolicited CDB back when I reset the bus and my identify
> command times out.
That sounds consistent with my failed try. I thought the problem was
caused by the controller not willing to switch out of legacy mode.
aLGCY bit of IDMSTAT register indicates that the controller is in legacy
mode. No matter what I do to it, it just won't go off. Have you
managed to clear that bit?
Thanks.
--
tejun
next prev parent reply other threads:[~2007-11-28 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 14:43 [PATCH] pata_pcmcia: Minor cleanups and support for dual channel cards Alan Cox
2007-11-24 0:47 ` Jeff Garzik
2007-11-26 15:40 ` Alan Cox
2007-11-28 1:56 ` Tejun Heo
2007-11-28 9:39 ` Current sata_inic attempts (was pata_pcmcia: Minor cleanups and support for dual channel cards) Alan Cox
2007-11-28 11:31 ` Tejun Heo [this message]
2007-11-28 13:03 ` Alan Cox
2007-12-04 19:37 ` [PATCH] pata_pcmcia: Minor cleanups and support for dual channel cards Jeff Garzik
2007-12-04 20:22 ` Alan Cox
2007-12-18 22:07 ` 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=474D51A1.1050107@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).