1. 19 Jan, 2010 1 commit
    • ROOL's avatar
      Incremented version number, no other change. · 63753fc1
      ROOL authored
      Previous changes were untagged, but incrementing the version number gives
      us a tag we can associate with the official RISC OS 5.16 release.
      Version 3.36. Tagged as 'ADFS-3_36'
  2. 15 Jun, 2009 1 commit
    • Ben Avison's avatar
      Build change · d4ba6c08
      Ben Avison authored
        CPU version is no longer specified in the makefile - it's better to inherit
        it from the build environment now that we actually set it appropriately.
        Not tested. Binary should be unchanged - this only affects the warnings
        generated during assembly.
      Version 3.35. Not tagged
  3. 11 Jun, 2009 1 commit
    • Ben Avison's avatar
      GET file pathnames changed · 451a6518
      Ben Avison authored
        Uses suffixed file extensions for compatiblity with both objasm and asasm.
        Supplied by Peter Naulls, tested at ROOL
      Version 3.35. Not tagged
  4. 03 Dec, 2003 1 commit
  5. 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'
  6. 28 Jan, 2003 1 commit
  7. 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'
  8. 18 Sep, 2002 1 commit
  9. 17 Nov, 2000 1 commit
    • Ben Avison's avatar
      Loading to/saving from top-bit-set addresses should now work. · 28968ea5
      Ben Avison authored
        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.
        Tested briefly.
      Version 3.33. Tagged as 'ADFS-3_33'
  10. 11 Jul, 2000 2 commits
    • Kevin Bracey's avatar
      Ursula_RiscPC branch merged. · 83c6bab3
      Kevin Bracey authored
        The Ursula_RiscPC branch contained version 3.30 of ADFS, which had
        minimal updates for Ursula, such as the service call table. This
        version, incorporating changes on the Ursula branch up to
        the Ursula_RiscPC_bp tag, is now merged on to the trunk as 3.32.
        This leaves version 3.31 on the Ursula branch, unmerged. This contains
        unfinished support for auto-detection of IDE drives and support for
        Phoebe hardware.
      Version 3.32. Tagged as 'ADFS-3_32'
    • Kevin Bracey's avatar
      created by srccommit. · eee8692b
      Kevin Bracey authored
  11. 29 Oct, 1998 1 commit
  12. 09 May, 1997 1 commit
  13. 02 May, 1997 1 commit
  14. 01 May, 1997 2 commits
  15. 21 Jan, 1997 1 commit
  16. 06 Jan, 1997 1 commit
  17. 21 Nov, 1996 4 commits
  18. 05 Nov, 1996 3 commits