summaryrefslogtreecommitdiffstats
path: root/c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Made to compile after hacking tftp driver into beginnings of a mini-filesystem.Joel Sherrill1999-01-2115-117/+897
|
* Changed call to __rtems_close() to close().Joel Sherrill1999-01-202-6/+6
|
* Update of network driver from Erik Ivanenko <erik.ivanenko@utoronto.ca>.Joel Sherrill1999-01-206-165/+399
| | | | | | | | | | | Comments follow: Here is the contents of the network directory of the i386ex BSP. The reset function has been recently added, and tested through a command line interface. A reset event to the reset thread to reset the NIC. This is done when the ISR detects that the NIC is in an invalid state. It has not been tested "in real life" since the board has not seen an invalid state since the reset function was implemented.
* Patch from Eric Norum <eric@skatter.usask.ca> to make m68360.h usableJoel Sherrill1999-01-201-357/+366
| | | | | | | | outside RTEMS. Comment: I found a couple of places other than RTEMS where I'd like to use the declarations supplied in m68360.h. To make this easier to do, I've redone the declarations in m68360.h to use standard C types.
* More general fix based on bug report and patch from Ian Lance TaylorJoel Sherrill1999-01-2028-4/+84
| | | | | | | | | | <ian@airs.com> to fix this problem: There is a small bug in __rtems_close in c/src/lib/libc/libio.c. It does not check whether the file descriptor it is passed is open. This can cause it to make a null dereference if it is passed a file descriptor which is in the valid range but which was not opened, or which was already closed.
* Removed referencing to network driver since it has not been merged yet.Joel Sherrill1999-01-192-6/+6
|
* Changed definition of ASMFLAGS since as does not recognize -B optionJoel Sherrill1999-01-191-1/+1
| | | | used in gcc.
* Added comments for changing to a filesystemJoel Sherrill1999-01-193-0/+12
|
* Per bug report from Jiri Gaisler that RTEMS would no longer buildJoel Sherrill1999-01-192-2/+26
| | | | | with the --disable-posix option, stubs for some routines (_getpid_r and _kill_r) that are normally defined with POSIX were added.
* Removed duplicate lines in file.Joel Sherrill1999-01-191-14/+0
|
* Patch from Jiri Gaisler <jgais@ce.chalmers.se>:Joel Sherrill1999-01-196-17/+53
| | | | | | | | getting the spurious trap handling to work required a couple more fixes - I have attached a patch against rtems-4.0.0 with the necessary changes. I also added functionality so that the address of the trapped instruction is reported and in case of a data access error, the data address is also reported.
* Moved sys/ioctl.h to libc supportJoel Sherrill1999-01-193-19/+2
|
* Bug report from Jiri Gaisler <jgais@ws.estec.esa.nl>:Joel Sherrill1999-01-132-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > I think I have found a bug in src/exec/scor/sparc/cpu/erc32.h in: > > > > #define ERC32_Disable_interrupt( _source, _previous ) \ > > do { \ > > unsigned32 _level; \ > > unsigned32 _mask = 1 << (_source); \ > > \ > > sparc_disable_interrupts( _level ); \ > > (_previous) = ERC32_MEC.Interrupt_Mask; \ > > ERC32_MEC.Interrupt_Mask = _previous | _mask; \ > > sparc_enable_interrupts( _level ); \ > > (_previous) &= ~_mask; \ <- IS THIS CORRECT...? > > } while (0) > > > > The previous interrupt mask is returned after first clearing the > > bit to be disabled, regardless whether the bit was set before or > > not. If the bit was set (interrupt masked), subsequent call to > > ERC32_Restore_interrupt() will enable the interrupt even though > > it was supposed to be masked. This is indeed what happens in > > DEBUG_puts when polled console I/O is used. In my opinion, the > > last statement in the macro should be removed - what is your opinion? > > I think the "~" shouldn't be there. I recall that the intent of that line > is to only return the state of the interrupts you were concerned with. > Removing the line returns entire state. Given that the value returned > shuold only be used in conjunction with the map, I suppose either removing > the ~ or the entire line is correct? I can go either way. Just let me > know which you think is more correct and the source will change. :) Hmmm, just removing the '~' should be OK. DEBUG_puts() seems to be the only user of ERC32_Restore_interrupt() anyway ...
* Patch from Chris Johns <ccj@acm.org> to get around a C++ problem with psim.Joel Sherrill1999-01-051-13/+13
| | | | | | | | | | | | | | | | | | This problem should and likely was occurring with other BSPs. This is from Chris' email: I had a look in the psim bsp for the older snapshot I have and it looks like you are using the `libbsp/shared/main.c' and this is known to work. I have just built the powerpc tools, and compiled the bsp. I have not added the linker command file patch so got the list of linker warnings. It looks to me like a compiler bug. The `main' call is being inlined and when that happens the special code to call `__eabi' is not being added to the inlined version. I have attached a patch which places `main' after `boot_card' and a call to main is now generated. I have not tested it but it should work. I also include a dump of `boot_card' and `main' showing the bug.
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to use puts and have ↵Joel Sherrill1999-01-043-3/+9
| | | | prototype.
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to fix braces nesting problem.Joel Sherrill1999-01-043-3/+6
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to make macro nest ↵Joel Sherrill1999-01-043-9/+15
| | | | properly in conditionals
* Removed blank linesJoel Sherrill1999-01-044-6/+0
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to remove unused variable.Joel Sherrill1999-01-041-1/+0
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to mark sav as unused.Joel Sherrill1999-01-041-1/+1
|
* Patch from Jay Kulpinski <jskulpin@eng01.gdds.com> to get cdtest.exe to run.Joel Sherrill1998-12-171-0/+2
|
* changed version to 19981217Joel Sherrill1998-12-171-1/+1
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to eliminate anotherJoel Sherrill1998-12-171-1/+1
| | | | compiler dependent flag in a Makefile.
* New file added in automake reorg.Joel Sherrill1998-12-171-0/+30
|
* Automake reorgnization.Joel Sherrill1998-12-178-0/+112
|
* changed version to 19981215Joel Sherrill1998-12-161-1/+1
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> heading towardJoel Sherrill1998-12-169-12/+106
| | | | | | | | | | | | automake: Notes: * I didn't yet touch the cpu subdirectory. I still need some time to think on how to handle them. * I probably will wait for the next snapshot before mailing more patches (I still have some pending), giving you a chance to apply them and me a chance to become target of the bullets which will probably be aimed at me after these modifications.
* More automake preparation changes from Ralf CorsepiusJoel Sherrill1998-12-154-7/+46
| | | | <corsepiu@faw.uni-ulm.de>.
* Moved around per Ralf Corsepius as preparation for automakeJoel Sherrill1998-12-1515-2014/+0
|
* Part II automake reorg by Ralf CorsepiusJoel Sherrill1998-12-152-7/+2
|
* Part II automake reorg by Ralf CorsepiusJoel Sherrill1998-12-1566-7521/+0
|
* Added files as part of moveJoel Sherrill1998-12-156-0/+84
|
* Switched to use of ASM compilation conditional.Joel Sherrill1998-12-152-4/+4
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1998-12-153-3/+3
| | | | | | | | | | | | | | | | | | | | | | | Some Makefile.ins depend on gcc by hard-coded gcc-specific compiler flags: -g added to CFLAGS /LDFLAGS in > find . -name Makefile.in -exec grep -l ' \-g' {} \; ./c/src/lib/libbsp/i386/i386ex/startup/Makefile.in ./c/src/lib/libbsp/i386/pc386/tools/Makefile.in -Wall added CFLAGS in > find . -name Makefile.in -exec grep -l ' \-Wall' {} \; ./c/src/exec/score/tools/sh/Makefile.in ./c/src/lib/libbsp/i386/pc386/tools/Makefile.in Both -g and -Wall should not be used in any Makefile.in (Yes, I know, tools/sh/Makefile.in was written by me :-). I'd like to propose to remove these flags from the files mentioned above.
* Changed reference from no_cpu to mips64orion.Joel Sherrill1998-12-152-2/+2
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to reorganize POSIXJoel Sherrill1998-12-152-2/+2
| | | | | | | | | | | | | | | | | | | | | | directory in preparation for automake: Here is a shell script which reorganizes some parts of the exec/posix source tree. This shell scripts moves include files below exec/posix to different locations than now. It doesn't yet apply automake, but still use the old autoconf configuration scheme. It doesn't influence the build scheme at all (unless I corrupted something), only the location of the header files is different, which would ease applying automake later. The purpose of this shell script is to demonstrate the style of structural changes I would like to see in rtems in near future to prepare a smooth transition to automake. Then CC could pickup rtems' header files from their location inside of the source tree in future, instead of the build tree as it is done now. In case you would accept this patch/script, there would be more similiar ones to come.
* Moved around per Ralf Corsepius as preparation for automakeJoel Sherrill1998-12-1545-4254/+0
|
* 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-14220-373/+1400
| | | | | .s files to .S in conformance with GNU conventions. This is a minor step along the way to supporting automake.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to rename allJoel Sherrill1998-12-141-0/+28
| | | | | .s files to .S in conformance with GNU conventaons. This is a minor step along the way to supporting automake.
* Corrected prototype to confirm to POSIX 1003.1b.Joel Sherrill1998-12-144-20/+8
|
* Renamed ASFLAGS to ASMFLAGS for consistency per suggestion from Ralf ↵Joel Sherrill1998-12-141-4/+4
| | | | Corsepius <corsepiu@faw.uni-ulm.de>.
* Merged Eric Norum's select patch that was based on 4.0 and resolvedJoel Sherrill1998-12-1043-608/+405
| | | | all conflicts.
* RDBG headers files ignored if not configuredJoel Sherrill1998-12-101-0/+4
|
* Fixed conflict between patchesJoel Sherrill1998-12-101-4/+3
|
* Patch from Ian Lance Taylor <ian@airs.com>:Joel Sherrill1998-12-1013-0/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-079-15/+36
| | | | | | | | | | | | | 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-0390-21/+18877
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-07 11:54:43 +0000