Timeline



05/07/99:

17:09 Changeset in rtems [5a909149]4.104.114.84.95 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.
16:36 Changeset in rtems [16775a5]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Patch from Jiri Gaisler <jgais@…> to allow stacksize of POSIX Init thread to be user configured.
16:31 Changeset in rtems [07001360]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Added rules to handle alternate suffixes for C++ files.
16:30 Changeset in rtems [acb644a6]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Error reporting fixed by Jennifer.
16:29 Changeset in rtems [c34aaae7]4.104.114.84.95 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.
16:28 Changeset in rtems [b06279d]4.104.114.84.95 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.

04/29/99:

19:08 Changeset in rtems [f779efc]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Added paragraph for Tony Ambardar (tonya@…) submitting a BSP for the TS-1325 embedded PC from Technologic Systems (​http://www.t-systems.com) and patches to enable software floating-point emulation for x86 targets.

04/28/99:

13:59 Changeset in rtems [8846bbd]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Patch from Emmanuel Raguet <raguet@…>: 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.

04/27/99:

17:31 Changeset in rtems [cfcb5a2]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Patch from Eric Norum <eric@…> to corrent a miscount in length that results in an error in parsing network unit names/numbers.

04/26/99:

18:41 Changeset in rtems [9ae3b06]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
changed version to 19990426
18:22 Changeset in rtems [c7aa9d6]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Repairing damage and recovering changes including C++ wrappers..
18:08 Changeset in rtems [3aeaca9]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
changed version to 19990426
18:04 Changeset in rtems [c8cfdcfe]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Recovered changes since CVS file was corrupted.
17:53 Changeset in rtems [05bacd5]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
changed version to 19990426
17:35 Changeset in rtems [8b8204a1]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
changed version to 19990426

04/23/99:

16:49 Changeset in rtems [20b457a1]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Fixed Makefile to avoid copying the file to a new name.
16:42 Changeset in rtems [7a8dfad]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Changed date.
16:40 Changeset in rtems [44d05b2]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
Switched to full doc set.
16:37 Changeset in rtems [0b28bd9c]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
changed version to 19990423
16:35 Changeset in rtems [16a384cf]4.104.114.84.95 by Joel Sherrill <joel.sherrill@…>
New BSP from Tony R. Ambardar <tonya@…> from the University of British Columbia. The BSP is for: Yes, this is the "entry model" of a series of boards from Technologic Systems. Costs <$200 I believe. They have a WWW page at www.t-systems.com. I am letting them know about the availability of this BSP too.
Note: See TracTimeline for information about the timeline view.