D1386 Letter Ballot Comments Resolution
Total Page：16
File Type：pdf, Size：1020Kb
E00132r1 D1386 Letter Ballot Comments Resolution
Comments to accompany the Maxtor Corporation yes vote on the letter ballot for project 1386D.
1m. Title page, Abstract, first sentence, add a hyphen to IA64, i.e., IA-64. a. Accepted 2m. Page after title page, patent statement, why should we see clause 2? a. Delete the “see clause 2” 3m. Table of contents, tables , and figures are in a different font than the rest of the document. a. Will change from Times New Roman to Arial 4m. Pages should be number starting with the value i on the first page of the table of contents. a. Will make the first page number appear 5m. The table of tables has no figure 1. a. Will fix the figure numbering 6m. Page ii, starting with the second paragraph the Forward is in a different font. a. Will change font from times new roman to arial 7m. Page iv, Introduction, some of the sentences are not sentences and some have no period at the end. a. Will add all the periods b. Will change clause 4 to read “Clause 4 is the overview” 8m. Page 1, Scope, bulleted list, the fifth, sixth, and seventh items should end with a semicolon, the last item should end with a period. a. Accepted 9m. Page 2, starting with 2.1, the x.x headings are in the wrong font. a. Will change template to Arial 10m. Page 2, 2.1 Approved references, can technical reports be normative references? a. Move TR-21 to other reference 11m. Page 2, 2.2 References under development, 1394a should move up to the approved list. It is now IEEE 1394a-2000 IEEE Standard for a High Performance Serial Bus – Amendment 1. a. Accepted 12m. Global, do “keep withs” so that headings don’t end by themselves at the bottom of a page. a. Point taken 13m. Page 5, 3.2.13 INT 13h, Floppy, Hard Drive, should not be capitalized. a. Accepted 14m. Page 5, 3.2.14 INT 40 should be INT 40h. a. OK, do we want to put in the h on everything? 15m. Page 5, 3.2.17 Logical address/geometry, global, the document sometimes uses “FN”, sometimes uses “Fn”, and sometimes uses “Function”. Choose one and make it consistent. a. Will change all references to Fn 16m. Page 5, 3.2.18 NV memory, first sentence should say “Non-Volatile memory is memory that retains content even when the power has been shut off. a. Good point 17m. Page 6, 3.2.20 Default address/geometry is out of alphabetical order. a. Will Fix 18m. Page 7, clause 4 Overview, Change INT 13 to INT 13h. This is a global change. a. Will do 19m. Page 8, clause 4 Overview, second paragraph, second sentence, change to “This standard builds on NCITS TR-21 BIOS Enhanced Disk Drive Technical Report to enable other mass storage technologies, such as 1394, Fibre Channel, and USB.” a. Will Do 20m. Page 8, clause 4 Overview, fourth paragraph, first sentence, change to “Data written on media can render the media incompatible with certain drive letters when some drive letter based operating systems are used.” a. OK 21m. Page 8, clause 4 Overview, fifth paragraph, first sentence, change to “One of the important aspects of this standard is to allow a BIOS to describe the physical path to a device.” a. OK 22m. Page 8, clause 4 Overview, figure 2, this is the first figure in the document. a. Will fix 23m. Page 9, 5.1 Data structure, table 1 should be in this subclause not the next one. a. Will move the table to the correct position 24m. Page 10, table 1, offset 4 description, change to “Address of host transfer buffer. The host buffer that Read/Write operations will use to transfer the data. This is a 32-bit host address of the form Seg:Offset. If this field is set to FFFFh:FFFFh then the address of the transfer buffer is found at offset 10h.” a. OK 25m. Page 10, table 1, offset 10 description, change to “64 bit unsigned linear address of the host transfer buffer. This is the host buffer that Read/Write operations will use to transfer the data if the data at offset 4 is set to FFFFh:FFFFh, or the data at offset 2 is set to FFh. a. OK 26m. Page 12, table 3, this should be table 2. a. Interesting, my doc reads correctly 27m. Page 12, 6.3 Extended write, first sentence should say “This function transfers sectors from memory to the device.” The last sentence needs a period. a. OK 28m. Page 15, table 5, this should be table 3. a. My doc reads correctly 29m. Page 15, table 5, offset 0 description should say “The caller sets this value to the maximum buffer length in bytes. If the length of this buffer is less than 30 bytes, this function does not return the pointer to DPT extension. If the buffer length is 30 or greater on entry, it shall be set to 30 on exit. If the buffer length is between 26 and 29, it shall be set to 26 on exit. If the buffer length is less than 26 on entry an error is returned. a. OK 30m. Page 15, table 5, offset 32 description, is the value 44 in fact 44h? a. This is a decimal number, as are the offsets 31m. Page 16, table 7, this should be table 4. a. Fixed 32m. Page 16, table 7, font is different. a. OK 33m. Page 17, table 8, this should be table 5. a. Fixed 34m. Page 17, table 8, font is different. a. OK 35m. Page 18, table 9, should be table 6. a. Fixed 36m. Page 18, 6.8.3.2, is this the base address of the set of Control Block registers or is this the address of the Device Control register? a. Change to The Address of the device control register 37m. Page 19, 6.8.3.7, global change multi-word to multiword. a. OK 38m. Page 19, 6.8.3.7, change 0 to zero and 2 to two. a. OK 39m. Pages 19 and 20, subclauses of 6.8.3.9, change to “bit set to one’ and bit cleared to zero”. a. OK 40m. Page 20, 6.8.3.9.7, change to “If this ATA device implements the PACKET command feature set (ATAPI) as defined in ATA/ATAPI-4, this bit is set to one.” a. OK 41m. Page 20, table 10, this should be table 7. a. Fixed 42m. Page 21, table 12, should be table 8. a. Fixed 43m. Page 21, 6.10, change “2” to “two”, “1” to “one”, and “0” to “zero”. a. OK 44m. Page 22, table 13, should be table 9. a. Fixed 45m. Page 22, table 13, font is different. a. OK
Quantum’s comments for the letter ballot of T13/1386D, rev 4 (EDD) Some comments include more than one suggestion or question.
1q. Global, beginning on page 3 (DOCUMENT STATUS, Revision 2): The font of the document starts out just in Arial. Then other fonts are used beginning with the bulleted list under Revision 2. The font in this document should be changed to be consistent, and, I believe it should be changed to Arial. a. Will change to Arial 2q. Second cover page (PDF page 4) at top: The temporary NCITS document number should reflect year 200X, not 199X. a. Yeah.. 3q. Second cover page (PDF page 4) Foreword: Change "BIOS provided INT 13 interface" to "INT13 programming interface provided by BIOS firmware to higher level software". This distinguishes a software interface from a hardware interface and simplifies the wording. a. OK 4q. PDF page 5, CAUTION: Change "holder's" to "holders" to represent plural form of the noun. a. Gene will supply 5q. Abstract (PDF page 8): Change "personal computers systems" to "personal computer systems" to correct grammar. Both words should not be plural. a. OK 6q. page iii (PDF page 9), Foreword: At the time this document was submitted for letter ballot, Dan Colegrove had resigned from T13 and Mark Evans was the secretary. a. Gene will supply a new list 7q. Global (first occurrence, page 1, PDF page 11): It appears as if some of the characters did not translate properly from the Word document to the PDF document. At least some dashes and bullets appear as one or two question marks in the PDF document. a. OK 8q. Page 1 (PDF page 11) Scope: Add a sentence to the first paragraph saying something like, "To comply with this standard, higher-level software (the “caller”) or lower-level BIOS firmware (the “callee”) shall support the functions and data structures described in this document." This is to cover the lack of "shall" in many places and to describe the entities responsible for implementing the standard. Ideally, a software interface would describe each requirement as, "the caller shall perform software interrupt ## and provide these parameters", and, "the callee shall provide this data structure", etc. a. How about: To comply with this standard, higher level software shall call the INT functions using the data structures described herein; and system firmware shall provide the INT functions and data structures described herein. 9q. Page 2 (PDF page 12), 2.2 References under development: Add document titles and parenthesize acronyms to read "AT Attachment with Packet Interface (ATA/ATAPI-5)", "SCSI Primary Commands - 2 (SPC-2)", and Multi-Media Commands - 3 (MMC-3)". a. Spell out the names 10q.Page 2 (PDF page 12), 2.3 Other references: The WWW link for Mass Storage Overview is not fully underlined. a. OK 11q.page 3 (PDF page 13), Definitions, abbreviations, and conventions: The title of this clause is, “Definitions, abbreviations, and conventions”. However, the subclauses are, “Keywords” and “Definitions and abbreviations”. One way or the other, this should be made consistent. a. Change the title to Keywords, Definitions, abbreviations, and conventions 12q.page 3 (PDF page 13), Keywords: It is more typical for me to see the format of definitions in standards to be “word_to_be_defined: definition words.” Implementing this format in addition to implementing the recommendation in Quantum comment 13 might save a page in the document. a. Rejected 13q.page 3 (PDF page 13), Keywords: I searched both the .doc and .pdf files and could find no occurrence of the words “expected”, “obsolete”, “retired”, or any of their variants. Since these words are not used in the standard, I would recommend deleting them. a. Accepted 14q.Global (first occurrence, page 4, PDF page 14, 3.2.1 ATA): Italics are used in several places. First of all, I don’t think Italics are allowed in NCITS standards. Second, they are used inconsistently for this purpose. The following example is the format that I recommend should be used in this clause (please note as to how the abbreviation and its “spelled out” name are handled; only the abbreviation should be used from this point forward in the document): 3.2.1 ATA (Advanced Technology Attachment): An ATA drive, also known as an IDE drive, is a hard drive that conforms to an ATA standard. a. Will remove the italics from the definitions 15q.Page 4 (PDF page 14, 3.2.4: The term "Boot Device" is not used in the document, so this definition is unnecessary and should be deleted. a. OK 16q.PDF page 4, (PDF page 15) 3.2.6 CHS: I think this should be changed to something like, “CHS addressing: CHS addressing is a method of addressing the contents of a storage device using logical cylinders (C), logical heads (S), and logical sectors (S). This method of accessing allows a maximum C=16383, H=16, S=63, or 8.4GB. See LBA addressing for another addressing method.” a. OK 17q.Global (first occurrence, page 4, PDF page 14, 3.2.6 CHS): The term "access" is so general it can refer to connecting or even turning on the power. Because of this, the document should be searched for other occurrences, and the following changes should be made where appropriate: "accessing" to "addressing", "access" to "addressing", and "accessed" to "addressed" to be more specific. a. OK 18q.Page 4 (PDF page 14), 3.2.7 Conventional vs enhanced (this is the first occurrence of what should begin a global search of the document): The “which” shall be changed to a “shall”. Please search the document and replace all “which”s accordingly. a. Will change “which” to “that” 19q.page 4 (PDF page 14), 3.2.8 DOS [this may be a global]: I think that a “TM” or a “REG TM” or something needs to be used with MS-DOS, et al., as appropriate. a. I can place a R by these… b. Change DOS operating systems to DOS BASED operating systems c. Add Free DOS 20q.Page 4/5 (PDF page 14/15), 3.2.9 DWord: Clarify the meanings of "first" and "last" since they usually refer to time. Replace the sentence with "Byte 0 of a Dword is stored in the lowest byte address and Byte 3 is stored in the highest byte address". a. OK 21q.Page 5 (PDF page 15), 3.2.11 IA-32 (the first of several): This is the first of several definitions in this subclause that are incomplete sentences. I recommend that this be changed to, “IA-32: IA-32 refers to the Intel Architecture 32-bit wide processor data bus.” The sentence in the subclause following this subclause and others in this clause should be made into complete sentences a. OK. Will change IA-32 and IA-64 definitions b. Mike Eschman will find out if a tm or R is required 22q.Page 5 (PDF page 15), 3.2.16 LBA: This definition is not correct. An LBA is a logical block address. I think that this should be the definition for this term. In addition, I think there should then be a definition for “LBA addressing”. This could be: “LBA addressing is a method of addressing the contents of a storage device as a contiguous set of LBAs. This method of accessing allows a maximum LBA of 2^28 -1, or 137.4GB of data. See CHS addressing for another addressing method.” a. We debated this one and the current definition was the result b. I would like to leave this one the same 23q.page 5 (PDF page 15), 3.2.17 Logical Address/Geometry: Neither the term "logical address" or "logical geometry" is used in the document. This definition is unrelated to the similar term "logical block address" and doesn't mention CHS. Let's define "geometry" as "the maximum values for cylinder, head, and sector numbers used in CHS addressing". a. Rejected 24q.Page 6 (PDF page 16), QWord: Clarify the meanings of "first" and "last" since they usually refer to time. Replace the sentence with "Byte 0 of a Qword is stored in the lowest byte address and Byte 7 is stored in the highest byte address". a. Fine 25q.Page 6 (PDF page 16), 3.2.20 Default Address/Geometry: Not needed if "geometry" is defined per previous comment. a. Remove this definition 26q.Page 6 (PDF page 16), 3.2.22 Protect Mode: Change "Intel x86 based computer systems" to "Intel x86 processors" since other system components don't know about memory protection. Change "modes of operation" to "modes of main memory addressing" to be more specific. a. OK 27q.Page 6 (PDF page 16), 3.2.25 System Vendor: Change "Protected Area" to "Host Protected Area of a storage device (see ATA/ATAPI-5 or higher). Add a reference to the PARTIES standard after "Service Areas". On the other hand, none of these three terms are used in this document, so this definition may be deleted. a. Lets delete it. 28q.Page 6 (PDF page 16), 3.2.26 Warm boot: This term is used nowhere else in the document; delete the definition. Or, if we keep it, add, "A host may initiate a soft reset on a device by setting SRST in the Device Control register to one (see ATA/ATAPI-5).” a. Delete it 29q.Page 7 (PDF page 17), 3.2.27 Word: Clarify the meanings of "first" and "last" since they usually refer to time. Replace the sentence with "Byte 0 of a Word is stored in the lower byte address and Byte 1 is stored in the higher byte address". Add byte numbers to the figure. The figure's left-to-right orientation is not clear for "In Memory". a. OK, OK, OK… 30q.Page 7 (PDF page 17), Overview: Make all "INT 13" and "INT 13h" uses the same. Change the last sentence to read, "This standard defines an extended INT 13 interface. The purpose of these INT 13 extensions is to:” a. Will change all INT 13 to INT 13h 31q.Page 8 (PDF page 18), Overview: In the second full paragraph (starting with "DOS"), change "…can…" to "…will gain the capability to consistently…". This avoids the spec-like interpretation of the word "can". a. OK 32q.Page 8 (PDF page 18), Overview: In third full paragraph (starting with "Media"), change "can have" to "has been seen with". This avoids the spec-like interpretation of the word "can". Change, "Compatibility with this standard requires that operating systems…" to "Operating systems shall…" a. OK 33q.Page 8 (PDF page 18), 5 INT 13 Calling Conventions: This states. "…the extended INT13 functions are numbered 41h-48h…", but also describes functions 49h, 4Eh, 50h, and 52h in sections 6 and 7. Please reconcile and clarify this inconsistency. a. Good point. I will change the reference to read: are numbered from 41h through 49h, 4E, and 50h. 34q.Global (beginning on page 8 (PDF page 18), 5 INT 13 Calling Conventions): I thought that the NCITS editors wanted bulleted list to use some form of a hyphen or dash. If so, the document should be searched and changed accordingly. a. I have used dashes throughout… 35q.Page 8 (PDF page 18), 5 INT 13 Calling Conventions: In the second paragraph, change first sentence to, "The caller shall specify a device number in the DL register when calling functions 41h-48h." I shall now try to stop converting sentences from passive to active voice. a. OK 36q.Page 9 (PDF page 19), 5.2 Removable Media: Change "The distinction ….. differ" to "The distinction ….. differs" to correct grammar. a. OK 37q.Global (first occurrence, Page 10 (PDF page 20), Table1, offset 0, description, second sentence): The sentence should be changed from, “If the packet size is less than 16 the request is…” to “If the packet size is less than 16 the request shall be…” There are several places in this table and in the text in the remainder of the document where a similar change should be made. a. I will change this one, but I am concerned about making wording changes without the concent of the group 38q.Page 10 (PDF page 20), Table1, offset 2: Move the third sentence to the end and change "If a value greater than 127" to "If any other value". This is clearer for both signed and unsigned interpretations. a. OK 39q.Page 10 (PDF page 20), Table 1, offset 4, description (this could be a global): Change the “will” to “shall”. Please search the rest of the document and remove the “will”s. a. The wills appear to only be in 3 places. i. (Table 1 offset 4) The buffer that Read/Write operations will use to transfer the data ii. (Table 1 offset 10) This is the buffer that Read/Write operations will use to transfer iii. (6.6) This function will eject media from the specified device iv. (Table 5, offset 2) , a 0 bit indicates the feature is not available and will operate in a manner v. (6.11) This function defines a service that the system BIOS will call for sending data vi. (6.11) The BIOS will provide this service before the OS is loaded vii. (6.11) . This means that the BIOS will not process asynchronous 1. I think the will should stay here… viii. (6.11) The BIOS will send commands to devices and wait for responses ix. (6.11) The operating system will reconfigure the interface and hook the service described above 40q.Page 10 (PDF page 20), Table 1, offset 8: Change "the following formula holds true" to "the callee shall convert this LBA to a CHS using the current geometry in the following formula". a. OK 41q.Page 10 (PDF page 20), note below Table 1: This content of this note should be separated into separate notes and included at the bottom of the table a. Are you saying you want this included in the table boundaries? If so, OK 42q.Page 10 (PDF page 20), INT 13h interface subsets: Change the comma to a semicolon to correct grammar. a. OK 43q.Global: Change the 9 occurrences of "disk address packet" to be like the 4 occurrences of "device address packet" so that they all use the same term. a. Good point 44q.Page 10-11 (PDF page 20-21), INT 13h interface subsets: If only "at least one of" the three interface subsets is required, explain how the second (5.3.2) and third (5.3.3) subsets provide any read-write capability by themselves, since they have no read-write commands listed in their contents. a. Note: Conventional INT 13 may be used for media accessing if the Fixed disk access subset is not present 45q.Page 12 (PDF page 22), Table 2: Change the title to "Extensions present buffer" to agree with the name of the calling function. a. OK 46q.Page 13 (PDF page 23), 6.5 Lock/Unlock Media: In the next-to-last sentence, change "system software operates" to "caller may operate" to be more specific. a. OK 47q.Page 15(PDF page 25), Result buffer, offset 26: To clarify the last sentence, explain what replaces the DPTE in non-legacy ATA HDD configurations. What is the difference between legacy and non-legacy ATA HDD configurations? a. Change to: This field is only used for legacy INT 13 based systems configured with ATA or ATAPI devices 48q.Page 16 (PDF page 26), Table 3, offset 73 (also DPTE page 18): Clarify that, when performing 2's complement summation, carries and overflows out of the byte arithmetic are ignored as each byte is added, or explain the other algorithm. Is SIGNED or UNSIGNED arithmetic more appropriate in C? Is the algorithm the same as in ATA-5 for IDENTIFY and SMART information? Should we reference those? Should we include an example (such as Data FFh and 02h => checksum FFh)? a. Change: sum to unsigned sum 49q.Page 18 (PDF page 28), Table 6, Device parameter table extension, offset 4: In the description, remove the words "upper nibble"; they are unnecessary and confusing. a. Change Head Register to DEVICE/HEAD register b. Remve upper nibble reference 50q.Page 18 (PDF page 28), Table 6, Device parameter table extension, offset 14, and 6.8.3.11: Do versions earlier than 11h exist for this table format? If so, they should also be documented. a. There are no earlier versions 51q.Page 18 (PDF page 28), 6.8.3.1 and 6.8.3.2: Change "address of" to "16-bit address in I/O space of" to be more specific. a. OK 52q.Page 19 (PDF page 29), 6.8.3.5 IRQ number: Change "interrupt" to "assigned interrupt level" to be more specific. a. Change to: Assigned Interrupt Number 53q.Page 19 (PDF page 29), 6.8.3.7 Offset 8 - DMA channel/Multiword DMA Type: The document SFF-8038i is called out in this clause. However, there are several issues with this: 1) this document is not referenced in either clause 2.1 Approved references or clause 2.2 References under development, 2) I believe that the actual document designation is currently INF-8038i in the SFF document, and, 3) there is no there there, i.e., the document is listed by SFF as “expired” and the content of the document is not included in the SFF CD. a. One possibility: ATA channels that support PCI DMA bus mastering shall set the DMA channel to 0 54q.Page 19 (PDF page 29), 6.8.3.9 BIOS selected hardware specific option flags: Change "current system configured enabled" to "current hardware options enabled" to correct the grammar. a. OK 55q.Page 20 (PDF page 30), 6.8.3.9.11: Please clarify the referenced section title in the second sentence where it says "If this bit and bit 1, section (See section 6.8.3.9.2),". Should the first "Section" be "fast DMA"? a. Yes, I will add the section name 56q.Page 22 (PDF page 32), 6.11 Send Packet Command: In the first full paragraph, change "system BIOS will call" to "system BIOS provides", assuming this is part of the same interface being standardized. a. Changed will to shall throughout this section. I think should probably do it. 57q.Page 23 (PDF page 33), 7 INT15h removable media eject: Please restate "This function is called in response to a software request" to assign responsibilities if this is part of the same software interface or to identify the caller and callee if part of a different interface. If designed for a callback from interface callee to interface caller, please explain. a. Change: “This function is call in response to” to “this function is called by the BIOS in response to”
Comments with Gene Milligan’s Yes vote. Page numbers are pdf pages: Notes from d1386r4.pdf
1s. Page 2 Note 1; ITIC has changed their Email address to itic.org. a. OK 2s. Page 2 Note 2; Please add the unsubscribe information for the reflector. a. OK 3s. Page 4 Note 1; Font differences have changed em-dashes into ? marks. a. Got it 4s. Page 4 Note 2; Should IA-32 be IA32 or should IA64 be IA-64. a. I will make all IA references to IA- 5s. Page 4 Note 3; I thought I2O was a software or host interface not a storage interface. a. Storage can be connected to I2O. I placed this here in response to a request from Intel 6s. Page 5 Note 1; The patent statement is out of date as can be determined by holders being possessive rather than plural. Replace with updated statement. a. Need words… 7s. Page 8 Note 1; As much as I would like them to, the 1900s will not return. Please change <