summaryrefslogtreecommitdiffstats
path: root/c/src/exec (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Switch from .s to .S on includeJoel Sherrill1998-12-141-2/+2
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to rename allJoel Sherrill1998-12-1424-27/+27
| | | | | .s files to .S in conformance with GNU conventions. This is a minor step along the way to supporting automake.
* Corrected prototype to confirm to POSIX 1003.1b.Joel Sherrill1998-12-142-10/+4
|
* Merged Eric Norum's select patch that was based on 4.0 and resolvedJoel Sherrill1998-12-1018-240/+187
| | | | all conflicts.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-104-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From: Eric Norum <eric@skatter.usask.ca> Date: Sat, 5 Dec 98 13:20:51 -0600 What do you think of this patch? It implements your `tap' suggestion in a way that adds support for all ethernet devices with no driver modifications. I also added a return value from the tap function. If the return value is zero, the packet will be passed up the chain as usual. If the return value is non-zero the mbuf holding the packet will be freed and the packet will be dropped. If you like it, please submit it to Joel. I guess there needs to be an addition to the network documentation describing the additional ioctl's -- and a big warning that the tap function is called from a context that holds the network semaphore. Here is Eric's patch. I've tested it a bit, and made a couple of trivial changes. This is certainly better than mine: it should work for all Ethernet drivers. ================================================== The only concern I have about this patch is that the tap function may want to fiddle with the mbuf, calling functions like m_pullup and the like. If those force the networking code to rearrange the mbuf structure, then the caller's call to m_freem may crash. I don't know if this is a realistic concern--I don't know enough about the mbuf layer.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-071-1/+1
| | | | This patch avoids a warning from the development version of gas.
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-073-5/+12
| | | | | | | | | | | | | RTEMS permits using the SO_SNDTIMEO and SO_RCVTIMEO socket options to set a timeout for most socket I/O operations. However, in RTEMS 4.0.0, those options do not affect connect or accept. I don't know of any way to put a timeout on those calls in RTEMS 4.0.0; can anybody point to one. Since it is frequently useful to have a timeout on accept, and sometimes useful to have a timeout on connect shorter than the BSD system default of 75 seconds, the following patch causes SO_RCVTIMEO to affect connect and accept.
* changed version to 19981203Joel Sherrill1998-12-042-2/+2
|
* Patch from Emmanuel Raguet <raguet@crf.canon.fr> to add remote debug serverJoel Sherrill1998-12-0310-19/+1491
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and RPC support to RTEMS. Thanks. :) Email follows: Hello, For Xmas, here is the Remote Debugger on RTEMS ! Here are 2 patches for the Remote Debugger on RTEMS for pc386 from Linux host : - one for RTEMS it self, - one for GDB-4.17. 1/ RTEMS patch -------------- This patch adds 2 libraries : - a simplified SUN RPC library - the Remote Debugger library The configuration command is the following : ../rtems4/configure --target=i386-rtemself --enable-rtemsbsp=pc386 --enable-rdbg The SUN RPC library is built only if networking is set. The RDBG library is built if networking and enable-rdbg are set. The function used to initialize the debugger is : rtems_rdbg_initialize (); A special function has been created to force a task to be in a "debug" state : enterRdbg(). The use of this function is not mandatory. 2/ GDB-4.17 patch ----------------- This patch create a new RTEMS target for GDB-4.17. The configuration command is the following : ./configure --enable-shared --target=i386RTEMS To connect to a target, use : target rtems [your_site_address] Then, attach the target using : attach 1 And... Debug ;) You can obtain the original GDB-4.17 on ftp://ftp.debian.org/debian/dists/stable/main/source/devel/gdb_4.17.orig.tar.gz This has been tested from a Debian 2.0.1 linux host.
* Added imfs_fdatasync routine that gets called from both fdatasync and datasync.Jennifer Averett1998-12-031-0/+26
|
* Added a imfs fdatasync routine that gets called for fdatasync and datasync.Jennifer Averett1998-12-031-0/+4
|
* Added source for F_DUPFD.Jennifer Averett1998-12-031-12/+18
|
* Modifications for RTEMS_UNIX.Jennifer Averett1998-12-035-1/+23
|
* Moved stackchk.h to rtems subdirectory.Joel Sherrill1998-12-032-2/+2
|
* Corrected spacing.Joel Sherrill1998-12-031-1/+1
|
* Corrected ifdef on RTEMS_MULTIPROCESSING so the queue is actually closed.Joel Sherrill1998-12-031-2/+4
|
* New files added as part of file system infrastructure effort.Joel Sherrill1998-11-234-0/+84
|
* Added base version of file system infrastructure. This includes a majorJoel Sherrill1998-11-2398-644/+8995
| | | | | | | | | | | | | | | | | | | | | | | | overhaul of the RTEMS system call interface. This base file system is the "In-Memory File System" aka IMFS. The design and implementation was done by the following people: + Joel Sherrill (joel@OARcorp.com) + Jennifer Averett (jennifer@OARcorp.com) + Steve "Mr Mount" Salitasc (salitasc@OARcorp.com) + Kerwin Wade (wade@OARcorp.com) PROBLEMS ======== + It is VERY likely that merging this will break the UNIX port. This can/will be fixed. + There is likely some reentrancy/mutual exclusion needed. + Eventually, there should be a "mini-IMFS" description table to eliminate links, symlinks, etc to save memory. All you need to have "classic RTEMS" functionality is technically directories and device IO. All the rest could be left out to save memory.
* Added --disable-multiprocessing flag and modified a lot of files to makeJoel Sherrill1998-11-2377-174/+717
| | | | it work.
* Renamed exception constants per requests from Erik IvanenkoJoel Sherrill1998-11-191-19/+19
| | | | <erik.ivanenko@utoronto.ca> and Eric Valette <valette@crf.canon.fr>.
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1998-11-199-175/+243
| | | | | | | | | | | | | | | 1) Socket timeout field changed from `short' to `long'. This makes longer timeouts possible. With a 1 kHz system clock the old system allowed timeouts only up to a little over 30 seconds! This change is a slightly cleaned-up version of the patch proposed by Ian Lance Taylor. 2) Major changes to BOOTP/DHCP reply handling. Now supports much of RFC2132. These changes were done at the request of, and with the assistance of, Erik Ivanenko. If you're making changes, you might want to change the network supplement Essentially just do a global search and replace of BOOTP with BOOTP/DHCP.
* changed version to 4.0.0-AFCCJoel Sherrill1998-10-292-2/+2
|
* Patch from Ian Lance Taylor <ian@airs.com>.Joel Sherrill1998-10-281-11/+19
| | | | | | | | | | | | | | | | | | | | | I just happened across the sync_io support in c/src/exec/score/cpu/unix/cpu.c (is this documented anywhere?). That looked more useful than the signal driven I/O I was using before, so I tried it. I ran across a few bugs in the way it uses select. Select changes its fd_set arguments, so you can't use global variables for them. You have to copy them into local variables first. If select returns -1 with errno set to EINTR, then it has not changed any of the fd_sets. You can't start looking at them. When clearing a descriptor, the code has the usual select off by one error when setting sync_io_nfds. I don't see how this code could ever have worked correctly. I have appended a patch for the problems I found.
* Merged Vista SCORE603e, Radstone PPCn_60x, and DY-4 DMV177 BSPs alongJoel Sherrill1998-10-281-0/+2
| | | | with libchip.
* changed version to 4.0.0Joel Sherrill1998-10-272-2/+2
|
* changed version to 4.0.0-beta4bJoel Sherrill1998-10-262-2/+2
|
* Changed all of these to stubs.Joel Sherrill1998-10-227-403/+34
|
* changed version to 4.0.0-beta4aJoel Sherrill1998-10-152-2/+2
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1998-10-141-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Rtems contains some perl scripts that use hard-coded paths to /usr/bin/perl or /usr/local/bin/perl I have already fixed these problems by adding some checks to configure.in. While doing this, I also cleaned up some more autoconf related problems for generating shell scripts. This patch might seem a bit scary to you, but I am quite confident it won't break something (I've been testing it for almost a week now, however it might introduce typos for a limited number configurations I don't have access to - But it shouldn't be a problem for you to test them :-). I expect to get this finished tonight, hence you will very likely have the patch when you get up tomorrow. Changes: * Check for PERL and disable all PERL scripts if perl wasn't found. * Generate all KSHELL-scripts with autoconf instead of make-script * Automatic dependency handling for autoconf generated KSHELL or PERL scripts (make/rtems.cfg) Notes: * this patch contains new files and deletes some other files. * The patch is relative to rtems-4.0.0-beta4 with my previous rtems-rc-981014-1.diff patch applied. Testing: I tested it with sh-rtems and posix under linux. Now all targets which are touched by this patch and which are not used while building for sh-rtems and posix still need to be tested. AFAIS, only the sparc/erc32 BSP should be affected by this criterion. And if you like to, you should also consider testing it on a Cygwin32 and a Solaris host for one arbitrary BSP.
* Added rest of opendir family and made it compile.Joel Sherrill1998-10-131-1/+16
|
* New files.Joel Sherrill1998-10-135-0/+328
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to correct minorJoel Sherrill1998-10-132-4/+4
| | | | cosmetic things.
* changed version to 4.0.0-beta4Joel Sherrill1998-10-122-2/+2
|
* New files.Joel Sherrill1998-10-122-0/+164
|
* Added header files per request from Chris Johns to avoid problemsJoel Sherrill1998-10-121-0/+4
| | | | in include file order.
* changed version to 981006Joel Sherrill1998-10-062-2/+2
|
* Corrected assembly language to use constants instead of addresses.Joel Sherrill1998-10-061-2/+2
| | | | Thanks to Rod Barman for this one.
* Added missing field (idle_task_stack_size) to CPU Table.Joel Sherrill1998-10-061-0/+1
|
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-10-011-5/+8
| | | | | | | | The reentrant versions of the malloc functions in c/src/lib/libc/malloc.c do not match the definitions in newlib. These will be used if you use newlib routines such as fdopen. I believe this patch to malloc.c is needed to provide the correct versions.
* changed version to 981001Joel Sherrill1998-10-012-2/+2
|
* Patch from Thomas Doerfler <td@imd.m.isar.de> to improve 403 support.Joel Sherrill1998-10-014-1/+42
| | | | | | | | | | | | | | | | | - c/src/exec/score/cpu/powerpc/ppc.h: some small changes (added ppc403 characteristics like a exception vector prefix register, some special register definitions). I am quite sure, they are compatible with the existing sources, although I did not check - c/src/exec/score/cpu/powerpc/cpu.c: There is one severe limitation in the exception entries: Due to the current code arrangement, the "branch absolute" to the ISR handler may only jump to the first 128MByte or the last 128MByte of the 4GByte address range. When the ppc403 is running out of ROM, the ROM functions are located in the last 128MByte (0xFFF00000 and up). These addresses were not handled correctly (sign reduced) in "install_raw_handler". The change I added should work on existing ppc BSPs aswell...
* Patch from Eric Norum <eric@skatter.USask.Ca>:Joel Sherrill1998-09-302-18/+1
| | | | | | | | | | | | | | | | | | | | | | | I found that my 68040/68360 test programs would not run even after I fixed the `wrong BSP' problem. It seems that there's a bug in the interrupt handling code for processors with hardware interrupt stacks (e.g. 68040). The wrong status register was getting pushed on the stack for the `return from exception' to call _ISR__Dispatch. This ended up making the context switch code run on the interrupt stack, so interrupt-driven context switches would always fail. I guess that no one has tried running any of the RTEMS-4.0 snapshots on a 68040 machine! Anyhow, here are the patches for 1) gen68360.cfg --- to fix the `wrong-BSP' problem. 2) m68k/cpu_asm.s --- to fix the hardware interrupt stack problem. With these patches in place, the network demo programs run on my 68040/68360 system. The paranoia program runs with no failures, defects nor flaws.
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1998-09-291-3/+2
| | | | | | | | | | | | | | Remember the test to see if a socket could be read and written at the same time by two different tasks? I discovered that if both tasks attempt to close the socket a panic can occur from inside the BSD code. Closing the same socket twice from two different threads is certainly an error, but a panic is not the greatest error reporting method :-) The following small change to the socket close routine should reduce the chances of the panic.
* New files.Joel Sherrill1998-09-273-1/+35
|
* Now compiles.Joel Sherrill1998-09-253-1/+7
|
* Added ENOSYS stubs for a number of process routines.Joel Sherrill1998-09-258-0/+132
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>.Joel Sherrill1998-09-232-2/+2
|
* IDLE task stack size now specified as a field in the CPU Table for allJoel Sherrill1998-09-2313-18/+17
| | | | ports.
* Modifed to zero out the C heap if the CPU Table indicates that theJoel Sherrill1998-09-231-0/+15
| | | | RTEMS workspace is to be zeroed out.
* changed version to 980923Joel Sherrill1998-09-232-2/+2
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-13 21:11:24 +0000