summaryrefslogtreecommitdiffstats
path: root/cpukit (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to correct theJoel Sherrill1999-04-122-30/+931
| | | | --enable-tests problem a better way.
* Added line to initialize timer_max.Joel Sherrill1999-04-121-0/+2
|
* MPC821 support and PPC patches from Andrew Bray <andy@madhouse.demon.co.uk>:Joel Sherrill1999-04-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In c/src/exec/score/cpu/powerpc/rtems/score/ppc.h: A lot of hardware interrupts were omitted. Patch enclosed. I have also added the 821. In c/src/exec/score/cpu/powerpc/rtems/score/cpu.h: My patch adds the 821. In c/src/exec/score/cpu/powerpc/cpu.c: I have added the MPC821, and also fixed up for the missing hardware interrupts. It is also inconsistent with c/src/lib/libcpu/powerpc/mpc860/vectors/vectors.S. This has been fixed. In c/src/lib/libcpu/powerpc/mpc860/vectors/vectors.S: Fixed an inconsistency with cpu.c. I also include some new files to go with the above patches. These are the cpu library rtems-19990331/c/src/lib/libcpu/powerpc/mpc821/* and c/src/exec/score/cpu/powerpc/mpc821.h which are minor modifications of the 860 equivalents. Other comments: The various accesses to the DPRAM on the 860 are done with a linktime symbol. This could be done dynamically at run time by reading the immr register, and masking off the lower 16 bits. This takes the same amount of time as loading an address constant, and the same number of instructions as well (2). In c/src/lib/libcpu/powerpc/mpc860/console-generic/console-generic.c: This will silently fail if you attempt to use SCC1. This is only relevant if you are not using SCC1 for ethernet. This file also sets one of port B output pins for each port. This is NOT generic, it should be in the BSP specific console driver.
* Untar support submitted by Jake Janovetz <janovetz@tempest.ece.uiuc.edu>.Joel Sherrill1999-04-062-0/+406
|
* Patch from Emmanuel Rauget (raguet@crf.canon.fr) to add a htons on theJoel Sherrill1999-04-022-212/+233
| | | | sin_port.
* Moved sparc specific version of in_cksum_hdr to an inline routine likeJoel Sherrill1999-04-012-31/+43
| | | | | the reset of the CPU specific implementations after comment from Eric Norum.
* Disable IXON by default based on comment from Eric NorumJoel Sherrill1999-04-011-1/+1
| | | | | | | | | | | | | | | <e.norum@sk.sympatico.ca> and concerns from Thomas Doerfler <td@imd.m.ISAR.de> when he submitted the patch: Since enabling XON/XOFF has such a major performance hit on `smart' output devices I think it should be *off* by default. I think some thought should be given to adding hooks for hardware that can support XON/XOFF without software intervention, or for hardware like the 68360 SCC's that can use large buffers, but still handle special characters immediately. The patch you sent is a very good start, though. I just think that the software flow control should be off -- to match the way the serial I/O support has worked up until now.
* Patch from Thomas Doerfler <td@imd.m.ISAR.de> to add flow control:Joel Sherrill1999-03-311-32/+272
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some lines for "documentation": ====================================== One thing should be noted: when XON/XOFF is enabled, the serial device will always work with one-character buffers, so the interrupt load for the CPU might get higer, especially on devices like MC68360 and MPC860, where the serial channels are capable of using big buffers. But, once again, this only happens when XON/XOFF is actually selected. Please note that the flag IXON is set by default, so outgoing XON/XOFF flow control is enabled by default. XON/XOFF is controlled using the "standard" fields IXON/IXOFF in the termios structure. The termios flag IXANY is not (yet) supported. Hardware handshake for the incoming data stream is controlled using the standard flag CRTSCTS. If this flag is set, whenever the receive buffer is almost full, the driver function "device.stopRemoteTx()" is called, when the receive buffer has more space available, "device.startRemoteTx()" is called again. If the driver does not provide these interface functions (entries in device structure are NULL pointers), then these calls are suppressed. Changes of the flow control options during operation should work at any time, but this has not been extensively tested. No changes to the device driver interface are needed. ================================================ One critical point when using this patch might be, that any BSP using this version of termios will now have outgoing flow control enabled by default, so the behaviour of these BSPs will change here. The option IXON has already been set in older termios by default, but it did not work until this patch. Maybe this option should be switched off by default, what do you think?
* Removed asserts that shouldn't be called and commented case where thisJennifer Averett1999-03-313-4/+2
| | | | indicates an internal error.
* Corrected return value.Jennifer Averett1999-03-311-1/+1
|
* Fixed paths to include files so this will build.Joel Sherrill1999-03-318-0/+2581
|
* Patch from Chris Johns <ccj@acm.org>:Joel Sherrill1999-03-311-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | joel@OARcorp.com wrote: > > Chris, > > sp09 fails on the rtems_port_delete(0) call. This is supposed to give an > invalid id error. I can't find any changes other than the unlimited > objects patch which would have tripped this so would appreciate it if you > could look into it. I suspect that this is a side-effect of the unlimited > objects patch. > It is me. > > Basically, there are 0 ports configured in sp09. The test ends up > dereferecing NULL in local_table[0] and comes up with a non-NULL invalid > pointer. > The issue is not actually allocating a local_table for an object type which has a maximum value of 0. I cannot remember the exact workings of the id values and the local_table. I might have changed the nature from the pre-unlimited change. As you know the id's are an interesting game where performance is most important. > > I know the problem could be solved by adding a check for index == 0. But > I hate to slow this path down. I think you may have changed the way the > object information structure gets initialized. > ---- CVS log ---- This change lets the unlimited and sp09 tests run on the posix Linux BSP. A static local variable `null_local_table' has been added. This variable is always set to NULL. The `**local_table' element of the information structure is set to point to this variable earily in the initialisation. If the object type has more than 0 elements the `local_table' element is updated. All object types which have 0 elements reference `null_local_table'. This change fixes the problem sp09 found yet does not add any extra processing to the critical `_Objects_Get_local_object' function. ---- CVS log ----
* When compiled in debug mode, the POSIX threads inline file was notJoel Sherrill1999-03-311-0/+1
| | | | included and we ended up with undefined references.
* Patch from Eric Norum <eric@skatter.usask.ca> which changed the exitJoel Sherrill1999-03-311-2/+1
| | | | sequence.
* Removed warning for `#ifdef' argument starts with punctuation.Joel Sherrill1999-03-301-1/+1
|
* Removed warning for const removal.Joel Sherrill1999-03-301-1/+1
|
* Fixed typo where _POSIX_signals_Clear_process_signals was not prototypedJoel Sherrill1999-03-301-1/+1
| | | | and _POSIX_signals_Set_process_signals was done twice.
* Patch to add shutdown() routine from Tony R. Ambardar <tonya@ece.ubc.ca>.Joel Sherrill1999-03-301-0/+25
|
* Removed an uninitialized variable.Jennifer Averett1999-03-291-4/+5
|
* Fix based on bug report from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-03-241-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There seems to be an ugly dependency between posix-headers and libcsupport. Configuring rtems with ../rtems-rc-19990324-0/configure \ --target=i386-rtems \ --prefix=<somewhere> \ --disable-posix "make RTEMS_BSP=pc386" results into: [...] /opt/rtems/bin/i386-rtems-gcc --pipe -B/users/rtems/src/multi/build/pc386/lib/ -specs bsp_specs -qrtems -I/users/rtems/src/multi/build/pc386/lib/include/networking -g -Wall -ansi -fasm -O4 -fomit-frame-pointer -c -o o-pc386/utime.o ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c In file included from ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:16: /opt/rtems/i386-rtems/include/utime.h:4: sys/utime.h: No such file or directory ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: `struct utimbuf' declared inside parameter list ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: its scope is only this definition or declaration, ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: which is probably not what you want. ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c: In function `utime': ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:34: dereferencing pointer to incomplete type ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:34: dereferencing pointer to incomplete type make[4]: *** [o-pc386/utime.o] Error 1 make[3]: *** [all] Error 1 make[2]: *** [all] Error 1 make[1]: *** [all] Error 1 make[1]: Leaving directory `/lfs/poseidon/users/rtems/src/multi/build/c' make: *** [all] Error 1 Apparently sys/utime.h is one of the posix headers and therefore gets not installed (I suppose this is correct). IMO, this probably indicates that sys/utime.h has to be moved to another include subdirectory and should not be part of the posix-package. [AFAIK, sys/*.h are system dependent headers, so why should it be a posix-header? - Hmm]
* SPARC optimized version of IP checksum header routine. SubmittedJoel Sherrill1999-03-231-0/+32
| | | | by Jiri Gaisler <jgais@ws.estec.esa.nl>.
* Patch from Eric Norum <eric@skatter.usask.ca> to improve parsing ofJoel Sherrill1999-03-232-0/+45
| | | | | network interface names. This change does not introduce any compatibility problems.
* Another cleanup patch for the previous rejected hunk.Joel Sherrill1999-03-191-0/+1
|
* A cleanup patch on fcntl.c from Eric Norum <eric@skatter.usask.ca> forJoel Sherrill1999-03-191-0/+2
| | | | | 2 lines of code that did not get included when Joel tried to manually add a rejected patch.
* Patch from Eric Norum <eric@skatter.usask.ca> that adds externalJoel Sherrill1999-03-193-28/+72
| | | | fcntl support and an external fcntl handler for sockets.
* Unlimited objects patch from Chris Johns <ccj@acm.org>. Email follows:Joel Sherrill1999-03-178-147/+683
| | | | | | | | | | | | | | | | | | | | | | | | | First, the unlimited patch. I have compiled the unlmited patch for the Linux posix BSP only and it seems to work cleanly. I would like a really major application run on this change before commiting as the changes are very core and significant. I am currently building all the tests to run. I have no targets suitable to test on at the moment. I have tested the patch for inline functions and macros. Turning macros on has found some core bugs. I have fixed these but have not run all the tests. Please review the patch for these changes. They are: 1) The conditional compilation for MP support broke the core messages code. You cannot embed a conditional macro in another macro. The Send and Urgent Send calls are macros. 2) User extensions handler initialisation now has two parameters. I have updated the macros to support the extra parameter. The patch also contains the gcc-target-default.cfg fix required to build the kernel. More of a by product than a fix for you.
* Added ftpd server from Jake Janovetz <janovetz@tempest.ece.uiuc.edu>.Joel Sherrill1999-03-162-0/+1093
|
* Use proper include for libio.h.Joel Sherrill1999-03-166-12/+6
|
* Corrected bug where pointer to doubly linked blocks was being incorrectlyJoel Sherrill1999-03-081-2/+34
| | | | calculated.
* Added code to translate internal libio flags to POSIX style flags.Joel Sherrill1999-03-081-3/+20
|
* Added support for F_GETFL and F_SETFL.Joel Sherrill1999-03-081-2/+3
|
* Added F_GETFL support so the fdopen() implementation in newlib 1.8.1Joel Sherrill1999-03-064-2/+43
| | | | | | | | would work. At the same time, the initial implementation of F_SETFL was added. A support routine was added to convert internal libio flags back to the POSIX style. Eventually the internal representation should be eliminated in the interest of simplicity and code reduction. This problem was reported by Jake Janovetz <janovetz@tempest.ece.uiuc.edu>.
* Patch from Eric Norum <eric@skatter.usask.ca> to eliminate externalJoel Sherrill1999-03-0121-276/+61
| | | | | IO handlers scheme that was implemented originally just to support sockets. The file system IO switch is more general and works fine.
* Part of the automake VI patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-03-012-19/+19
| | | | | | | | | | | | | | | | > 5) rtems-rc-19990202-1.diff/reorg-install.sh > > reorg-install.sh fixes a Makefile variable name clash of RTEMS > configuration files and automake/autoconf standards. > Until now, RTEMS used $(INSTALL) for install-if-change. Automake and > autoconf use $(INSTALL) for a bsd-compatible install. As > install-if-change and bsd-install are not compatible, I renamed all > references to install-if-changed to $(INSTALL_CHANGED) and used > $(INSTALL) for bsd-install (==automake/autoconf standard). When > automake will be introduced install-if-change will probably be replaced > by $(INSTALL) and therefore will slowly vanish. For the moment, this > patch fixes a very nasty problem which prevents adding any automake file > until now (There are still more).
* Changed IMFS to use IMFS_NAME_MAX as the maximum length of a basenameJoel Sherrill1999-02-248-24/+34
| | | | | | | rather then NAME_MAX. NAME_MAX is 255 and that lets IMFS chew up memory too fast. Perhaps in the future, the places in IMFS that put a maximum length name string on the stack and the jnode structure does not include a maximu length name string can be fixed so this is not a problem.
* Corrected name of constant so this would compile.Joel Sherrill1999-02-241-1/+1
|
* Moved back up in tree.Joel Sherrill1999-02-198-0/+4202
|
* Moved asm.h back up in tree.Joel Sherrill1999-02-1914-0/+1728
|
* Moved to proper rtems/scoreJoel Sherrill1999-02-1927-6045/+289
|
* Part of the automake VI patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-02-1834-0/+13100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > 4) rtems-rc-19990202-0.diff /reorg-score-cpu.sh > > reorg-score-cpu.sh reorganizes the cpu/<cpu>/* subdirectories in a > similar manner than previous reorg scripts did. rtems-rc-19990202-0.diff > contains the diffs after reorg-score-cpu.sh has been run on a > rtems-19981215 snapshot + my patches up to rtems-rc-19990131-2.diff. > > This patch is rather nasty and may break something. However, I've tested > it for about 10 different target/bsp pairs and believe to have shaken > out most bugs. I wonder about the following .h files that were not moved: a29k/asm.h a29k/cpu_asm.h i386/asm.h i960/asm.h m68k/asm.h m68k/m68302.h m68k/m68360.h m68k/qsm.h m68k/sim.h mips64orion/asm.h mips64orion/cpu_asm.h mips64orion/mips64orion.h no_cpu/asm.h no_cpu/cpu_asm.h powerpc/asm.h powerpc/mpc860.h sh/asm.h sparc/asm.h sparc/erc32.h
* Yet another part of automake VI from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-02-187-2466/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > 4) rtems-rc-19990202-0.diff /reorg-score-cpu.sh > > reorg-score-cpu.sh reorganizes the cpu/<cpu>/* subdirectories in a > similar manner than previous reorg scripts did. rtems-rc-19990202-0.diff > contains the diffs after reorg-score-cpu.sh has been run on a > rtems-19981215 snapshot + my patches up to rtems-rc-19990131-2.diff. > > This patch is rather nasty and may break something. However, I've tested > it for about 10 different target/bsp pairs and believe to have shaken > out most bugs. I wonder about the following .h files that were not moved: a29k/asm.h a29k/cpu_asm.h i386/asm.h i960/asm.h m68k/asm.h m68k/m68302.h m68k/m68360.h m68k/qsm.h m68k/sim.h mips64orion/asm.h mips64orion/cpu_asm.h mips64orion/mips64orion.h no_cpu/asm.h no_cpu/cpu_asm.h powerpc/asm.h powerpc/mpc860.h sh/asm.h sparc/asm.h sparc/erc32.h
* Patch from Emmanuel Raguet <raguet@crf.canon.fr>:Joel Sherrill1999-02-181-1/+9
| | | | | | | You will find enclosed a patch which contains, for Intel PC386 target : - an Ethernet driver for DEC21140 device based boards. - a simple cache management with paging mechanism.
* GLobal reentrancy structure is now dynamically initialized.Joel Sherrill1999-02-181-1/+2
|
* Patch from Eric Valette <valette@crf.canon.fr> to undo the patchJoel Sherrill1999-02-151-2/+0
| | | | that added ifdef on the pc386.
* POSIX timer support.Joel Sherrill1999-02-101-1/+1
|
* Set the read/write offset to 0 when the file is opened. The ACVC had a testJoel Sherrill1999-02-101-0/+1
| | | | | that performed the sequence open/write/close/open/read/close on a file. It did not get the correct result since the file descriptor was reused.
* Corrected multiple places the file size was not being properly updated.Joel Sherrill1999-02-101-2/+8
|
* Added getcwd().Joel Sherrill1999-02-101-0/+280
|
* POSIX timer support modifications.Joel Sherrill1999-02-103-4/+16
|
* Comments fixed after problem report from Ian Lance Taylor <ian@airs.com>.Joel Sherrill1999-02-101-19/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-27 16:23:37 +0000