From: Jeff Garzik <jgarzik@pobox.com>
To: the4hoffmans@earthlink.net
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org, blward@micron.com
Subject: Re: Issue with AHCI driver
Date: Mon, 04 Aug 2008 15:33:38 -0400 [thread overview]
Message-ID: <48975992.4030003@pobox.com> (raw)
In-Reply-To: <30565143.1217877521998.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
the4hoffmans@earthlink.net wrote:
> We do have the AHCI class code - PCI offset 09h = 010601h. We are detected as an AHCI controller under Vista. I even tried adding our vendor/device id to ahci.c but that didn't make any difference. Is there something else I'm missing?
>
> A little background...
>
> We have a PCIe plug-in card that identifies itself as an AHCI controller as mentioned above. We used a PCIe analyzer card to look at traffic as we booted Linux (build 2.6.19). We saw various PCI reads & writes as the system initialized PCI resources but we never saw what would amount to an 'Identify Device' command which I'm assuming the libata driver should do. Any ideas?
Turn on debugging (top of include/linux/libata.h), and show us that output.
As Tejun noted, every vendor that claims full AHCI compatibility works
with the Linux AHCI driver just fine. A couple vendors that are not
fully compatible (Marvell, ACard) need some tweaks due to non-standard
register and operational differences.
Jeff
next prev parent reply other threads:[~2008-08-04 19:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 19:18 Issue with AHCI driver the4hoffmans
2008-08-04 19:33 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-08 20:41 the4hoffmans
2008-08-08 21:43 ` Jeff Garzik
2008-08-07 20:51 the4hoffmans
2008-08-06 16:59 the4hoffmans
2008-08-06 23:15 ` Tejun Heo
2008-08-06 13:17 the4hoffmans
2008-08-05 21:28 the4hoffmans
2008-08-05 23:10 ` Tejun Heo
2008-08-05 20:14 the4hoffmans
2008-08-04 20:56 the4hoffmans
2008-08-04 23:10 ` Tejun Heo
2008-08-04 14:36 the4hoffmans
2008-08-04 14:44 ` Tejun Heo
2008-07-10 15:17 the4hoffmans
2008-08-01 4:06 ` Tejun Heo
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=48975992.4030003@pobox.com \
--to=jgarzik@pobox.com \
--cc=blward@micron.com \
--cc=linux-ide@vger.kernel.org \
--cc=the4hoffmans@earthlink.net \
--cc=tj@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).