source: xtideuniversalbios/trunk/XTIDE_Universal_BIOS/Src/Device/Serial/SerialCommand.asm@ 485

Last change on this file since 485 was 480, checked in by aitotat@…, 12 years ago

Changes to XTIDE Universal BIOS:

  • XT-CF DMA transfers should now work.
File size: 7.8 KB
Line 
1; Project name : XTIDE Universal BIOS
2; Description : Serial Device Command functions.
3
4;
5; XTIDE Universal BIOS and Associated Tools
6; Copyright (C) 2009-2010 by Tomi Tilli, 2011-2012 by XTIDE Universal BIOS Team.
7;
8; This program is free software; you can redistribute it and/or modify
9; it under the terms of the GNU General Public License as published by
10; the Free Software Foundation; either version 2 of the License, or
11; (at your option) any later version.
12;
13; This program is distributed in the hope that it will be useful,
14; but WITHOUT ANY WARRANTY; without even the implied warranty of
15; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16; GNU General Public License for more details.
17; Visit http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
18;
19
20; Section containing code
21SECTION .text
22
23%define SERIALSERVER_AH_ALREADY_HAS_COMMAND_BYTE
24%define SERIALSERVER_NO_ZERO_SECTOR_COUNTS
25
26;--------------------------------------------------------------------
27; SerialCommand_OutputWithParameters
28; Parameters:
29; BH: Non-zero if 48-bit addressing used
30; (ignored at present as 48-bit addressing is not supported)
31; BL: IDE Status Register bit to poll after command
32; (ignored at present, since there is no IDE status register to poll)
33; ES:SI: Ptr to buffer (for data transfer commands)
34; DS:DI: Ptr to DPT (in RAMVARS segment)
35; SS:BP: Ptr to IDEREGS_AND_INTPACK
36; Returns:
37; AH: INT 13h Error Code
38; CX: Number of successfully transferred sectors (for transfer commands)
39; CF: Cleared if success, Set if error
40; Corrupts registers:
41; AL, BX, CX, DX, (ES:SI for data transfer commands)
42;--------------------------------------------------------------------
43ALIGN JUMP_ALIGN
44SerialCommand_OutputWithParameters:
45
46 mov ah,SerialServer_Command_Read
47
48 mov al,[bp+IDEPACK.bCommand]
49
50 cmp al,20h ; Read Sectors IDE command
51 jz .readOrWrite
52 inc ah ; now SerialServer_Protocol_Write
53 cmp al,30h ; Write Sectors IDE command
54 jz .readOrWrite
55
56; all other commands return success
57; including function 0ech which should return drive information, this is handled with the identify functions
58;
59 xor ah,ah ; also clears carry
60 ret
61
62.readOrWrite:
63 call IdeTransfer_NormalizePointerInESSI
64 mov [bp+IDEPACK.bFeatures],ah ; store protocol command
65
66 mov dx, [di+DPT_SERIAL.wSerialPortAndBaud]
67
68ALIGN JUMP_ALIGN
69SerialCommand_FallThroughToSerialServer_SendReceive:
70
71%include "SerialServer.asm"
72
73%ifndef CHECK_FOR_UNUSED_ENTRYPOINTS
74 %if SerialCommand_FallThroughToSerialServer_SendReceive <> SerialServer_SendReceive
75 %error "SerialServer_SendReceive must be the first routine at the top of SerialServer.asm in the Assembly_Library"
76 %endif
77%endif
78
79ALIGN JUMP_ALIGN
80SerialCommand_ReturnError:
81 stc
82 ret
83
84;--------------------------------------------------------------------
85; SerialCommand_IdentifyDeviceToBufferInESSIwithDriveSelectByteInBH
86; Parameters:
87; BH: Drive Select byte for Drive and Head Select Register
88; DS: Segment to RAMVARS
89; ES:SI: Ptr to buffer to receive 512-byte IDE Information
90; CS:BP: Ptr to IDEVARS
91; Returns:
92; CF: Cleared if success, Set if error
93; Corrupts registers:
94; AL, BL, CX, DX, SI, DI, ES
95;--------------------------------------------------------------------
96ALIGN JUMP_ALIGN
97SerialCommand_IdentifyDeviceToBufferInESSIwithDriveSelectByteInBH:
98;
99; To improve boot time, we do our best to avoid looking for slave serial drives when we already know the results
100; from the looking for a master. This is particularly true when doing a COM port scan, as we will end up running
101; through all the COM ports and baud rates a second time.
102;
103; But drive detection isn't the only case - we also need to get the right drive when called on int13h/25h.
104;
105; The decision tree:
106;
107; Master:
108; wSerialPortAndBaud Non-Zero: -> Continue with wSerialPortAndBaud (1)
109; wSerialPortAndBaud Zero:
110; previous serial drive not found: -> Scan (2)
111; previous serial drive found: -> Continue with previous serial drive info (3)
112;
113; Slave:
114; wSerialPortAndBaud Non-Zero:
115; previous serial drive not found: -> Error - Not Found (4)
116; previous serial drive found: -> Continue with wSerialPackedAndBaud (5)
117; wSerialPortAndBaud Zero:
118; previous serial drive not found: -> Error - Not Found (4)
119; previous serial drive found: -> Continue with previous serial drive info (6)
120;
121; (1) This was a port/baud that was explicitly set with the configurator. In the drive detection case, as this
122; is the Master, we are checking out a new controller, and so don't care if we already have a serial drive.
123; And as with the int13h/25h case, we just go off and get the needed information using the user's setting.
124; (2) We are using the special .ideVarsSerialAuto structure. During drive detection, we would only be here
125; if we hadn't already seen a serial drive (since we only scan if no explicit drives are set),
126; so we go off to scan.
127; (3) We are using the special .ideVarsSerialAuto structure. We won't get here during drive detection, but
128; we might get here on an int13h/25h call. If we have scanned COM drives, they are the ONLY serial drives
129; in use, and so we use the values from the previously seen serial drive DPT.
130; (4) No master has been found yet, therefore no slave should be found. Avoiding the slave reduces boot time,
131; especially in the full COM port scan case. Note that this is different from the hardware IDE, where we
132; will scan for a slave even if a master is not present. Note that if ANY master had been previously found,
133; we will do the slave scan, which isn't harmful, it just wastes time. But the most common case (by a wide
134; margin) will be just one serial controller.
135; (5) A COM port scan for a master had been previously completed, and a drive was found. In a multiple serial
136; controller scenario being called with int13h/25h, we need to use the value in bSerialPackedPortAndBaud
137; to make sure we get the proper drive.
138; (6) A COM port scan for a master had been previously completed, and a drive was found. We would only get here
139; if no serial drive was explicitly set by the user in the configurator or that drive had not been found.
140; Instead of performing the full COM port scan for the slave, use the port/baud value stored during the
141; master scan.
142;
143 mov dx,[cs:bp+IDEVARS.wSerialPortAndBaud]
144 xor ax,ax
145
146 push si
147 call FindDPT_ToDSDIforSerialDevice
148 pop si
149%ifdef MODULE_SERIAL_FLOPPY
150 jnc .founddpt
151;
152; If not found above with FindDPT_ToDSDIforSerialDevice, DI will point to the DPT after the last hard disk DPT
153; So, if there was a previously found floppy disk, DI will point to that DPT and we use that value for the slave.
154;
155 cmp byte [RAMVARS.xlateVars+XLATEVARS.bFlopCntAndFirst], 0
156 jz .notfounddpt
157.founddpt:
158%else
159 jc .notfounddpt
160%endif
161 mov ax, [di+DPT_SERIAL.wSerialPortAndBaud]
162.notfounddpt:
163
164 test bh, FLG_DRVNHEAD_DRV
165 jz .master
166
167 test ax,ax ; Take care of the case that is different between master and slave.
168 jz SerialCommand_ReturnError
169
170; fall-through
171.master:
172 test dx,dx
173 jnz .identifyDeviceInDX
174
175 xchg dx, ax ; move ax to dx (move previously found serial drive to dx, could be zero)
176
177.identifyDeviceInDX:
178
179ALIGN JUMP_ALIGN
180SerialCommand_FallThroughToSerialServerScan_ScanForServer:
181
182%include "SerialServerScan.asm"
183
184%ifndef CHECK_FOR_UNUSED_ENTRYPOINTS
185 %if SerialCommand_FallThroughToSerialServerScan_ScanForServer <> SerialServerScan_ScanForServer
186 %error "SerialServerScan_ScanForServer must be the first routine at the top of SerialServerScan.asm in the Assembly_Library"
187 %endif
188%endif
189
190
Note: See TracBrowser for help on using the repository browser.