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? Thanks again for your help so far Bob -----Original Message----- >From: Tejun Heo <tj@xxxxxxxxxx> >Sent: Aug 4, 2008 10:44 AM >To: the4hoffmans@xxxxxxxxxxxxx >Cc: jgarzik@xxxxxxxxx, linux-ide@xxxxxxxxxxxxxxx, blward@xxxxxxxxxx >Subject: Re: Issue with AHCI driver > >the4hoffmans@xxxxxxxxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
