summaryrefslogtreecommitdiffstats
path: root/c/src/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Regenerated.Joel Sherrill1999-05-278-621/+1107
|
* Removed all post 4.0 changes.Joel Sherrill1999-05-201-81/+78
|
* Regenerated.Joel Sherrill1999-05-188-1107/+621
|
* Spacing correction.Joel Sherrill1999-05-181-1/+0
|
* Patch from D. V. Henkel-Wallace <gumby@zembu.com> to remove compilerJoel Sherrill1999-05-173-4/+4
| | | | warnings.
* Added 3COM 3C509 driver from Rosimildo DaSilva <rdasilva@connecttel.com>.Joel Sherrill1999-05-147-2/+2247
|
* Enabled compilation of rtems_servers at request of Jake JanovetzJoel Sherrill1999-05-144-6/+8
| | | | <janovetz@tempest.ece.uiuc.edu>.
* Fix based on bug report from Jay Kulpinski <jskulpin@eng01.gdds.com>Joel Sherrill1999-05-111-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | that the per task reentrancy structure was not being processed properly during exit(). joel@oarcorp.com wrote: > > > This is always an ugly place to poke around. :( > > The code in newlib/libc/stdlib/exit.c walks the atexit chain for the > reentrancy structure for JUST the current task. The code in libc_wrapup() > does it for both the current task and the global reentrancy structure > (which tends to be where driver atexit()'s were registered. > > So I think the _wrapup_reent(0) in libc_wrapup() should be commented out. > > If you concur, then I will make the change and improve the comment on this > line of code to explain things: > > libc_wrapup(); /* Why? XXX */ > > --joel That does the job. cdtest.exe works correctly now.
* Patch from Erik Ivanenko <erik.ivanenko@utoronto.ca> to correct 32 bitJoel Sherrill1999-05-111-0/+2
| | | | jmp relative offset from .reset section.
* Error reporting fixed by Jennifer.Joel Sherrill1999-05-071-15/+15
|
* Bug fix from Gunter Magin <magin@@skil.camelot.de>:Joel Sherrill1999-05-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Bug fix from Gunter Magin <magin@skil.camelot.de>:Joel Sherrill1999-05-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Patch from Emmanuel Raguet <raguet@crf.canon.fr>:Joel Sherrill1999-04-281-1/+3
| | | | | | | | | | 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.
* Patch from Eric Norum <eric@cls.usask.ca> to corrent a miscount in lengthJoel Sherrill1999-04-271-1/+1
| | | | that results in an error in parsing network unit names/numbers.
* New BSP from Tony R. Ambardar <tonya@ece.ubc.ca> from theJoel Sherrill1999-04-2348-0/+5933
| | | | | | | | 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.
* Added lstat().Joel Sherrill1999-04-223-7/+40
|
* Changed ioctl() prototype to be more like Linux/POSIX than BSD to easeJoel Sherrill1999-04-192-2/+2
| | | | porting of ACE to RTEMS.
* Regenerated.Joel Sherrill1999-04-196-60/+72
|
* Direct .gcc_exc section to ram to eliminate the warning Ralf Corsepius isJoel Sherrill1999-04-191-1/+1
| | | | seeing.
* After discussion with Eric Norum <eric@skatter.usask.ca>,Joel Sherrill1999-04-199-16/+30
| | | | | I added __INSIDE_RTEMS_BSD_TCPIP_STACK__ that trips all the needed macro definitions for a network driver.
* Patch from Erik Ivanenko <erik.ivanenko@utoronto.ca> to eliminate aJoel Sherrill1999-04-191-1/+2
| | | | warning.
* New files.Joel Sherrill1999-04-192-0/+128
|
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to add scitabs.c toJoel Sherrill1999-04-191-1/+1
| | | | CLEAN_ADDITIONS.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-04-19382-387/+387
| | | | | | | | | | | | | | This one is an enhancement to acpolish. It replaces some Makefile variables by others variable in Makefile.ins (tries to use unique name for some variables). It therefore eases parsing Makefile.ins for further automatic Makefile.in conversions in future. To apply: cd <rtems-source-tree> sh <path-to>/rtems-rc-19990407-8.sh ./autogen
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-04-192-83/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an attempt to work-around a couple of nasty bugs in librdbg's Makefiles and configuration: Configure and build RTEMS as below: configure --enable-networking --enable-rdbg --target=i386-rtems make RTEMS_BSP=i386ex After a few minutes you will notice that building aborts in librdbg .... Analysis: 1) librdbg is tried to be built, though librdbg is not supported and the required directory hierarchy librdbg/i386/i386ex/ is not existant. The cause for this is incorrect setting of HAS_RDBG in most make/custom/*.cfg files (except pc386.cfg). At the moment all custom/*.cfg files (except pc386.cfg) in general are required to contain HAS_RDBG=no. However, having HAS_NETWORKING=no in most custom/*.cfg files and the toplevel configure script suppress building librdbg for all CPUs except of i386. => The i386ex BSP falls though this scheme and librdbg is tried to be build (CPU=i386 and HAS_NETWORKING=yes). 2) The Makefile.ins below lib/librdbg in general support i386/pc386 only and are not capable to be used for multiple CPUs or BSPs (RPCGEN generates it's target and bsp-specific files into librdbg/, therefore no other CPU or BSP can ever be built afterwards). This problem is hidden until now, because only a single CPU/BSP pair (i386/pc386) is really supported. 3) The Makefile.ins below lib/librdbg can delete source files due to improper handling of source files (make clean removes the *.x files in the source-tree when configuring inside of the source-tree). The patch below tries to work-around these problems for the i386ex and the pc386 BSPs. This work-around is rather fragile (it applies rpcgen -D, I don't know how portable this is) and incomplete (all custom/*.cfg except of pc386.cfg should contain HAS_RDBG=no), nevertheless it should work.
* Fixed some spacing issues.Joel Sherrill1999-04-191-4/+5
|
* Patch from Ralf Corsepius <corsepiu@@faw.uni-ulm.de>:Joel Sherrill1999-04-161-1/+0
| | | | | | | | | | | | | | 2) ./c/src/lib/libbsp/i386/go32/startup > all: ${ARCH} $(SRCS) $(PGM) > $(INSTALL_CHANGE) ${PROJECT_RELEASE}/lib > > This also is very questionable, because it means "install $(PROJECT_RELEASE)/$/lib to the void". I think, removing the INSTALL_CHANGE is the right way to fix it.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-04-161-6/+1
| | | | | | | | | | | | | | | | | | | 1) ./c/src/lib/libbsp/i386/i386ex/startup/Makefile.in > preinstall: > $(INSTALL_CHANGE) ${IMPORT_SRC} . > > # ${CP} ${IMPORT_SRC} . > > > This fragment is broken, because IMPORT_SRC is always empty. IMO, the fix would be to remove this fragment or to replace it with test -z "${IMPORT_SRC}" || cp ${IMPORT_SRC} . if an external shell variable IMPORT_SRC shall be supported by this Makefile, which IMO should not be done.
* Corrected to reflect new way of doing mips constructors.Joel Sherrill1999-04-162-12/+94
|
* Added .eh_fram and .gcc_exc sections.Joel Sherrill1999-04-161-0/+11
|
* Added reentrant versions.Joel Sherrill1999-04-152-0/+41
|
* Updated version string.Joel Sherrill1999-04-151-2/+1
|
* Minor corrections from Jay Kulpinski <jskulpin@eng01.gdds.com>.Joel Sherrill1999-04-141-3/+3
| | | | | | This first one below looked like it only belonged in a virtual memory environment. The second one was causing problems without the PROVIDE() - I don't know why.
* Bug report from Ralf on UNIX port where the S_IR* constants were notJoel Sherrill1999-04-141-0/+1
| | | | defined.
* Bug fix from Brendan Simon <brendan@dgs.monash.edu.au> with fix confirmedJoel Sherrill1999-04-132-2/+2
| | | | by Andrew Bray <andy@madhouse.demon.co.uk>.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-04-121-1/+1
| | | | | | | | Installing of bsp_specs for aliased bsps is broken. Instead of installing RTEMS_BSP_FAMILY/bsp_specs, RTEMS_BSP/bsp_specs was tried to be installed. The patch below should fix this problem (tested with mips64orion p4600 and p4650).
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-04-1218-594/+1040
| | | | | | | | | | | | | | | | | | | | | | This patch addresses a few minor issues and contains a few (minor) preparations for automake. * configure.in: Fix for handing c/src/tests subdirectory handling (FIX) * aclocal/rtems-top.m4: + Add TARGET_SUBDIR and --with-target-subdir (preparation of future enhancements for cross-compiling) + Activate RTEMS_ROOT handling (automake preparation) * automake/*.am: replace comments "#" with "##" so that comments won't get included into Makefile.in's anymore * c/update-tools/* automake support (NEW) * ./autogen update/enhancement (cf. ./autogen for details) After applying this patch please run: ./autogen cvs add c/update-tools/configure.in cvs add c/update-tools/Makefile.am cvs add c/update-tools/aclocal.m4
* Addressed this bug report:Joel Sherrill1999-04-122-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Date: Mon, 12 Apr 1999 00:38:04 +0000 From: Brendan Simon <brendan@dgs.monash.edu.au> To: Jay Monkman <jmonkman@frasca.com>, "joel@OARcorp.com" <joel@oarcorp.com> Subject: [Fwd: Goof in SMC initialize for mpc860] Nick Simon reported this bug in the eth_comm BSP sources. I see that it is still there in the latest snapshot that Joel sent me (thanks). I thought I better forward this on to you guys. Brendan. Nick.SIMON@syntegra.bt.co.uk wrote: > Sice I believe you're using the same base BSP as I am (you sent it to me) I > thought I'd mention.. > > In console-generic.c, in m860_smc_initialize, the receive buffer is malloced > and assigned to RxBd[port+3]-> buffer - it should be [port-1]. > > TTFN B
* MPC821 support and PPC patches from Andrew Bray <andy@madhouse.demon.co.uk>:Joel Sherrill1999-04-0715-1/+2953
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to preinstallJoel Sherrill1999-04-0632-62/+12
| | | | all bsp_specs.
* Untar support submitted by Jake Janovetz <janovetz@tempest.ece.uiuc.edu>.Joel Sherrill1999-04-065-1/+471
|
* Patch from Andrew Bray <andy@chaos.org.uk>:Joel Sherrill1999-04-067-4/+25
| | | | | | In your various bsp_specs files, even when ecrti.o is defined as a startfile, ecrtn.o is not defined as an endfile. Instead it seems to be in the library list - untidy.
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1999-04-061-0/+6
| | | | | | | I'd like to make the following change which adds the m360 structure information to the debugging symbols in the final executable. This makes it much easier to use the debugger to look at the elements of the m360 structure.
* Patch from Emmanuel Rauget (raguet@crf.canon.fr) to add a htons on theJoel Sherrill1999-04-022-212/+233
| | | | sin_port.
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to address problemsJoel Sherrill1999-04-015-19/+19
| | | | on BSPs that install there own tools.
* 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.
* Removed warning.Joel Sherrill1999-04-011-4/+6
|
* 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?
* Regenerated.Joel Sherrill1999-03-314-391/+229
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-30 12:29:25 +0000