Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Initiated updating this to reflect split up. | Joel Sherrill | 1999-05-26 | 2 | -4/+8 |
| | |||||
* | Initial revision | Joel Sherrill | 1999-05-20 | 16 | -0/+4561 |
| | |||||
* | Renamed to rtemstimer.c to avoid conflict with timer drivers in EVERY | Joel Sherrill | 1999-05-20 | 2 | -53/+2 |
| | | | | BSP as we transition to more .o's and less .rel's. | ||||
* | Removed all post 4.0 changes. | Joel Sherrill | 1999-05-20 | 4 | -324/+312 |
| | |||||
* | Patch from Daniel Kelley <dank@icube.com>: | Joel Sherrill | 1999-05-18 | 4 | -16/+16 |
| | | | | | | I found a small buglet in the mips64orion _CPU_ISR_Set_level; the original was wiping out the level argument, and then comparing the current interrupt level with some random value of v0. See patch below. | ||||
* | Regenerated. | Joel Sherrill | 1999-05-18 | 17 | -2100/+1163 |
| | |||||
* | Spacing correction. | Joel Sherrill | 1999-05-18 | 1 | -1/+0 |
| | |||||
* | Reworked to avoid pulling in the jump point entry in EVERY executable. | Joel Sherrill | 1999-05-17 | 11 | -19/+50 |
| | |||||
* | Fixed some typos. | Joel Sherrill | 1999-05-17 | 2 | -8/+8 |
| | |||||
* | Split Interrupt Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 5 | -77/+118 |
| | |||||
* | Split Signal Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 7 | -217/+312 |
| | |||||
* | Dual-Ported Memory Manager split into one routine per file. | Joel Sherrill | 1999-05-17 | 13 | -473/+697 |
| | |||||
* | Split Partition Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 13 | -606/+843 |
| | |||||
* | Split Timer Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 18 | -926/+944 |
| | |||||
* | Split Event Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 13 | -685/+916 |
| | |||||
* | Split Rate Monotonic Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 17 | -833/+1141 |
| | |||||
* | Split the Semaphore Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 15 | -969/+1537 |
| | |||||
* | Moved some MP routines to semmp.c. | Joel Sherrill | 1999-05-17 | 4 | -110/+108 |
| | |||||
* | Forgot to actually remove the routines. :) | Joel Sherrill | 1999-05-17 | 2 | -1496/+0 |
| | |||||
* | Split Message Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 25 | -1/+2217 |
| | |||||
* | Moved an MP routine from msg.c to here. | Joel Sherrill | 1999-05-17 | 2 | -0/+52 |
| | |||||
* | Cleaned up some multiprocessing issues. | Joel Sherrill | 1999-05-17 | 2 | -34/+30 |
| | |||||
* | Split Clock Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 10 | -388/+393 |
| | |||||
* | Split Region Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 17 | -911/+1241 |
| | |||||
* | Splitting the Thread Handler forced the inclusion of more prototypes. | Joel Sherrill | 1999-05-17 | 2 | -0/+66 |
| | |||||
* | Moved _Entry_Table to its own file to avoid having every RTEMS directive | Joel Sherrill | 1999-05-17 | 3 | -95/+107 |
| | | | | pulled in. | ||||
* | Added simple test to find minimum code size of executive with this BSP | Joel Sherrill | 1999-05-17 | 8 | -1/+175 |
| | | | | and RTEMS configuration. | ||||
* | Split Task Manager into multiple files. Eventually this effort will | Joel Sherrill | 1999-05-17 | 31 | -1923/+2768 |
| | | | | reduce the size of executables. | ||||
* | Thread Handler split into multiple files. Eventually, as RTEMS is | Joel Sherrill | 1999-05-17 | 51 | -2609/+3968 |
| | | | | split into one function per file, this will decrease the size of executables. | ||||
* | Patch from D. V. Henkel-Wallace <gumby@zembu.com> to remove compiler | Joel Sherrill | 1999-05-17 | 12 | -16/+16 |
| | | | | warnings. | ||||
* | Patch from D. V. Henkel-Wallace <gumby@zembu.com>: | Joel Sherrill | 1999-05-17 | 2 | -0/+32 |
| | | | | | | Here's a tiny patch that shreds memory returned to the pool (such as by free() and delete). This may help people find some nasty bugs, so here it is. | ||||
* | Added C++ linking rule from Rosimildo DaSilva <rdasilva@connecttel.com>. | Joel Sherrill | 1999-05-14 | 1 | -1/+20 |
| | |||||
* | Added testing for C++ exceptions from Rosimildo DaSilva | Joel Sherrill | 1999-05-14 | 2 | -34/+180 |
| | | | | <rdasilva@connecttel.com>. | ||||
* | Added 3COM 3C509 driver from Rosimildo DaSilva <rdasilva@connecttel.com>. | Joel Sherrill | 1999-05-14 | 7 | -2/+2247 |
| | |||||
* | Regenerated. | Joel Sherrill | 1999-05-14 | 0 | -0/+0 |
| | |||||
* | Regenerated. | Joel Sherrill | 1999-05-14 | 0 | -0/+0 |
| | |||||
* | Enabled compilation of rtems_servers at request of Jake Janovetz | Joel Sherrill | 1999-05-14 | 8 | -12/+16 |
| | | | | <janovetz@tempest.ece.uiuc.edu>. | ||||
* | Fixed typo. | Joel Sherrill | 1999-05-14 | 1 | -1/+1 |
| | |||||
* | Added tool hints. | Joel Sherrill | 1999-05-14 | 3 | -1/+12 |
| | |||||
* | New file. | Joel Sherrill | 1999-05-14 | 1 | -0/+47 |
| | |||||
* | Removed check for initialized ID at request of Rosimildo DaSilva | Joel Sherrill | 1999-05-14 | 2 | -0/+46 |
| | | | | | <rdasilva@connecttel.com> who encountered random failures in his port of omniORB2. | ||||
* | Removed -fomit-frame-pointer from all i386 BSPs since it breaks C++ | Joel Sherrill | 1999-05-14 | 5 | -5/+10 |
| | | | | exceptions and makes debug stack traces impossible. | ||||
* | Fix based on bug report from Jay Kulpinski <jskulpin@eng01.gdds.com> | Joel Sherrill | 1999-05-11 | 3 | -3/+33 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | that the per task reentrancy structure was not being processed properly during exit(). joel@oarcorp.com wrote: > > > This is always an ugly place to poke around. :( > > The code in newlib/libc/stdlib/exit.c walks the atexit chain for the > reentrancy structure for JUST the current task. The code in libc_wrapup() > does it for both the current task and the global reentrancy structure > (which tends to be where driver atexit()'s were registered. > > So I think the _wrapup_reent(0) in libc_wrapup() should be commented out. > > If you concur, then I will make the change and improve the comment on this > line of code to explain things: > > libc_wrapup(); /* Why? XXX */ > > --joel That does the job. cdtest.exe works correctly now. | ||||
* | Patch from Erik Ivanenko <erik.ivanenko@utoronto.ca> to correct 32 bit | Joel Sherrill | 1999-05-11 | 1 | -0/+2 |
| | | | | jmp relative offset from .reset section. | ||||
* | Made all calls to _Thread_Yield_processor consistent in how they are | Joel Sherrill | 1999-05-07 | 4 | -18/+18 |
| | | | | wrapped by calls to _Thread_Enable_dispatch and _Thread_Disable_dispatch. | ||||
* | Patch from Jiri Gaisler <jgais@ws.estec.esa.nl> to allow stacksize | Joel Sherrill | 1999-05-07 | 6 | -6/+20 |
| | | | | of POSIX Init thread to be user configured. | ||||
* | Added rules to handle alternate suffixes for C++ files. | Joel Sherrill | 1999-05-07 | 2 | -0/+18 |
| | |||||
* | Error reporting fixed by Jennifer. | Joel Sherrill | 1999-05-07 | 4 | -60/+60 |
| | |||||
* | Bug fix from Gunter Magin <magin@@skil.camelot.de>: | Joel Sherrill | 1999-05-07 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | in libcpu/powerpc/mpc860/clock/clock.c:InstallClock() the reload value for the PIT is defined as: pit_value = (BSP_Configuration.microseconds_per_tick * Cpu_table.clicks_per_usec) - 1 ; What exactly is a tick, and what is a click? My confusion stems from the fact, that Jay defines clicks_per_usec to 1 which is correct for his configuration, where a 4MHz clock is predivided by 4 and then fed to the PIT. So I assume a "click" is just the period of the PIT input frequency. However, our HW config seems to have 32.768 kHz crystal input for PIT. Mandatory division by 4 means 8.196kHz (122usec) at the PIT. I think, the above assignment should read: pit_value = (BSP_Configuration.microseconds_per_tick / Cpu_table.clicks_per_usec) - 1; where I can define Cpu_table.clicks_per_usec in bspstart.c to 122 (clicks_per_usec). That would lead to a PIT reload value of 10000/122 - 1 = 81 to reach a 10ms "tick" period. | ||||
* | Bug fix from Gunter Magin <magin@skil.camelot.de>: | Joel Sherrill | 1999-05-07 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | in libcpu/powerpc/mpc860/clock/clock.c:InstallClock() the reload value for the PIT is defined as: pit_value = (BSP_Configuration.microseconds_per_tick * Cpu_table.clicks_per_usec) - 1 ; What exactly is a tick, and what is a click? My confusion stems from the fact, that Jay defines clicks_per_usec to 1 which is correct for his configuration, where a 4MHz clock is predivided by 4 and then fed to the PIT. So I assume a "click" is just the period of the PIT input frequency. However, our HW config seems to have 32.768 kHz crystal input for PIT. Mandatory division by 4 means 8.196kHz (122usec) at the PIT. I think, the above assignment should read: pit_value = (BSP_Configuration.microseconds_per_tick / Cpu_table.clicks_per_usec) - 1; where I can define Cpu_table.clicks_per_usec in bspstart.c to 122 (clicks_per_usec). That would lead to a PIT reload value of 10000/122 - 1 = 81 to reach a 10ms "tick" period. |