NFG Games + GameSX

User Tools

Site Tools

Trace:
x68000:writing_drivers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
x68000:writing_drivers [2014/07/11 00:54] – eidisx68000:writing_drivers [2014/07/11 01:04] – [0x05 - Read no wait] eidis
Line 13: Line 13:
  
 **Note :** the following contains very hard stuff ! I might be confusing sometimes, sorry in advance. Don't hesitate to ask for help if you do not understand something. Thank you. **Note :** the following contains very hard stuff ! I might be confusing sometimes, sorry in advance. Don't hesitate to ask for help if you do not understand something. Thank you.
- 
- 
- 
- 
- 
  
 **Terminology :** **Terminology :**
Line 25: Line 20:
   * Char : 1 character = 1 byte   * Char : 1 character = 1 byte
   * All data types are CPU specific : M68K family. So, byte ordering is always "Big Endian" and a pointer is 32 bits (long).   * All data types are CPU specific : M68K family. So, byte ordering is always "Big Endian" and a pointer is 32 bits (long).
- 
  
 ====== Compilation flags, libraries and startup code ====== ====== Compilation flags, libraries and startup code ======
Line 93: Line 87:
 **Command execution result flags :** **Command execution result flags :**
  
-This list contains all acceptable values to fill the result status flags in the request packet header. S_**** flags will display (or hide) the "A"bort, "R"etry and "I"gnore line, and E_**** will show an appropriate error message. "Result status" member can be any combination of S_**** flags (ORed together), but only one E_**** can be set.+This list contains all acceptable values to fill the result status flags in the request packet header. S_**** flags will display (or hide) the "A"bort, "R"etry and "I"gnore line, and E_**** will show an appropriate error message. 
 + 
 +"Result status" member can be any combination of S_**** flags (ORed together), but only one E_**** can be set.
  
   * 0x1000 - S_ABORT : "A"bort the whole request.   * 0x1000 - S_ABORT : "A"bort the whole request.
Line 159: Line 155:
  
   
-Output parameters :+**Output parameters :**
  
 ^  Position  ^  Type  ^  Description  ^ ^  Position  ^  Type  ^  Description  ^
Line 224: Line 220:
  
 ^  Position  ^  Type  ^  Description  ^ ^  Position  ^  Type  ^  Description  ^
-|  14  |  Long  |  Pointer to a buffer that'll contain readed data from the unit. The driver is responsible of filling this buffer.  | +|  14  |  Long  |Pointer to a buffer that'll contain readed data from the unit. The driver is responsible of filling this buffer.  | 
-|  18  |  Long  |  Buffer size  |+|  18  |  Long  |Buffer size  |
   
 **Output parameters :** none **Output parameters :** none
Line 231: Line 227:
 ===== 0x04 - Input (read) ===== ===== 0x04 - Input (read) =====
  
-Command ID : 0x04 (C_INPUT)+**Command ID :** 0x04 (C_INPUT)
  
 **Availability :** Block/Character **Availability :** Block/Character
Line 242: Line 238:
 |  13  |  Byte  |Block device driver only. Media type.  |     |  13  |  Byte  |Block device driver only. Media type.  |    
 |  14  |  Long  |Pointer to a buffer that'll contain the readed data from the unit.The driver is responsible of filling this buffer.  | |  14  |  Long  |Pointer to a buffer that'll contain the readed data from the unit.The driver is responsible of filling this buffer.  |
-|  18  |  Long  |Block device driver : number of sector to read. A sector length is normally specified by the BPB. +|  18  |  Long  |Block device driver : number of sector to read. A sector length is normally specified by the BPB.  | 
-Character device driver : Buffer size.  | +| | |Character device driver : Buffer size.  |
 |  22  |  Long  |Block device driver only : logical start sector to read from.  | |  22  |  Long  |Block device driver only : logical start sector to read from.  |
  
Line 252: Line 248:
 ===== 0x05 - Read no wait ===== ===== 0x05 - Read no wait =====
  
-Command ID : 0x05 (C_NDREAD)+**Command ID :** 0x05 (C_NDREAD)
  
 **Availability :** Character **Availability :** Character
x68000/writing_drivers.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1