From: Mark Lord <kernel@teksavvy.com>
To: James Cloos <cloos@jhcloos.com>
Cc: Stan Hoeppner <stan@hardwarefreak.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: AMD 890GX vs 6Gbps SATA?
Date: Tue, 16 Nov 2010 09:31:35 -0500 [thread overview]
Message-ID: <4CE295C7.7090808@teksavvy.com> (raw)
In-Reply-To: <m3aalajry7.fsf@jhcloos.com>
On 10-11-15 02:40 PM, James Cloos wrote:
>>>>>> "SH" == Stan Hoeppner<stan@hardwarefreak.com> writes:
>
>>> * Gen3 signaling speed (6.0Gb/s)
>
> SH> That's what I was looking for--confirms it's def a 6Gb drive.
>
> Yes.
>
> And thanks for the reminder that hdparm -I is no longer a raw (and
> wrong-endian) dump of the -i info. I'd forgotten that. It even
> works on my usb-storage backup drive, where hdparm -i fails.
Heh heh.
Just for historical background, the reason they work(ed) that way,
is hdparm was originally written (by me) for testing the new Linux IDE
driver subsystem. Well, okay, it *was* "new" back in the mid-90s. :)
The -i reported what the device driver probed from the drive at boot time,
and -I always interrogated the drive itself, and displayed the raw data
exactly as the drive reported it. Thus, for some early drives, the data
looked good, and for others it was byte-swapped.
Eventually ATA standardization kicked in, and all modern drives now agree
on the correct byte-ordering, so I changed -I to give human readable output. :)
Cheers
next prev parent reply other threads:[~2010-11-16 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2DEEA3AB13739D45A22ADDB5086AEA0B915107@sshaexmb1.amd.com>
2010-11-15 7:45 ` AMD 890GX vs 6Gbps SATA? Huang, Shane
2010-11-15 16:31 ` James Cloos
2010-11-15 17:02 ` Huang, Shane
2010-11-15 17:11 ` James Cloos
[not found] ` <4CE179B4.4090404@hardwarefreak.com>
[not found] ` <m3fwv2ju9y.fsf@jhcloos.com>
2010-11-15 19:33 ` Stan Hoeppner
2010-11-15 19:40 ` James Cloos
2010-11-16 14:31 ` Mark Lord [this message]
2010-11-16 10:04 ` Huang, Shane
2010-11-17 0:31 ` Stan Hoeppner
2010-11-17 0:38 ` Stan Hoeppner
2010-11-17 2:48 ` Huang, Shane
2010-11-14 17:50 James Cloos
2010-11-15 4:08 ` Jeff Garzik
2010-11-15 16:39 ` James Cloos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE295C7.7090808@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=cloos@jhcloos.com \
--cc=linux-ide@vger.kernel.org \
--cc=stan@hardwarefreak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.