Re: [PATCH] 2.5.18 IDE 73

Martin Dalecki
2002-05-29T14:43:41Z

Russell King wrote:
> On Wed, May 29, 2002 at 03:03:27PM +0200, Martin Dalecki wrote:
>
>>Dear Gerald please look closer. The hdparm -i is executing the
>>drive id command directly and does *not* rely on the internally
>
>
> hdparm -i uses the HDIO_GET_IDENTITY ioctl, which returns drive->id.
> It doesn't obtain the ID from the drive. hdparm -I asks the
> identity from the drive.

Yes. But this will be just changed soon, since there
is no reaons at all to don't just read it always from the drive, in esp.
in face of the above.

BTW.> The above function was only used when the user
invoked ioctl() - that was my point.

> hdparm --help gives some hints:
>
> -i display drive identification
> -I read drive identification directly from drive
>
> and the man page is quite clear:
>
> -i Display the identification info that was obtained
> from the drive at boot time, if available. This is
> a feature of modern IDE drives, and may not be sup­
> ported by older devices. The data returned may or
> may not be current, depending on activity since
> booting the system. However, the current multiple
> sector mode count is always shown. For a more
> detailed interpretation of the identification info,
> refer to AT Attachment Interface for Disk Drives
> (ANSI ASC X3T9.2 working draft, revision 4a, April
> 19/93).
>
> -I Request identification info directly from the
> drive, which is displayed in its raw form with no
> endian changes or corrections. Text strings may
> appear mangled when using -I but that is NOT a bug.
> Otherwise similar to the -i option.
>

--
- phone: +49 214 8656 283
- job: eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!)
- langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort: ru_RU.KOI8-R