With SATA, there are no masters or slaves, all disks are equal.Interrogative wrote:I am guessing that ports 0 and 1 are primary masters and ports 2 and 3 are slaves.
Best regards,
Niels
With SATA, there are no masters or slaves, all disks are equal.Interrogative wrote:I am guessing that ports 0 and 1 are primary masters and ports 2 and 3 are slaves.
Well, Niels, that is what I would have thought. Yet, having read the documentation (SYS:Documentation/IDE/sii3114ide_dev.doc)...nbache wrote:With SATA, there are no masters or slaves, all disks are equal.Interrogative wrote:I am guessing that ports 0 and 1 are primary masters and ports 2 and 3 are slaves.
Best regards,
Niels
The driver treats the SATA card like a regular IDE card with primary, secondary, master, and slave configurations. What I've been trying to figure out is what ports are considered primary, secondary, masters, and slaves by the driver. Once I have that figured out, I can correctly set up my drives on the card and the sii3114ide_conf. As said in the documentation...- sii3114ide_conf
Compose 4 chars (pri master, pri slave, sec master, sec slave) using :
0 : nothing
1 : harddisk
2 : dvd/cdrom reader or burner
Default : if you don't set this envvar, sii3114ide will scan the IDE buses and
try to determine the configuration by itself.
One more problem is that setting maxbus doesn't seem to do anything. UBoot still scans all four ports timing out on ports 1 and 3.- Using sii3114ide_conf (properly set !) saves need for timeouts for drive
detection at boot time.
I'm pretty sure that is just a copy/paste thing from the docs of the ide drivers it was built upon. But of course I am not a developer and don't have access to the source.Interrogative wrote:(SYS:Documentation/IDE/sii3114ide_dev.doc)...nbache wrote:With SATA, there are no masters or slaves, all disks are equal.- sii3114ide_conf
Compose 4 chars (pri master, pri slave, sec master, sec slave) using :
In other words, my newly bought 3512 is dying. If I was to get another one, it might just work. Time to send this one back.Yes, I've had one die on me only a few days ago. The boot process seemed to freeze, but left to itself, it would complete after half an hour or so. The card seemed to be continuously interrupting while ever a HD was connected to it.
Once the system was up, I could move the mouse, but nothing would seem to change for about a minute, when the mouse pointer would jerk on the screen. You can imagine how long it took to type a command on the console.
Replacing the card fixed the problem, but it *could* have been just the act of unplugging the card and replugging the new one. I didn't recheck the old one after satisfying myself that it was the fault of the card.