x68000:writing_drivers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| x68000:writing_drivers [2014/07/11 01:02] – [0x04 - Input (read)] eidis | x68000:writing_drivers [2019/08/27 20:45] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| The following information was kindly contributed by our forum member **Lydux**. | The following information was kindly contributed by our forum member **Lydux**. | ||
| + | |||
| + | Original thread can be found here: | ||
| + | http:// | ||
| So I've decided to share with you some of my study and work. | So I've decided to share with you some of my study and work. | ||
| Line 238: | Line 241: | ||
| | 13 | Byte |Block device driver only. Media type. | | | 13 | Byte |Block device driver only. Media type. | | ||
| | 14 | Long |Pointer to a buffer that' | | 14 | Long |Pointer to a buffer that' | ||
| - | | 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 248: | Line 251: | ||
| ===== 0x05 - Read no wait ===== | ===== 0x05 - Read no wait ===== | ||
| - | Command ID : 0x05 (C_NDREAD) | + | **Command ID :** 0x05 (C_NDREAD) |
| **Availability :** Character | **Availability :** Character | ||
| Line 267: | Line 270: | ||
| **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 308: | ||
| ^ Position | ^ Position | ||
| | 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. | | ||
| - | + | ||
| **Output parameters :** none | **Output parameters :** none | ||
x68000/writing_drivers.1405004534.txt.gz · Last modified: 2019/08/27 20:44 (external edit)