Changeset 294 in xtideuniversalbios for trunk/XTIDE_Universal_BIOS/Inc


Ignore:
Timestamp:
Mar 4, 2012, 1:35:10 AM (12 years ago)
Author:
krille_n_@…
google:author:
krille_n_@hotmail.com
Message:

Commit 2/2 (BIOS):

  • Fixed a bug in AH1h_HStatus.asm.
  • Minor optimizations.
  • Fixed spelling and did some cleaning.
Location:
trunk/XTIDE_Universal_BIOS/Inc
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • trunk/XTIDE_Universal_BIOS/Inc/BootMenu.inc

    r291 r294  
    11; Project name  :   XTIDE Universal BIOS
    22; Description   :   Equates and structs used in Boot Menu.
     3
    34%ifndef BOOTMENU_INC
    45%define BOOTMENU_INC
    … …  
    1920
    2021; Boot Menu Information Table. These are generated for all XTIDE Universal
    21 ; BIOS drives. Available only until boot is successfull.
     22; BIOS drives. Available only until boot is successful.
    2223MAX_HARD_DISK_NAME_LENGTH               EQU     30      ; Bytes reserved for drive name
    2324
    … …  
    3031DPT_BOOTMENUINFO_SIZE_MULTIPLIER  equ   BOOTMENUINFO_size / LARGEST_DPT_SIZE
    3132
    32 %ifndef CHECK_FOR_UNUSED_ENTRYPOINTS               
     33%ifndef CHECK_FOR_UNUSED_ENTRYPOINTS
    3334
    34 %if MAX_HARD_DISK_NAME_LENGTH % 2 <> 0 
    35 %error "MAX_HARD_DISK_NAME_LENGTH needs to be a multiple of 2, memory is moved with word operations."
     35%if MAX_HARD_DISK_NAME_LENGTH % 2 <> 0
     36    %error "MAX_HARD_DISK_NAME_LENGTH needs to be a multiple of 2, memory is moved with word operations."
    3637%endif
    3738
    3839%if BOOTMENUINFO_size % LARGEST_DPT_SIZE <> 0
    39 %error "BOOTMENUINFO's size must be an even multiple of DPT's size.  Add or remove padding at the bottom of BOOTMENUINFO to bring the two sizes into alignment.  As BOOTMENUINFO is only used at boot time, with plenty of memory to consume, it is OK to waste some space here."
     40    %error "BOOTMENUINFO's size must be an even multiple of DPT's size.  Add or remove padding at the bottom of BOOTMENUINFO to bring the two sizes into alignment.  As BOOTMENUINFO is only used at boot time, with plenty of memory to consume, it is OK to waste some space here."
    4041%endif
    4142
    4243%if BOOTMENUINFO.szDrvName <> 0
    43 %error "BOOTMENUINFO.szDrvName is assumed to be the first member of struc BOOTMENUINFO, in BootMenuPrint_RefreshItem"
     44    %error "BOOTMENUINFO.szDrvName is assumed to be the first member of struc BOOTMENUINFO, in BootMenuPrint_RefreshItem"
    4445%endif
    4546

  • trunk/XTIDE_Universal_BIOS/Inc/BootVars.inc

    r254 r294  
    1010
    1111
    12 ; Pre-boot variables. These do not exist after successfull boot to OS.
     12; Pre-boot variables. These do not exist after successful boot to OS.
    1313; Segment is always 0000h, same as BDA segment
    1414struc BOOTVARS
    … …  
    9595    mov     ss, ax
    9696    lss     sp, [ss:BOOTVARS.dwPostStack]
    97 %endif 
     97%endif
    9898%endmacro
    9999

  • trunk/XTIDE_Universal_BIOS/Inc/CustomDPT.inc

    r258 r294  
    3737%ifdef MODULE_SERIAL
    3838; DPT for Serial devices
    39 struc DPT_SERIAL 
     39struc DPT_SERIAL
    4040    .dpt                        resb    DPT_size
    4141
    … …  
    6363FLGH_DPT_INTERRUPT_IN_SERVICE   EQU (1<<3)  ; Set when waiting for IRQ
    6464FLGH_DPT_RESET_nDRDY            EQU (1<<4)  ; Drive ready to accept commands
    65 FLGH_DPT_RESET_nINITPRMS        EQU (1<<5)  ; Initialize Device Parameters successfull
    66 FLGH_DPT_RESET_nRECALIBRATE     EQU (1<<6)  ; Recalibrate successfull
    67 FLGH_DPT_RESET_nSETBLOCK        EQU (1<<7)  ; Initialize Block Mode successfull
     65FLGH_DPT_RESET_nINITPRMS        EQU (1<<5)  ; Initialize Device Parameters successful
     66FLGH_DPT_RESET_nRECALIBRATE     EQU (1<<6)  ; Recalibrate successful
     67FLGH_DPT_RESET_nSETBLOCK        EQU (1<<7)  ; Initialize Block Mode successful
    6868MASKH_DPT_RESET                 EQU 0F0h
    6969

  • trunk/XTIDE_Universal_BIOS/Inc/Int13h.inc

    r218 r294  
    55
    66; Hard Disk function (INT 13h) return status codes in AH
    7 RET_HD_SUCCESS          EQU     0h      ; Operation succesfull, no error occurred
     7RET_HD_SUCCESS          EQU     0h      ; Operation successful, no error occurred
    88RET_HD_INVALID          EQU     1h      ; Invalid value passed or unsupported func
    99RET_HD_ADDRMARK         EQU     2h      ; Missing address mark
Note: See TracChangeset for help on using the changeset viewer.