1. 14 Mar, 2011 1 commit
  2. 19 Jan, 2010 1 commit
    • ROOL's avatar
      Incremented version number, no other change. · 157c6c53
      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 0.38. Tagged as 'Buffers-0_38'
      157c6c53
  3. 11 Jun, 2009 1 commit
    • Ben Avison's avatar
      GET file pathnames changed · a52f3ee5
      Ben Avison authored
      Detail:
        Uses suffixed file extensions for compatiblity with both objasm and asasm.
      Admin:
        Supplied by Peter Naulls, tested at ROOL
      
      Version 0.37. Not tagged
      a52f3ee5
  4. 16 May, 2003 1 commit
  5. 06 Jun, 2001 1 commit
    • Dan Ellis's avatar
      Bug fix to Buffer_Threshold. · b1314e55
      Dan Ellis authored
      Detail:
        A threshold value of -1 is meant to do a read, it was however also causing
      an UpCall to occur because during 32bit conversion, the PSR was being
      restored before checking for a flag that this was trashing.
      
        This bug affected 26bit builds as well and may have caused the odd
      spurious bufferemptying/filling upcall.
      
      Admin:
        Threshold UpCall no longer occurs when reading threshold. (Tested on RPC).
      cd ~/RiscOS/Sources/HWSupport.
      
      Version 0.36. Tagged as 'Buffers-0_36'
      b1314e55
  6. 16 Mar, 2001 1 commit
  7. 11 Oct, 2000 1 commit
    • Stewart Brodie's avatar
      Fixed some interrupt holes. · cf33544e
      Stewart Brodie authored
      Detail:
        At a couple of points, the Buffer Manager would re-enable interrupts
          when it should not have done so.  These holes are now fixed.  Some
          other code has been optimised in light of extensions made to the
          CPU macros after this component was originally made 32-bit safe.
      Admin:
        Built.
      
      Version 0.34. Tagged as 'Buffers-0_34'
      cf33544e
  8. 24 Mar, 2000 1 commit
    • Kevin Bracey's avatar
      Another attempt to get free buffer space reported correctly. · 7a340dd7
      Kevin Bracey authored
      Detail:
        This has got to win some sort of award. The buffer manager service routine
        (reason code 7) and CnpV were _still_ getting the result wrong.
      
        Buffer_GetInfo (which uses a separate calculation) has been modified to
        ensure it returns the same result for free and used space when word-aligned
        buffers in use.
      
      Version 0.33. Tagged as 'Buffers-0_33'
      7a340dd7
  9. 13 Jan, 2000 1 commit
  10. 10 Dec, 1999 1 commit
    • Stewart Brodie's avatar
      32-bit compatibility. · ba4c0adc
      Stewart Brodie authored
      Admin:
        Phoebe & 32 machine builds tested.  Tested on Risc PC.
        Tested against old and new DeviceFS builds.
      
      Version 0.31. Tagged as 'Buffers-0_31'
      ba4c0adc
  11. 03 Dec, 1999 1 commit
    • Simon Forrest's avatar
      * Fixed the free space call which has been broken since V0.27. · cec64a6b
      Simon Forrest authored
      Detail:
      
        * See summary, above.  Basically the calculation of the free space
          was flawed.  Should now be fixed properly!
      
      Admin:
      
        * Untested, but it's been verified by the BBVA (Bracey Bug-fix Verification
          Association)...
      
      Version 0.30. Tagged as 'Buffers-0_30'
      cec64a6b
  12. 06 Aug, 1999 1 commit
    • Simon Forrest's avatar
      Alterations to fix bugs introduced in V0.27 when the word-aligned buffer support was added. · e9486d1d
      Simon Forrest authored
      Detail:
      
        Added the missing "Buffer must be word aligned" error message to the
        German resources (although the sentence is in English).
      
        Non-internationalised version was missing the "Buffer must be word
        aligned" message; this has now been rectified.
      
        The buffer manager service routine "Return free space" (reason code
        number 7) was incorrectly calculating the free space.  Instead of
        using the size of the buffer and insertion point in the calculation
        it was using an uninitialised register and the reason code!  This
        was due to a change made in V0.27 to the stack environment which
        invalidated the usage of R0 and R1.  Registers R6 and R7 are now
        used in place of these.
      
      Admin:
      
        Tested by softloading on an NC1 using the baseline Lazarus OS image.
        Fixes verified as being correct.
      
      
      Version 0.29. Tagged as 'Buffers-0_29'
      e9486d1d
  13. 05 Aug, 1999 2 commits
  14. 15 Dec, 1998 1 commit
  15. 29 Sep, 1998 2 commits
  16. 09 May, 1997 1 commit
  17. 21 Jan, 1997 1 commit
  18. 21 Nov, 1996 1 commit
  19. 05 Nov, 1996 1 commit