** This is the quasi-official and semi-temporary T13 email list server. **
Michael,
You made a point I was going to bring you is that by allowing the BIOS
guys to inc++ by one the 28-bit capacity it roles to ZERO, that provides
the case to exclusive 48-bit and forced LBA and the complete death of CHS.
Now if the BIOS imposes the inc++ and the content of 28bit cpacity becomes
zero, then it is the HOST driver that has to know what to look for and
handle.
if (atadevice->28bitcapacitypointer & 0x0FFFFFFF)
or
if (atadevice->28bitcapacitypointer & 0x10000000)
This is a quick test to see that we are going to be forced into doing
48-bit things.
That is all.
The problem is that nobody will accept when a mistake is made and it is a
back scratch fest. Almost to the point of two wrongs to make a right.
This is not optics or the hubble, sometimes less stable than the latter.
Everyone here knew about the problem yet chose not to fix it.
We are doing 48-bit and not 64-bit because it is path of least effort.
We all know that 64-bit is where we go next regardless that the physical
capacity to 144pb is not going to happen for a long time.
I just want to be `completely lazy' and do it right the first time and
only once, as to not have to repeat.
Moral battle no, retentive and exact YES.
Cheers,
Andre Hedrick
CTO ASL, Inc.
Linux ATA Development
On Wed, 15 Aug 2001, Eschmann, Michael K wrote:
> Date: Wed, 15 Aug 2001 09:36:27 -0700
> From: "Eschmann, Michael K" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: [temp t13] Re: Read Native Max in ATA/ATAPI-6
>
> ** This is the quasi-official and semi-temporary T13 email list server. **
>
> Andre, I totally disagree with you.
>
> The burden of this issue will be on drive vendors, not the platform folks,
> when a PC owner buys a disk to add on and it does not work. You want to add
> this burden just because you want to have a moral battle with BIOS folks?
> Give me a break!
>
> The best thing to do is not require this field to be 0x0FFFFFFF, but rather
> this is it's limit. Besides, who are we to say that if a drive can do above
> this limit, that the 28-bit commands must actually be able to use exactly
> this limit. I may want to limit use of 28-bit to say ZERO and force
> everyone to use 48-bit commands (trying to be funny here, so lighten up).
>
> BTW, I hope the new company is treating you well.
>
> Regards, MKE.
>
>
>
> -----Original Message-----
> From: Andre Hedrick [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 11:22 PM
> To: [EMAIL PROTECTED]
> Subject: [temp t13] Re: Read Native Max in ATA/ATAPI-6
>
>
> ** This is the quasi-official and semi-temporary T13 email list server. **
>
>
> Then that is a broken BIOS HOST...make them fix their problem and not us
> clean up their mess.
>
> Regards,
>
> Andre Hedrick
> CTO ASL, Inc.
> Linux ATA Development
>
> On Mon, 13 Aug 2001, Daniel J Colegrove wrote:
>
> > Date: Mon, 13 Aug 2001 08:55:57 -0700
> > From: Daniel J Colegrove <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: [temp t13] Read Native Max in ATA/ATAPI-6
> >
> > ** This is the quasi-official and semi-temporary T13 email list server.
> **
> >
> > In ATA/ATAPI-6 we put in a statement that for drives larger than
> > 0FFFFFFFh logical blocks Read Native Max shall return 0FFFFFFFh
> > blocks. This conflicts with the compatibility issue we noted earlier
> > that some BIOS may add 1 to the number returned to get the maximum
> > number of sectors, roll over, and have an error. Read Native Max
> > should be changed to a maximum value of 0FFFFFFFh so devices
> > can return 0FFFFFFEh, avoiding the problem.
> >
> > Best Regards,
> > DC
> >
> > Dan Colegrove
> > Senior Technical Staff Member
> > Storage Technology Division
> > IBM Corporation
> >
> > 702-614-6119
> > 702-614-7955 fax
> > Tie Line 280-9959 (IBM internal)
> > [EMAIL PROTECTED]
> > --
> > If you have any questions or wish to unsubscribe send a
> > message to Hale Landis, [EMAIL PROTECTED] To post to
> > this list server send your message to [EMAIL PROTECTED]
> >
> > For questions concerning Thistle Grove Industries or TGI's
> > list services please send email to [EMAIL PROTECTED]
> >
> >
> >
>
> --
> If you have any questions or wish to unsubscribe send a
> message to Hale Landis, [EMAIL PROTECTED] To post to
> this list server send your message to [EMAIL PROTECTED]
>
> For questions concerning Thistle Grove Industries or TGI's
> list services please send email to [EMAIL PROTECTED]
>
>
>
> --
> If you have any questions or wish to unsubscribe send a
> message to Hale Landis, [EMAIL PROTECTED] To post to
> this list server send your message to [EMAIL PROTECTED]
>
> For questions concerning Thistle Grove Industries or TGI's
> list services please send email to [EMAIL PROTECTED]
>
>
>
--
If you have any questions or wish to unsubscribe send a
message to Hale Landis, [EMAIL PROTECTED] To post to
this list server send your message to [EMAIL PROTECTED]
For questions concerning Thistle Grove Industries or TGI's
list services please send email to [EMAIL PROTECTED]
