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 01:03] – [0x04 - Input (read)] eidisx68000:writing_drivers [2014/07/11 01:06] – [0x08 - Output (write)] eidis
Line 238: 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.  | |||Character device driver : Buffer size.  | +|  18  |  Long  |Block device driver : number of sector to read. A sector length is normally specified by the BPB.  | 
 +| | |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 247: Line 248:
 ===== 0x05 - Read no wait ===== ===== 0x05 - Read no wait =====
  
-Command ID : 0x05 (C_NDREAD)+**Command ID :** 0x05 (C_NDREAD)
  
 **Availability :** Character **Availability :** Character
Line 266: Line 267:
 **Availability :** Block **Availability :** Block
  
-**Description :** To check furthermore. This seems to be really X68000 specific floppy drive command, or some kind of kernel hack by Human68k developpers. It does some kind of IOCTL, but internally to the kernel to dis/allow and control of FDD ejection, LEDs or media write protection control...+**Description :** //To check furthermore.// This seems to be really X68000 specific floppy drive command, or some kind of kernel hack by Human68k developpers. It does some kind of IOCTL, but internally to the kernel to dis/allow and control of FDD ejection, LEDs or media write protection control...
  
 ===== 0x06 - Input status ===== ===== 0x06 - Input status =====
Line 304: Line 305:
 ^  Position  ^  Type  ^  Description  ^ ^  Position  ^  Type  ^  Description  ^
 |  14  |  Long  |Pointer to a buffer that contains data to write to the unit.| |  14  |  Long  |Pointer to a buffer that contains data to write to the unit.|
-|  18  |  Long  |Block device driver : number of sector to write. A sector length is normally specified by the BPB.  |||Character device driver : Buffer size.  | +|  18  |  Long  |Block device driver : number of sector to write. A sector length is normally specified by the BPB.  | 
 +| | |Character device driver : Buffer size.  |
 |  22  |  Long  |Block device driver only : logical start sector to write to.  |  |  22  |  Long  |Block device driver only : logical start sector to write to.  |
   
x68000/writing_drivers.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1