Timeline




matching tags

May 17, 1999:

11:48 PM Changeset in rtems [0995b6f]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Reworked to avoid pulling in the jump point entry in EVERY executable.
11:26 PM Changeset in rtems [9180f63]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Fixed some typos.
11:22 PM Changeset in rtems [c9973bb]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Interrupt Manager into one routine per file.
11:20 PM Changeset in rtems [0123e3b]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Signal Manager into one routine per file.
11:18 PM Changeset in rtems [1dc030f]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Dual-Ported Memory Manager split into one routine per file.
11:15 PM Changeset in rtems [842db5f3]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Partition Manager into one routine per file.
11:10 PM Changeset in rtems [be47df9]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Timer Manager into one routine per file.
11:06 PM Changeset in rtems [cc2bc302]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Event Manager into one routine per file.
11:03 PM Changeset in rtems [5f9b3db]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Rate Monotonic Manager into one routine per file.
10:58 PM Changeset in rtems [c06d8f64]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split the Semaphore Manager into one routine per file.
10:56 PM Changeset in rtems [a2d0f39]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Moved some MP routines to semmp.c.
10:53 PM Changeset in rtems [3270ca6]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Forgot to actually remove the routines. :)
10:52 PM Changeset in rtems [1e1b3e00]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Message Manager into one routine per file.
10:46 PM Changeset in rtems [ef22ab2]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Moved an MP routine from msg.c to here.
10:45 PM Changeset in rtems [86cb89f]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Cleaned up some multiprocessing issues.
10:42 PM Changeset in rtems [bd83f47]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Clock Manager into one routine per file.
10:39 PM Changeset in rtems [5aa64518]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Region Manager into one routine per file.
10:19 PM Changeset in rtems [1178b8c]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Splitting the Thread Handler forced the inclusion of more prototypes.
10:16 PM Changeset in rtems [2f831ac]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Moved _Entry_Table to its own file to avoid having every RTEMS directive pulled in.
10:15 PM Changeset in rtems [d7851582]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added simple test to find minimum code size of executive with this BSP and RTEMS configuration.
9:02 PM Changeset in rtems [c4d69e2]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Split Task Manager into multiple files. Eventually this effort will reduce the size of executables.
8:41 PM Changeset in rtems [05df0a8]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Thread Handler split into multiple files. Eventually, as RTEMS is split into one function per file, this will decrease the size of executables.
3:45 PM Changeset in rtems [a238cc9]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Patch from D. V. Henkel-Wallace <gumby@…> to remove compiler warnings.
3:28 PM Changeset in rtems [577c4080]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Patch from D. V. Henkel-Wallace <gumby@…>: 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.

May 14, 1999:

4:26 PM Changeset in rtems [9e7d42dd]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added C++ linking rule from Rosimildo DaSilva? <rdasilva@…>.
4:25 PM Changeset in rtems [fcf17a4]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added testing for C++ exceptions from Rosimildo DaSilva? <rdasilva@…>.
4:23 PM Changeset in rtems [44dd8a61]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added 3COM 3C509 driver from Rosimildo DaSilva? <rdasilva@…>.
3:58 PM Changeset in rtems [222a71a]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Regenerated.
3:33 PM Changeset in rtems [8e718b67]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Regenerated.
3:31 PM Changeset in rtems [c5881fc]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Enabled compilation of rtems_servers at request of Jake Janovetz <janovetz@…>.
3:21 PM Changeset in rtems [878baa4]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Fixed typo.
3:19 PM Changeset in rtems [cb20294]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added tool hints.
3:15 PM Changeset in rtems [2bd9383]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
New file.
2:43 PM Changeset in rtems [a0b94685]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Removed check for initialized ID at request of Rosimildo DaSilva? <rdasilva@…> who encountered random failures in his port of omniORB2.
2:34 PM Changeset in rtems [123d4b7d]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Removed -fomit-frame-pointer from all i386 BSPs since it breaks C++ exceptions and makes debug stack traces impossible.

May 11, 1999:

4:30 PM Changeset in rtems [4c5080ed]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Fix based on bug report from Jay Kulpinski <jskulpin@…> that the per task reentrancy structure was not being processed properly during exit(). joel@… 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.
3:15 PM Changeset in rtems [ddd22e5]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Patch from Erik Ivanenko <erik.ivanenko@…> to correct 32 bit jmp relative offset from .reset section.

May 7, 1999:

5:09 PM Changeset in rtems [5a909149]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Made all calls to _Thread_Yield_processor consistent in how they are wrapped by calls to _Thread_Enable_dispatch and _Thread_Disable_dispatch.
4:36 PM Changeset in rtems [16775a5]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Patch from Jiri Gaisler <jgais@…> to allow stacksize of POSIX Init thread to be user configured.
4:31 PM Changeset in rtems [07001360]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Added rules to handle alternate suffixes for C++ files.
4:30 PM Changeset in rtems [acb644a6]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Error reporting fixed by Jennifer.
4:29 PM Changeset in rtems [c34aaae7]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Bug fix from Gunter Magin <magin@@skil.camelot.de>: 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.
4:28 PM Changeset in rtems [b06279d]4.104.114.84.9 by Joel Sherrill <joel.sherrill@…>
Bug fix from Gunter Magin <magin@…>: 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.
Note: See TracTimeline for information about the timeline view.