summaryrefslogtreecommitdiffstats
path: root/c (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Wrong BSP referenced.Joel Sherrill2000-01-232-2/+2
|
* Removing unused file accidentally left in CVS. Discovered byJoel Sherrill2000-01-233-269/+0
| | | | Ralf Corsepius <corsepiu@faw.uni-ulm.de>.
* Patch from Eric Norum <eric@cls.usask.ca> at the request of JakeJoel Sherrill2000-01-212-66/+112
| | | | | | | Janovetz <janovetz@tempest.ece.uiuc.edu> to return a status from network initialization rather than panic'ing. It changes a bunch of rtems_panics to printfs and returns a status from rtems_bsdnet_initialize_network().
* Patch from Eric Norum <eric@cls.usask.ca> to implement this:Joel Sherrill2000-01-216-21/+25
| | | | | | | | | | | | | | | | | | | | I'd like to propose a change to RTEMS task variables that I think would make them more useful. I think that it is early enough in their existence to still make changes to their API. 1) Change type from `int' to `void *'. 2) Add extra argument to task_variable_add -- if non-NULL, a pointer to a `destructor' function to be called when the task exits. This function would be called with that task's value of the task variable as its argument. In many cases, the `dtor' function could be `free'. rtems_status_code rtems_task_variable_add ( rtems_id tid, void **ptr, void (*dtor)(void *)); rtems_status_code rtems_task_variable_delete (rtems_id tid, void **ptr); This would be all we'd need to cleanly and efficiently support C++ per-thread exception information without dragging in all that POSIX API stuff.
* Patch from Eric Norum <eric@cls.usask.ca> to remove warnings.Joel Sherrill2000-01-212-8/+6
|
* Patch from Eric Norum <eric@cls.usask.ca>:Joel Sherrill2000-01-211-28/+16
| | | | | | | | Some excellent sleuthing by Bob Wisdom <bobwis@ascweb.co.uk> revealed that an empty mbuf at the end of a packet chain would cause the `retire' function to blow up. Moving the line of code which bumps the transmit buffer descriptor pointer fixes the problem. Some additional cleanup of the sendpacket function was also completed.
* Updated to reflect final test output.Joel Sherrill2000-01-141-3/+15
|
* Updated screen to reflect final test output.Joel Sherrill2000-01-141-24/+114
|
* Added -U__STRICT_ANSI__ to remove MANY warnings since the BSD codeJoel Sherrill2000-01-141-1/+1
| | | | is not strict ANSI.
* Removed unused variable warning.Joel Sherrill2000-01-142-2/+0
|
* Removed no prototype of kill() warning.Joel Sherrill2000-01-141-0/+2
|
* Now ignores minimum and does not run it.Joel Sherrill2000-01-142-2/+2
|
* Now using Makefile.am to generate this file.Joel Sherrill2000-01-141-279/+0
|
* Warning corrections per feedback from Emmanuel Raguet <raguet@crf.canon.fr>.Joel Sherrill2000-01-141-1/+1
|
* Removed warning.Joel Sherrill2000-01-142-2/+4
|
* Removed numerous warnings.Joel Sherrill2000-01-147-8/+16
|
* Updated files missed in earlier batch from Eric Norum.Joel Sherrill2000-01-132-26/+18
|
* Fixed warnings.Joel Sherrill2000-01-131-14/+0
|
* Patch rtems-rc-20000104-17.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-01-1314-100/+4986
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that addresses the librdbg/rpcgen related problems: Changes: * All rpcgen generated files are now kept inside of the source tree * Fix librdbg/configure to correctly detect presence of rpcgen and awk * Use rpcgen -m to generated remdeb_svc.c * Remove msgout/_msgout from awk.svc * minor cleanups to librdbg/configure.in ATTENTION --- IMPORTANT: * With keeping rpc-generated files pre-build inside of the source tree, you as the packager of RTEMS have to ensure that timestamps are correctly set up: The generated files must not be older than the *.x files. * This is extraordinarily important when - putting the package on read-only media - after checking out from CVS - after modifications to the *.x files * If one of the *.x files is modified you have to either - build for i386/pc386 and powerpc/mcp750 - or to invoke the same rpcgen calls as the librdbg/src/<cpu>/<bsp>/Makefile.am do manually before checking-in the files to CVS. Proposal: We could add something to bootstrap for touching the rpcgen-generated sources and/or to manually regenerate them. NOTE FROM JOEL: Ralf proposed modifying bootstrap to handle rpcgen. I think this is the best solution as it is something already done in the snapshot procedure.
* All m68k BSPs now build with new ELF style linkcmds.Joel Sherrill2000-01-1346-681/+192
|
* POSIX message queues now include complete functionality includingJoel Sherrill2000-01-131-2/+22
| | | | | | | | | | | | | | | | blocking sends when the queue is full. The SuperCore was enhanced to support blocking on send. The existing POSIX API was debugged and numerous test cases were added to psxmsgq01 by Jennifer Averett. SuperCore enhancements and resulting modifications to other APIs were done by Joel. There is one significant point of interpretation for the POSIX API. What happens to threads already blocked on a message queue when the mode of that same message queue is changed from blocking to non-blocking? We decided to unblock all waiting tasks with an EAGAIN error just as if a non-blocking version of the same operation had returned unsatisfied. This case is not discussed in the POSIX standard and other implementations may have chosen differently.
* Added test case for broadcast to queue with messages pending.Joel Sherrill2000-01-132-0/+14
|
* Changed error checking macros for POSIX.Joel Sherrill2000-01-132-50/+110
|
* POSIX message queues now include complete functionality includingJoel Sherrill2000-01-1314-387/+1278
| | | | | | | | | | | | | | | | blocking sends when the queue is full. The SuperCore was enhanced to support blocking on send. The existing POSIX API was debugged and numerous test cases were added to psxmsgq01 by Jennifer Averett. SuperCore enhancements and resulting modifications to other APIs were done by Joel. There is one significant point of interpretation for the POSIX API. What happens to threads already blocked on a message queue when the mode of that same message queue is changed from blocking to non-blocking? We decided to unblock all waiting tasks with an EAGAIN error just as if a non-blocking version of the same operation had returned unsatisfied. This case is not discussed in the POSIX standard and other implementations may have chosen differently.
* Missed removing this file in an earlier commit. This is removedJoel Sherrill2000-01-131-70/+0
| | | | because of the conversion to automake and replaced by a Makefile.am.
* + Added commentsJennifer Averett2000-01-133-8/+46
|
* + Added and yellow line tested _CORE_message_queue_Flush_waiting_threadsJennifer Averett2000-01-133-1/+174
| | | | | and _CORE_message_queue_Insert_message for posix message queues. + Yellow line tested new source
* Added comment.Jennifer Averett2000-01-131-0/+1
|
* + Comment cleanupJennifer Averett2000-01-134-15/+12
|
* Removed referance to rtems error.Jennifer Averett2000-01-131-1/+2
| | | | Added correct include file.
* Added comment to indicate this path does not occur.Jennifer Averett2000-01-131-1/+2
|
* Added start and end herald.Jennifer Averett2000-01-132-2/+6
|
* Made sweep of changes to get all BSPs to the same point on the linkcmdsJoel Sherrill2000-01-1322-39/+102
| | | | and memory layout. Next step is to share the same bsp_pretasking_hook.
* New patch from Eric Norum plus some minor mods by Joel.Joel Sherrill2000-01-138-361/+310
|
* Fixed spacing.Joel Sherrill2000-01-131-2/+2
|
* Made _clear_end a "PROVIDE."Joel Sherrill2000-01-131-1/+1
|
* + Added code for waiting sendJennifer Averett2000-01-121-4/+39
| | | | + Yellow lined tested routine with Posix message queue test (01)
* Debugged and yellow line tested routines.Jennifer Averett2000-01-123-41/+71
|
* + Modified return codesJennifer Averett2000-01-121-16/+27
| | | | | + Added messsage size check + Debugged and yellowed out routine
* + Added signal processing.Jennifer Averett2000-01-121-1/+3
| | | | + Yellow line tested source.
* + Modified to correct return codes.Jennifer Averett2000-01-121-2/+5
| | | | | + Removed extra flag attribute from message queue structure. + Yellow-lined all posix message queue routines.
* + Changed call from core flush to core close routine. This flushes waitingJennifer Averett2000-01-121-2/+4
| | | | queues as well as the messages.
* + Removed name validation code (this was already done in nametoid.Jennifer Averett2000-01-121-41/+6
|
* Patch rtems-rc-20000104-16.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-01-122-41/+288
| | | | that converts the libbsp/i386 subdirectory to full automake.
* Eric Norum <eric@cls.usask.ca> submitted linker script and bsp_specsJoel Sherrill2000-01-1226-761/+1420
| | | | | | | | for the gen68360 that let it work with ELF and C++ exceptions. This was used as the basis for changes to EVERY m68k bsp_specs and linkcmds. Before this modification is over, the layout of the starting stack, heap, and workspace will likely be modified for every m68k BSP. Then they will all be very similar.
* Patch rtems-rc-20000104-16.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-01-1276-1787/+1142
| | | | that converts the libbsp/i386 subdirectory to full automake.
* Patch rtems-rc-20000104-15.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-01-127-10/+14
| | | | | | | | | | that fixes the following problems: 1. Removing bogus ';' in some configure.in (cosmetical fix) 2. Moves GAS_CODE16 checks to libbsp/i386/*/configure.in (essential fix) #2 was responsible for the gcc/binutils-2.9.5 choking while building for the pc386.
* File removed as it was not being used.Joel Sherrill2000-01-111-268/+0
|
* Removed old hack of using Configuration Table entry ticks_per_timesliceJoel Sherrill2000-01-1130-620/+450
| | | | | | | being set to 0 to indicate that there should be no Clock Tick. This was used by the Timing Tests to avoid clock tick overhead perturbing execution times. Now the Timing Tests simply leave the Clock Tick Driver out of the Device Driver Table.
* Patch from Emmanuel Raguet <raguet@crf.canon.fr> to correct macroJoel Sherrill2000-01-111-4/+4
| | | | | expansion. These macros were modified to correct warnings and obviously needed more parentheses to expand correctly.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-30 10:55:07 +0000