On Wed, Oct 26, 2005 at 05:22:47PM +0100, Phil Quinton wrote:
> OK, some more info....
> 
> 
> I've stuck some more debugging in and I've spotted something a little 
> weird.
> 
> The piece of code below chucks out the following:
> 
> sii3112_drv_probe: sstatus = SStatus_DET_DEV.
> satalinkcb0: port 1: scnt=0xff sn=0xff cl=0xff ch=0xff
> 
> NOTICE the values are all 0xff... somehow I don't think this is correct.
> 
> Could it be possible that the chp->cmd_iot, chp->cmd_iohs[wd_sdh] are 
> mapped to the wrong place?

Yes, this can be the cause of the problem. When a drive probed as ST506 is
because the driver knows there is a drive here, but can't issue a
IDENTIFY command to it (that is, communications between the kernel and
device don't work).

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--