summaryrefslogtreecommitdiffstats
path: root/c (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Split out the routine rtems_assoc_name_bad().Joel Sherrill1999-05-2710-58/+166
|
* Removed usage of printf.Joel Sherrill1999-05-275-5/+5
|
* Split initialization and reserve resources from termios to reduceJoel Sherrill1999-05-277-119/+188
| | | | size of mininum application.
* Split out polled io, debug puts, and console reserve resources toJoel Sherrill1999-05-274-83/+146
| | | | reduce dependencies and shrink minimum executable size.
* Disabled running size_rtems until all file splitting is finished.Joel Sherrill1999-05-271-1/+1
|
* Regenerated.Joel Sherrill1999-05-2712-947/+1693
|
* Corrected so rtems.o is built and installed on all targets.Joel Sherrill1999-05-2710-31/+20
|
* Corrected macro names.Joel Sherrill1999-05-271-2/+6
|
* Initiated updating this to reflect split up.Joel Sherrill1999-05-261-2/+4
|
* Renamed to rtemstimer.c to avoid conflict with timer drivers in EVERYJoel Sherrill1999-05-202-53/+2
| | | | BSP as we transition to more .o's and less .rel's.
* Removed all post 4.0 changes.Joel Sherrill1999-05-203-243/+234
|
* Patch from Daniel Kelley <dank@icube.com>:Joel Sherrill1999-05-182-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 Sherrill1999-05-1814-1695/+949
|
* Spacing correction.Joel Sherrill1999-05-181-1/+0
|
* Reworked to avoid pulling in the jump point entry in EVERY executable.Joel Sherrill1999-05-1711-19/+50
|
* Fixed some typos.Joel Sherrill1999-05-171-4/+4
|
* Split Interrupt Manager into one routine per file.Joel Sherrill1999-05-173-41/+63
|
* Split Signal Manager into one routine per file.Joel Sherrill1999-05-174-109/+158
|
* Dual-Ported Memory Manager split into one routine per file.Joel Sherrill1999-05-177-237/+351
|
* Split Partition Manager into one routine per file.Joel Sherrill1999-05-177-307/+429
|
* Split Timer Manager into one routine per file.Joel Sherrill1999-05-1710-618/+475
|
* Split Event Manager into one routine per file.Joel Sherrill1999-05-177-343/+460
|
* Split Rate Monotonic Manager into one routine per file.Joel Sherrill1999-05-179-417/+573
|
* Split the Semaphore Manager into one routine per file.Joel Sherrill1999-05-178-485/+771
|
* Moved some MP routines to semmp.c.Joel Sherrill1999-05-172-55/+54
|
* Forgot to actually remove the routines. :)Joel Sherrill1999-05-171-748/+0
|
* Split Message Manager into one routine per file.Joel Sherrill1999-05-1713-1/+1112
|
* Moved an MP routine from msg.c to here.Joel Sherrill1999-05-171-0/+26
|
* Cleaned up some multiprocessing issues.Joel Sherrill1999-05-171-17/+15
|
* Split Clock Manager into one routine per file.Joel Sherrill1999-05-176-259/+199
|
* Split Region Manager into one routine per file.Joel Sherrill1999-05-179-456/+623
|
* Splitting the Thread Handler forced the inclusion of more prototypes.Joel Sherrill1999-05-171-0/+33
|
* Moved _Entry_Table to its own file to avoid having every RTEMS directiveJoel Sherrill1999-05-173-95/+107
| | | | pulled in.
* Added simple test to find minimum code size of executive with this BSPJoel Sherrill1999-05-175-1/+125
| | | | and RTEMS configuration.
* Split Task Manager into multiple files. Eventually this effort willJoel Sherrill1999-05-1716-962/+1387
| | | | reduce the size of executables.
* Thread Handler split into multiple files. Eventually, as RTEMS isJoel Sherrill1999-05-1726-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 compilerJoel Sherrill1999-05-179-12/+12
| | | | warnings.
* Patch from D. V. Henkel-Wallace <gumby@zembu.com>:Joel Sherrill1999-05-171-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 DaSilvaJoel Sherrill1999-05-141-17/+90
| | | | <rdasilva@connecttel.com>.
* Added 3COM 3C509 driver from Rosimildo DaSilva <rdasilva@connecttel.com>.Joel Sherrill1999-05-147-2/+2247
|
* Enabled compilation of rtems_servers at request of Jake JanovetzJoel Sherrill1999-05-148-12/+16
| | | | <janovetz@tempest.ece.uiuc.edu>.
* Removed check for initialized ID at request of Rosimildo DaSilvaJoel Sherrill1999-05-141-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 Sherrill1999-05-112-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 bitJoel Sherrill1999-05-111-0/+2
| | | | jmp relative offset from .reset section.
* Made all calls to _Thread_Yield_processor consistent in how they areJoel Sherrill1999-05-072-9/+9
| | | | wrapped by calls to _Thread_Enable_dispatch and _Thread_Disable_dispatch.
* Patch from Jiri Gaisler <jgais@ws.estec.esa.nl> to allow stacksizeJoel Sherrill1999-05-073-3/+10
| | | | of POSIX Init thread to be user configured.
* Added rules to handle alternate suffixes for C++ files.Joel Sherrill1999-05-071-0/+9
|
* Error reporting fixed by Jennifer.Joel Sherrill1999-05-073-45/+45
|
* Bug fix from Gunter Magin <magin@@skil.camelot.de>:Joel Sherrill1999-05-071-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 Sherrill1999-05-071-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.