RE: [t13] Automatic ATA device / host mode sync

[Mark Overby]

Title: Automatic ATA device / host mode sync

So, on parallel ATA the method for locking the timings is going to be specific to each manufacturer as they are going to use different PLL's, clocking technologies, it will depend on the modes, upstream interfaces, etc. The absolute LAST thing you want is a controller to be sniffing the commands that are going out and making programming decisions based on those commands. It leads to all sorts of nastyness. See PATA->SATA bridge as an example.

 

That's what ACPI is for.... (for an integrated controller)

 

More answers:

*When is someone going to design a "TrueRAID" controller that hides the devices when programming at the ATA
*command/ports level?

There are controllers that do this today. There are controllers that don't. Both approaches are valid for different reasons.

*For the chipset/BIOS guys, It would be nice if the RAID controller could have two modes - RAID / Non-RAID in
*which the PCI class codes reflect the mode it's in.  (Also be sure to use UDMA on your int 13h interface - many
*highpoint based implementations use PIO 0 via int 13h)

Most if not all do reflect an 0104 class code when in RAID. (Not all do, but most do)

As far as your SMART comment goes, I'll leave that to be answered by one of the drive guys. That being said, I've heard compelling reasons before for why they don't open up that level of detail.

Remember ATA != SCSI. :)

 

---

From: [EMAIL PROTECTED] on behalf of David F.
Sent: Fri 6/17/2005 9:27 AM
To: Forum@t13.org
Subject: [t13] Automatic ATA device / host mode sync

I'm not sure if this has been addressed but this was something I came across quite a while ago that was annoying.

Using the SET FEATURES to set the various modes, such as PIO mode, doesn't seem to have any affect unless you reprogram the host - which requires figuring out the chipset.  It seems to me there should  be a standard that the host automatically syncs to whatever mode the device gets set too (or vise-versa)  or that there be a well defined standard of setting up the host mode as well.  (Including RAID "controllers").

ALSO:

When is someone going to design a "TrueRAID" controller that hides the devices when programming at the ATA command/ports level?

For the chipset/BIOS guys, It would be nice if the RAID controller could have two modes - RAID / Non-RAID in which the PCI class codes reflect the mode it's in.  (Also be sure to use UDMA on your int 13h interface - many highpoint based implementations use PIO 0 via int 13h)

When is SMART going to be standardized so that recovery / security tools have one standard to work from to get key information like relocation table size, number of bad sectors relocated, which sectors have been relocated to where, ability to enable/disable relocation, sectors that are starting to encounter errors, device level problems like temp, spin up problems, etc.  Right now, it's not standard.

--
David F.
TeraByte Unlimited
http://www.terabyteunlimited.com