- 20 Nov, 2013 1 commit
-
-
Robert Sprowson authored
The kernel will use RTC_Read and RTC_Write to access the hardware clock, while maintaining the software clock as before. Makefile: header export is now in the RTC module's sources KernelWS: remove RTCFitted flag NewReset: sync the time after the module init i2cutils: deleted clock chip code osinit: move OS_ResyncTime into PMF/realtime realtime: mostly packages up ordinals and calls the respective SWI Tested on IOMD softload. Version 5.35, 4.79.2.202. Tagged as 'Kernel-5_35-4_79_2_202'
-
- 27 Jan, 2013 1 commit
-
-
Robert Sprowson authored
SystemName, ROMSizeOffset, HAL32, HAL26 only used here, moved here. Remove uses of "M_" booleans, apparently that's bad form. Fix SWIDespatch_Size for the non thumb capable case (was ASSERTing). Swapped UserMemStart for AppSpaceStart. Removed last use of OldComboSupport (pre Medusa!). Removed switch 'CDVPoduleIRQs', a correction to the machine definitions mean this can now simply be switched on NumberOfPodules (previously, IOMD couldn't chain podule interrupts). Take out disabled sub interrupt support - it's in CVS if you want to try to get it working. Moved ConfiguredLang to 11 for everyone, it only matters if !Boot fails, and no harm in making it common for 5.xx onwards. Version 5.35, 4.79.2.183. Tagged as 'Kernel-5_35-4_79_2_183'
-
- 10 Jan, 2013 1 commit
-
-
Robert Sprowson authored
Permits applications to query what value would be used in the event of a CMOS reset for a given configure value. Notably, the configure plugins will use this in favour of 'ResetCMOS'. hdr/Options: retire the 'Select16BitSound' switch, add comment for ChecksumCMOS switch hdr/KernelWS: DuffEntry and Nowhere moved here Kernel.s: Unused OSMD removed, retire single use of SPIRQ in favour of r13_irq Middle.s: Retire SPIRQ NewReset.s: Trim out 300+ lines of CMOS reset defaults, call OS_NVMemory 6 instead PMF/i2cutils.s: CMOS reset default code and table moved here with refactoring Note, the previous code preserved YearCMOS during the zeroing, only to unconditionally write it later - so have removed it from the zeroing step. Note, the locations 80-111 are now considered as system CMOS in the allocations hence are now wiped too (previously they got skipped as user CMOS during R-power-on). Tested on OMAP3 ROM with delete-power-on and R-power-on variants, and a simple BASIC program to read locations 0-255 via OS_NVMemory. Version 5.35, 4.79.2.180. Tagged as 'Kernel-5_35-4_79_2_180'
-
- 27 Nov, 2011 1 commit
-
-
Robert Sprowson authored
Expand tabs. Swap DCI for instructions now Objasm 4 is out. Symbols for FSControl_CAT/RUN/OPT changed to non Arthur definitions. Still boots on IOMD class, no other testing. Version 5.35, 4.79.2.124. Tagged as 'Kernel-5_35-4_79_2_124'
-
- 08 Aug, 2011 1 commit
-
-
Jeffrey Lee authored
Detail: A whole mass of changes to add high processor vectors + zero page relocation support to the Cortex branch of the kernel At the moment the code can only cope with two ZeroPage locations, &0 and &FFFF0000. But with a bit more tweaking those restrictions can probably be lifted, allowing ZeroPage to be hidden at almost any address (assuming it's fixed at compile time). If I've done my job right, these restrictions should all be enforced by asserts. There's a new option, HiProcVecs, in hdr/Options to control whether high processor vectors are used. When enabling it and building a ROM, remember: * FPEmulator needs to be built with the FPEAnchor=High option specified in the components file (not FPEAnchorType=High as my FPEmulator commit comments suggested) * ShareFS needs unplugging/removing since it can't cope with it yet * Iyonix users will need to use the latest ROOL boot sequence, to ensure the softloaded modules are compatible (OMAP, etc. don't really softload much so they're OK with older sequences) * However VProtect also needs patching to fix a nasty bug there - http://www.riscosopen.org/tracker/tickets/294 The only other notable thing I can think of is that the ProcessTransfer code in s/ARM600 & s/VMSAv6 is disabled if high processor vectors are in use (it's fairly safe to say that code is obsolete in HAL builds anyway?) Fun challenge for my successor: Try setting ZeroPage to &FFFF00FF (or similar) so its value can be loaded with MVN instead of LDR. Then use positive/negative address offsets to access the contents. File changes: - hdr/ARMops - Modified ARMop macro to take the ZeroPage pointer as a parameter instead of 'zero' - hdr/Copro15ops - Corrected $quick handling in myISB macro - hdr/Options - Added ideal setting for us to use for HiProcVecs - s/AMBControl/allocate, s/AMBControl/growp, s/AMBControl/mapslot, s/AMBControl/memmap, s/AMBControl/service, s/AMBControl/shrinkp, s/Arthur2, s/Arthur3, s/ArthurSWIs, s/ChangeDyn, s/ExtraSWIs, s/HAL, s/HeapMan, s/Kernel, s/MemInfo, s/Middle, s/ModHand, s/MoreSWIs, s/MsgCode, s/NewIRQs, s/NewReset, s/Oscli, s/PMF/buffer, s/PMF/IIC, s/PMF/i2cutils, s/PMF/key, s/PMF/mouse, s/PMF/osbyte, s/PMF/oseven, s/PMF/osinit, s/PMF/osword, s/PMF/oswrch, s/SWINaming, s/Super1, s/SysComms, s/TickEvents, s/Utility, s/vdu/vdu23, s/vdu/vdudriver, s/vdu/vdugrafl, s/vdu/vdugrafv, s/vdu/vdupalxx, s/vdu/vdupointer, s/vdu/vduswis, s/vdu/vduwrch - Lots of updates to deal with zero page relocation - s/ARM600 - UseProcessTransfer option. Zero page relocation support. Deleted pre-HAL ClearPhysRAM code to tidy the file up a bit. - s/ARMops - Zero page relocation support. Set CPUFlag_HiProcVecs when high vectors are in use. - s/KbdResPC - Disable compilation of dead code - s/VMSAv6 - UseProcessTransfer option. Zero page relocation support. Admin: Tested with OMAP & Iyonix ROM softloads, both with high & low zero page. High zero page hasn't had extensive testing, but boot sequence + ROM apps seem to work. Version 5.35, 4.79.2.98.2.48. Tagged as 'Kernel-5_35-4_79_2_98_2_48'
-
- 20 Feb, 2010 2 commits
-
-
Jeffrey Lee authored
Detail: s/PMF/i2cutils - Although the code will detect the Philips RTC correctly, it was failing to set the device size in R4, causing CMOS RAM to be misread. This change fixes that. Admin: Not tested; however it's identical to the fix applied to the HAL branch Version 5.35, 4.79.2.98.2.23. Tagged as 'Kernel-5_35-4_79_2_98_2_23'
-
Jeffrey Lee authored
Detail: s/PMF/i2cutils - Although the code will detect the Philips RTC correctly, it was failing to set the device size in R4, causing CMOS RAM to be misread. This change fixes that. Admin: Tested in IOMD HAL build on development version of RPCEmu. Version 5.35, 4.79.2.110. Tagged as 'Kernel-5_35-4_79_2_110'
-
- 02 Feb, 2010 2 commits
-
-
Jeffrey Lee authored
Fix bug in InitCMOSCache that could cause CMOS to be erroneously reset if NVRAM is of type 'MaybeIIC' (Cortex branch) Detail: s/PMF/i2cutils - Kernel was checking if the full IIC flags word was equal to MaybeIIC instead of just checking if the Provision bits equalled MaybeIIC. Thus if any of the additional flags were set along with MaybeIIC the kernel would have skipped the probing code, skipped the IIC code, and then fallen through to using the (likely unimplemented) HAL interface for initialising the NVRAM cache. Admin: Fix tested in HAL branch in IOMD build under RPCemu; kernel now takes the correct path for MaybeIIC + ProtectAtEnd. Version 5.35, 4.79.2.98.2.22. Tagged as 'Kernel-5_35-4_79_2_98_2_22'
-
Jeffrey Lee authored
Fix bug in InitCMOSCache that could cause CMOS to be errouneously reset if NVRAM is of type 'MaybeIIC' Detail: s/PMF/i2cutils - Kernel was checking if the full IIC flags word was equal to MaybeIIC instead of just checking if the Provision bits equalled MaybeIIC. Thus if any of the additional flags were set along with MaybeIIC the kernel would have skipped the probing code, skipped the IIC code, and fallen through to using the (likely unimplemented) HAL interface for initialising the NVRAM cache. Admin: Tested in IOMD build under RPCemu; kernel now takes the correct path for MaybeIIC + ProtectAtEnd. Version 5.35, 4.79.2.109. Tagged as 'Kernel-5_35-4_79_2_109'
-
- 24 Jan, 2010 1 commit
-
-
Jeffrey Lee authored
Detail: s/PMF/osword - Migrate the 2012 RTC fix from the HAL branch to the Cortex branch, plus apply similar fix to the code that handles HAL RTC devices (via new YearLOIsGood flag) s/PMF/i2cutils - Update HAL RTC year handling to correctly treat YearLO as either 2-bit int or 2-digit BCD hdr/RTCDevice - Add YearLOIsGood flag, revise NeedsYearHelp description Admin: Tested on rev C2 beagleboard. Code seems to behave as intended. Version 5.35, 4.79.2.98.2.21. Tagged as 'Kernel-5_35-4_79_2_98_2_21'
-
- 30 Sep, 2009 1 commit
-
-
Jeffrey Lee authored
Detail: The kernel will now attempt to cope with errors returned by HAL RTC devices - For RTC read operations, instead of just loading random garbage, the bad result will now be ignored and the soft 5-byte time left unaltered. Admin: Tested on rev C2 beagleboard. Year now correctly defaults to 1970 instead of 1900 if the OMAP3 RTC driver returns an error because the RTC isn't running yet. Version 5.35, 4.79.2.98.2.13. Tagged as 'Kernel-5_35-4_79_2_98_2_13'
-
- 23 Jul, 2009 1 commit
-
-
Jeffrey Lee authored
Detail: HAL kernels (on the Cortex branch at least) now support HALDevice-based RTCs. If the kernels own RTC code is disabled or fails to detect an RTC, then after HAL_InitDevices is called the HALDevice list will be scanned for any HAL-resident RTC devices. Additionally, the RTCSupport flag (in Hdr:Machine.Machine), which was previously TRUE for all HAL kernels, can now be set to FALSE in HAL kernels to disable the kernels own IIC RTC code. This allows the unwanted legacy RTC code to be disabled for machines which are known to use HAL RTCs instead. hdr/RTCDevice - new header describing data structures used for HAL RTC device hdr/HALDevice - added RTCDevice device type, IIC serial bus type hdr/KernelWS - upgraded RTCFitted from a 1 byte field to 4 byte. It now stores either a null value (for no RTC), a value <2048 for an IIC RTC address, or a value >= 2048 for a RTCDevice ptr Makefile - added header export of hdr/RTCDevice s/GetAll - include hdr/RTCDevice s/NewReset - initialise HAL RTC after HAL_InitDevices if required s/PMF/i2cutils, s/PMF/osinit, s/PMF/osword - modifications to allow use of HAL RTC (and disallow use of builtin IIC RTC) Admin: Tested on rev C2 beagleboard Version 5.35, 4.79.2.98.2.11. Tagged as 'Kernel-5_35-4_79_2_98_2_11'
-
- 15 Jun, 2009 1 commit
-
-
Ben Avison authored
Detail: s.PMF.i2cutils line 454: this LDR of byte values was harmless (bits 8 upwards are discarded later) but slower than an LDRB on ARMv6 or later. s.PMF.i2cutils line 556: should have loaded RTCFitted using LDRB. Looks like effect would have been to reduce utilisation of CMOS cache. s.vdu.vduswis line 1500: mistakenly accessing ExternalFramestore using LDR. I don't think the intention was to prevent the screen DA being resized while screen memory was claimed, but that was the effect. s.vdu.vduwrch line 3106: this LDR of a 1-byte variable was harmless (only used for testing bit 4) but slower than an LDRB on ARMv6 or later. 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. Admin: Built and briefly tested. Version 5.35, 4.79.2.98.2.9. Tagged as 'Kernel-5_35-4_79_2_98_2_9'
-
- 22 Dec, 2008 1 commit
-
-
Ben Avison authored
Detail: * Added some documentation on previously undocumented HAL calls * Corrected NVMemoryFlag_Provision bitmask to match documentation * Bugfix: NVMemoryFlag_ProtectAtEnd flag was being ignored Admin: Not tested Version 5.35, 4.79.2.98. Tagged as 'Kernel-5_35-4_79_2_98'
-
- 21 Mar, 2005 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.84. Tagged as 'Kernel-5_35-4_79_2_84'
-
- 08 Sep, 2004 1 commit
-
-
John Ballance authored
Tungsten HAL IIC_Transfer not initialising the checksum Detail: Admin: tested at castle.. again! castle added IP Version 5.35, 4.79.2.75. Tagged as 'Kernel-5_35-4_79_2_75'
-
- 06 Sep, 2004 1 commit
-
-
John Ballance authored
Detail: CheckSumBlock called IIC_OpV to checksum byte 0 of CMOS, but read back the resultant checksum from the wrong offset (#20.. new R1 value).. now corrected to #24 as the correct offset (approx line 997). Admin: tested at castle in iyonix castle added IP Version 5.35, 4.79.2.74. Tagged as 'Kernel-5_35-4_79_2_74'
-
- 25 Jun, 2004 1 commit
-
-
Kevin Bracey authored
* Added use of CDVPoduleIRQs (from Hdr:Machine) * Fixed checksum corruption in OS_NVMemory block writes ending just below the checksum byte. * Fixed R4 corruption by OS_Byte 162 with certain HALs. Version 5.35, 4.79.2.71. Tagged as 'Kernel-5_35-4_79_2_71'
-
- 30 Nov, 2002 1 commit
-
-
Ben Avison authored
Detail: Lots of changes since last version, at least the following: * Updated OS timestamp, removed alpha status * Negative INKEY OS version changed to &AA * GraphicsV is now alocated vector number &2A * ROM moved up to &FC000000 * Max application slot increased to 512 Mbytes (for now) * Max size of RMA increased to 256 Mbytes * RMA is now first-created dynamic area (so it gets lowest address after top of application slot) * OS_Memory 10 reimplemeted * New OS_ReadSysInfo 6 values 18-22 added * OS_ReadSysInfo 8 gains flag bit to indicate soft power-off * Misc internal top-bit-set-address fixes * *ChangeDynamicArea can take sizes in megabytes or gigabytes * Magic word "&off" in R0 passed to OS_Reset powers down if possible * Added acceleration: block copy; CLS; text window scroll up; rectangle fill * Disabled LED flashing in page mode (liable to crash) * Masked sprite plot and VDU 5 text avoids reading the screen if possible * Framestore made USR mode accessible * Fix for VDU 5,127 bug - now relies on font definitions being in extreme quarters of memory, rather than bottom half * Allocated 64-bit OS_Convert... SWIs * IIC errors use allocated error numbers * Looks for Dallas RTC before Philips RTC because we're using a Philips NVRAM device with the same ID * Fix to bug that meant the oscillator in the Dallas RTC wasn't enabled * Default mouse type (USB) changed to allocated number * Ram disc max size increased to 128 Mbytes (Ursula merge) and made cacheable for StrongARMs (not XScale) * Branch through zero handler now works in USR mode, by use of a trampoline in the system stack to allow PC-relative register storage * Address exception handler changed to not use 0 as workspace * OS_Memory 13 extended to allow specification of cacheability and access privileges * Added OS_Memory 16 to return important memory addresses * RISCOS_MapInIO() takes cacheable flag in bit 3, access permissions in bits 10 and 11, doubly-mapped flag in bit 20, and access permissions specified flag in bit 21 * Bug fix in last version for application abort handlers didn't quite work; register shuffle required * "Module is not 32-bit compatible" error now reports the module name * Default configured language changed from 10 to 11 (now Desktop again) Version 5.35, 4.79.2.51. Tagged as 'Kernel-5_35-4_79_2_51'
-
- 07 Oct, 2002 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.48. Tagged as 'Kernel-5_35-4_79_2_48'
-
- 17 May, 2001 1 commit
-
-
Kevin Bracey authored
* Kernel puts sensible default FIQ handler in through the HAL. * Fix to temporary page uncaching code. Version 5.35, 4.79.2.30. Tagged as 'Kernel-5_35-4_79_2_30'
-
- 11 Apr, 2001 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.26. Tagged as 'Kernel-5_35-4_79_2_26'
-
- 19 Mar, 2001 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.21. Tagged as 'Kernel-5_35-4_79_2_21'
-
- 16 Mar, 2001 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.20. Tagged as 'Kernel-5_35-4_79_2_20'
-
- 07 Mar, 2001 1 commit
-
-
Kevin Bracey authored
-
- 09 Oct, 2000 1 commit
-
-
Kevin Bracey authored
-
- 06 Oct, 2000 1 commit
-
-
Kevin Bracey authored
It says "Abort on data transfer".
-
- 05 Oct, 2000 1 commit
-
-
Dan Ellis authored
Detail: Added the HAL NVRAM entries. Modified i2cutils to use the HAL entries for NVRAM and behave sensibly if the HAL reports that there is no NVRAM, in which case there must be a forced reset_cmos call so that the cache gets set up sensibly. Admin: Tested under the RPC emulator and appears to be working correctly, although some calls to IIC are still being made in the no nvram case. Version 5.35, 4.79.2.8. Tagged as 'Kernel-5_35-4_79_2_8'
-
- 03 Oct, 2000 1 commit
-
-
Mike Stephens authored
partial video changes for kernel/HAL split near-HAL code for VIDC/IOMD in vdu.vduhint briefly tested in Ursula desktop build still some kernel workspace dependency in near-HAL code Version 5.35, 4.79.2.3. Tagged as 'Kernel-5_35-4_79_2_3'
-
- 02 Oct, 2000 1 commit
-
-
Kevin Bracey authored
Version 5.35, 4.79.2.2. Tagged as 'Kernel-5_35-4_79_2_2'
-
- 15 Sep, 2000 1 commit
-
-
Kevin Bracey authored
* Added ARM_IMB and ARM_IMBRange SWIs as recommended by ARMv5. * Some early prototype HAL bits popped in - a lot of source restructuring still to come. * New debug target creates an AIF image with debug information, and translates this into an ASCII object file for the 16702B logic analyser. Version 5.35, 4.79.2.1. Tagged as 'Kernel-5_35-4_79_2_1'
-
- 08 Sep, 2000 1 commit
-
-
Robert Catherall authored
[ E2ROMSupport ..... ] Detail: Changes to s.Middle (SysReadInfo routine that used #NVRamSpeed) and s.PMF.i2cutils #NVRamSpeed again Admin: Compiles okay Requires HdrSrc-0_99 or greater (for MaxI2Cspeed variable) Version 5.35. Tagged as 'Kernel-5_35'
-
- 04 Sep, 2000 1 commit
-
-
Robert Catherall authored
New routine in i2cutils that allows access to protected sections such as MAC address OS_ReadSysInfo 4 now checks both copies MACAddress if MACNVRAM2copies is set Detail: 32K EEPROM has to be configured with IIC address &A6 (i.e wired up on the pcb) ClockNVMemoryFast has been replaced with MaxI2Cspeed so that several different rates can be used depending on the devices on the IIC bus. Admin: Need to implement routine that can use one copy of the MAC address to replace the other in the event of it being corrupted. Version 5.33. Tagged as 'Kernel-5_33'
-
- 04 Apr, 2000 1 commit
-
-
Kevin Bracey authored
Details: The Kernel will now compile to produce a pure 32-bit system if No26bitCode is set to TRUE. If No26bitCode is FALSE, then the Kernel will be a standard 26-bit Kernel, although some internal changes have taken place to minimise compile switches between the two cases. See Docs.32bit for more technical info. The hardest part was the flood-fill... Other changes: Pointer shape changes now take place on the next VSync, rather than actually WAITING for the VSync. Turning the Hourglass on shouldn't slow your machine down by 5% now :) Lots of really crusty pre-IOMD code removed. Admin: Tested in 32 and 26-bit forms in a limited desktop build. Basically, this will need to see a lot of use to iron out difficulties. I'd like anyone who has a non-frozen project to at least attempt using this Kernel. Version 5.23. Tagged as 'Kernel-5_23'
-
- 27 Jan, 2000 1 commit
-
-
Stewart Brodie authored
Detail: If E2ROMSupport is {FALSE} then the kernel fails to build due to the use a symbols that are only defined if E2ROMSupport is {TRUE}. This is now fixed by stopping the symbols being used where they should not be (NVRAM and RTC related symbols). Admin: Built. Version 5.14. Tagged as 'Kernel-5_14'
-
- 26 Jan, 2000 1 commit
-
-
Kevin Bracey authored
Kernel now always assumes that 4K and 8K ATMEL EEPROM devices have their top quarter write protected, even if IOMD_C_EEPROMProtect isn't set. Version 5.10. Tagged as 'Kernel-5_10'
-
- 29 Sep, 1999 1 commit
-
-
Kevin Bracey authored
* Wasn't allowing writes to most of EEPROM. * Old prototype OS_SetTime SWI code removed. * MPEGPoduleNTSCNotPALMask option support removed to simplify things a bit. * Now can cope with a system with a PAL/NTSC link, but no monitor detect line. * Default PAL & NTSC modes now always 12 & 46 respectively. * Kernel now knows about monitor type 8 (NTSC) - modes 44-46 (640x200) are available. * STB/NC CMOS test removed from POST pending further investigation. Version 4.90. Tagged as 'Kernel-4_90'
-
- 23 Sep, 1999 1 commit
-
-
Kevin Bracey authored
Added support for ATMEL 4K and 8K EEPROM parts, including write protection of top quarter. Untested. Added support for ARM7500FE IO clock divide by 2. Version 4.89. Tagged as 'Kernel-4_89'
-
- 03 Aug, 1999 1 commit
-
-
Kevin Bracey authored
* Integrated Ursula fast service call dispatch code. * Added Interruptible32bitModes from Ursula. * Stopped allowing ROM modules (other than the Kernel/UtilityModule) to write to the hardware vectors in 26-bit mode. Version 4.81. Tagged as 'Kernel-4_81'
-
- 30 Sep, 1998 1 commit
-
-
Kevin Bracey authored
Bandwidth limit for 7500FE fixed. RO371Timings flag set to :LNOT:STB Version 4.64. Tagged as 'Kernel-4_64'
-