From: Tejun Heo <tj@kernel.org>
To: the4hoffmans@earthlink.net
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, blward@micron.com
Subject: Re: Issue with AHCI driver
Date: Mon, 04 Aug 2008 23:44:32 +0900 [thread overview]
Message-ID: <489715D0.4000500@kernel.org> (raw)
In-Reply-To: <6738527.1217860606852.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
the4hoffmans@earthlink.net wrote:
> Thank you for your response, Tejun. We have figured some things out
> since I first e-mailed. We have been using IOMeter running on a
> remote Windows system which connects to a Dynamo module running on
> the Linux target. The Dynamo module uses a file open command with an
> O_DIRECT flag to minimize the effects of caching. Unfortunately,
> this causes the IO to be totally synchronous which is kinda bad for
> this type of benchmarking.
Ah.. Okay.
> I have another question for you. Where can I find information on how
> to get the AHCI driver to recognize our new AHCI controller?
If your controller has ahci class code, you don't need to do anything.
If not, you'll need to add the PCI ID to the device id table in ahci.c.
If the controller needs some quirks, you'll also need to add device id
entry and set its driver data to the appropriate board id (board_ahci_*).
--
tejun
next prev parent reply other threads:[~2008-08-04 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 14:36 Issue with AHCI driver the4hoffmans
2008-08-04 14:44 ` Tejun Heo [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 19:18 the4hoffmans
2008-08-04 19:33 ` Jeff Garzik
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=489715D0.4000500@kernel.org \
--to=tj@kernel.org \
--cc=blward@micron.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=the4hoffmans@earthlink.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).