From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Date: Thu, 20 Dec 2007 16:42:57 +0000
From: Bob <rpangrazio@gmail.com>
Message-ID: <192fd422-5e8a-456c-8861-2141054b7a82@p1g2000hsb.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <978dfe78-6b93-44d0-9f3c-faa0a8f69240@x69g2000hsx.googlegroups.com>
Subject: [9fans] Re: Intel Sata
Topicbox-Message-UUID: 1e937714-ead3-11e9-9d60-3106f5b1d025

On Dec 20, 8:12 am, quans...@quanstro.net (erik quanstrom) wrote:
> On Thu Dec 20 04:47:55 EST 2007, rpangra...@gmail.com wrote:
>
> > So now the update. The dev id 27c0 corresponds to my sata in ata mode.
> > 27c1 is the sata in ahci mode. If I add 27c1 to sdiahci.c and 27c0 to
> > sdata.c I get nothing from the kernel at boot up saying it found
> > anything. If I add 27c1 to both I get the response from the kernel. I
> > wonder if the driver can't handle the drive. Maybe the sata controller
> > I have is different enough from the controller used to write the
> > driver that it won't work. I find that hard to believe, but stranger
> > things are true.
>
> either you can recognize the drive as ahci, or as a normal ata drive,
> but not both at the same time.  that's prohibited.
>
> - erik

So adding the same dev id to both drivers is wrong. But then why does
it not work when I add the corresponding dev id's to the appropiate
driver. It should then be able to recognize it in both instances.

Bob