1. 18 Jul, 2011 1 commit
    • Jeffrey Lee's avatar
      Update IOMD HAL build to use OS_Memory 9 instead of HAL_ControllerAddress for... · fff2a575
      Jeffrey Lee authored
      Update IOMD HAL build to use OS_Memory 9 instead of HAL_ControllerAddress for finding the floppy controller
      
      Detail:
        s/Adfs19 - The (currently disabled) floppy code now uses OS_Memory 9 to look for controller 34 instead of the less-portable (and allocation clashing) HAL_ControllerAddress (to look for controller 6).
      Admin:
        Compiles but untested. IOMD floppy support is broken at the moment anyway.
      
      
      Version 3.39. Tagged as 'ADFS-3_39'
      fff2a575
  2. 22 Jun, 2011 1 commit
    • Jeffrey Lee's avatar
      IOMD/HAL build fixes · 013c01da
      Jeffrey Lee authored
      Detail:
        s/Adfs12 - Don't use DefaultIDEHardware in HAL builds, use the proper addresses instead
        s/Adfs19 - Make floppy code use HAL_ControllerAddress to get 82C710 address in non-PCI, non-Podule, HAL builds. However floppy code is currently disabled in this configuration because it hangs the machine when floppy access is attempted.
        s/Consts, s/StaticsIDE - Get rid of some bad address constants for HAL builds
      Admin:
        Tested in Iyonix & IOMD ROM softloads.
      
      
      Version 3.38. Tagged as 'ADFS-3_38'
      013c01da
  3. 06 Dec, 2010 1 commit
    • Ben Avison's avatar
      Reintroduced support for IOMD machines · a2d689f9
      Ben Avison authored
      Detail:
        There was no "Ver" file for Machine=32, and the code for build switch
        settings appropriate for IOMD had not been kept up-to-date with various
        changes to the module which were made to support Tungsten. This version
        provides working IDE support for IOMD HAL builds, although there are
        still some issues with floppy support. Tungsten builds should be
        functionally identical.
      Admin:
        Tested on a Risc PC. Joint development effort by Tom Walker and Ben Avison.
      
      Version 3.37. Tagged as 'ADFS-3_37'
      a2d689f9
  4. 03 Apr, 2003 1 commit
    • Kevin Bracey's avatar
      * DMA support completed. · 664368e8
      Kevin Bracey authored
      * Selects PIO/DMA/Ultra DMA modes appropriate for each device.
      * DMA support added to ADFS_IDEUserOp, but not yet ADFS_ATAPIOp.
      * WinIDEMaxSectorsPerTransfer increased to 256.
      * Floppy driver reattaches to DMA Manager if it's reinitialised.
      
      Version 3.35. Tagged as 'ADFS-3_35'
      664368e8
  5. 28 Jan, 2003 1 commit
  6. 17 Jan, 2003 1 commit
    • Kevin Bracey's avatar
      * ADFS_DiscOp64 and ADFS_ATAPIOp added. · d980237a
      Kevin Bracey authored
      * New FileCore error passing scheme supported.
      * PCI floppy support functional.
      * 48-bit LBA support added for ADFS_IDEUserOp and accessing beyond the
        first 128GB of a drive - not thoroughly tested.
      * IDE autodetection improved
      
      Version 3.34. Tagged as 'ADFS-3_34'
      d980237a
  7. 18 Sep, 2002 1 commit
  8. 17 Nov, 2000 1 commit
    • Ben Avison's avatar
      Loading to/saving from top-bit-set addresses should now work. · 28968ea5
      Ben Avison authored
      Detail:
        The problem was in the API definition of the scatter lists used in
        background data transfer. These consist of a sequence of word pairs,
        holding addresses and lengths; any negative (ie top-bit-set) address word
        is defined to mean that the list continues at an location that is offset
        by that amount. To get around this, the check is now made not on whether
        the address word is negative, but on whether it is equal to or greater
        than (less negative than) &FFFF0000. This means that accesses to these
        addresses will still fail, but such addresses should be reserved for
        system use anyway.
      Admin:
        Tested briefly.
      
      Version 3.33. Tagged as 'ADFS-3_33'
      28968ea5
  9. 21 Jan, 1997 1 commit
  10. 21 Nov, 1996 1 commit
  11. 05 Nov, 1996 2 commits