Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Corrected so rtems.o is built and installed on all targets. | Joel Sherrill | 1999-05-27 | 10 | -31/+20 |
| | |||||
* | Corrected macro names. | Joel Sherrill | 1999-05-27 | 1 | -2/+6 |
| | |||||
* | Initiated updating this to reflect split up. | Joel Sherrill | 1999-05-26 | 1 | -2/+4 |
| | |||||
* | 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 | 3 | -243/+234 |
| | |||||
* | Patch from Daniel Kelley <dank@icube.com>: | Joel Sherrill | 1999-05-18 | 2 | -8/+8 |
| | | | | | | 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 | 14 | -1695/+949 |
| | |||||
* | 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 | 1 | -4/+4 |
| | |||||
* | Split Interrupt Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 3 | -41/+63 |
| | |||||
* | Split Signal Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 4 | -109/+158 |
| | |||||
* | Dual-Ported Memory Manager split into one routine per file. | Joel Sherrill | 1999-05-17 | 7 | -237/+351 |
| | |||||
* | Split Partition Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 7 | -307/+429 |
| | |||||
* | Split Timer Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 10 | -618/+475 |
| | |||||
* | Split Event Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 7 | -343/+460 |
| | |||||
* | Split Rate Monotonic Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 9 | -417/+573 |
| | |||||
* | Split the Semaphore Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 8 | -485/+771 |
| | |||||
* | Moved some MP routines to semmp.c. | Joel Sherrill | 1999-05-17 | 2 | -55/+54 |
| | |||||
* | Forgot to actually remove the routines. :) | Joel Sherrill | 1999-05-17 | 1 | -748/+0 |
| | |||||
* | Split Message Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 13 | -1/+1112 |
| | |||||
* | Moved an MP routine from msg.c to here. | Joel Sherrill | 1999-05-17 | 1 | -0/+26 |
| | |||||
* | Cleaned up some multiprocessing issues. | Joel Sherrill | 1999-05-17 | 1 | -17/+15 |
| | |||||
* | Split Clock Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 6 | -259/+199 |
| | |||||
* | Split Region Manager into one routine per file. | Joel Sherrill | 1999-05-17 | 9 | -456/+623 |
| | |||||
* | Splitting the Thread Handler forced the inclusion of more prototypes. | Joel Sherrill | 1999-05-17 | 1 | -0/+33 |
| | |||||
* | 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 | 5 | -1/+125 |
| | | | | and RTEMS configuration. | ||||
* | Split Task Manager into multiple files. Eventually this effort will | Joel Sherrill | 1999-05-17 | 16 | -962/+1387 |
| | | | | reduce the size of executables. | ||||
* | Thread Handler split into multiple files. Eventually, as RTEMS is | Joel Sherrill | 1999-05-17 | 26 | -1305/+1990 |
| | | | | 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 | 9 | -12/+12 |
| | | | | warnings. | ||||
* | Patch from D. V. Henkel-Wallace <gumby@zembu.com>: | Joel Sherrill | 1999-05-17 | 1 | -0/+16 |
| | | | | | | 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 testing for C++ exceptions from Rosimildo DaSilva | Joel Sherrill | 1999-05-14 | 1 | -17/+90 |
| | | | | <rdasilva@connecttel.com>. | ||||
* | Added 3COM 3C509 driver from Rosimildo DaSilva <rdasilva@connecttel.com>. | Joel Sherrill | 1999-05-14 | 7 | -2/+2247 |
| | |||||
* | Enabled compilation of rtems_servers at request of Jake Janovetz | Joel Sherrill | 1999-05-14 | 8 | -12/+16 |
| | | | | <janovetz@tempest.ece.uiuc.edu>. | ||||
* | Removed check for initialized ID at request of Rosimildo DaSilva | Joel Sherrill | 1999-05-14 | 1 | -0/+23 |
| | | | | | <rdasilva@connecttel.com> who encountered random failures in his port of omniORB2. | ||||
* | Fix based on bug report from Jay Kulpinski <jskulpin@eng01.gdds.com> | Joel Sherrill | 1999-05-11 | 2 | -2/+22 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | 2 | -9/+9 |
| | | | | 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 | 3 | -3/+10 |
| | | | | of POSIX Init thread to be user configured. | ||||
* | Added rules to handle alternate suffixes for C++ files. | Joel Sherrill | 1999-05-07 | 1 | -0/+9 |
| | |||||
* | Error reporting fixed by Jennifer. | Joel Sherrill | 1999-05-07 | 3 | -45/+45 |
| | |||||
* | 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. | ||||
* | Patch from Emmanuel Raguet <raguet@crf.canon.fr>: | Joel Sherrill | 1999-04-28 | 1 | -1/+3 |
| | | | | | | | | | | I have made test with the Dec21140 driver and it appears that all works fine even if the cache is enabled for the memory space in which the incoming and outcoming Ethernet frames are stored. I have had #ifdef to "comment" the code. If you want to disable cache, you only have to #define the name. It could be mandatory for some BSPs. | ||||
* | Patch from Eric Norum <eric@cls.usask.ca> to corrent a miscount in length | Joel Sherrill | 1999-04-27 | 3 | -3/+3 |
| | | | | that results in an error in parsing network unit names/numbers. | ||||
* | Repairing damage and recovering changes including C++ wrappers.. | Joel Sherrill | 1999-04-26 | 7 | -5/+62 |
| | |||||
* | Recovered changes since CVS file was corrupted. | Joel Sherrill | 1999-04-26 | 1 | -1/+9 |
| | |||||
* | changed version to 19990426 | Joel Sherrill | 1999-04-26 | 1 | -1/+1 |
| | |||||
* | changed version to 19990423 | Joel Sherrill | 1999-04-23 | 1 | -1/+1 |
| |