This message is from the T13 list server.
Please clarify what you mean by:
"There are drive vendors who are stuffing the
identify page in the techincal wrong place."
What, specifically, is incorrect in the IDENTIFY data ?
Thanx !!!
-----------------------------------------------------------------
Jim Hatfield
ATA Interface Firmware
Seagate Technology - PSG
e-mail: [EMAIL PROTECTED]
s-mail: 389 Disc Drive; Longmont, CO 80501 USA
voice: 720-684-2120
fax : 720-684-2711
====================================================
Andre Hedrick
<t13@linux-id To: Gary Laatsch
<[EMAIL PROTECTED]>
e.org> cc: "T13 (E-mail)" <[EMAIL PROTECTED]>
Sent by: Subject: Re: [t13] 48BIT Supported Poll
owner-forum@t
13.org
No Phone Info
Available
09/24/2002
05:53 PM
This message is from the T13 list server.
Gary,
If you are not checking the DCO identify page, the presences of any HPA
regions, while looking at words 100-103 you are toast. This is kind of
overkill, but what needs to happens is to restrict the usage of words
100-103 to devices addressing beyond 137GB. There are drive vendors who
are stuffing the identify page in the techincal wrong place. However,
this is expected so one deals with it and moves on.
SET_MAX_EXT needs to be tested against words 100-103, ideally.
Comments?
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Tue, 24 Sep 2002, Gary Laatsch wrote:
> This message is from the T13 list server.
>
>
> Question to all the drive folks.......
>
> There seems to be a fuzzy area about use of the 48-bit addressing
> supported bit in the IDENTIFY DATA (bit 10 of WORD 83). I guess some
> are setting this bit regardless of the drive capacity and some are only
> setting it if the capacity is over 137GB. I am hearing "rumors" that
> this might be creating some driver issues because of the SET MAX and SET
> MAX EXT commands.
>
> Just wondering how you drive folks are setting this?
>
> Gary Laatsch
> Principal Engineer
> Mass Storage
> Phoenix Technologies Ltd.
> Office: 949-790-2107
> Fax: 949-790-2001
> [EMAIL PROTECTED]
>
> "Working code is good code, good code is not always working code...."
> - Craig Llewellyn (my first firmware manager) circa 1978
>
>
>
