User Tools

Site Tools


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:04] – [0x05 - Read no wait] eidisx68000:writing_drivers [2014/07/11 01:06] – [0x08 - Output (write)] eidis
Line 267: 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 305: 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