summaryrefslogtreecommitdiffstats
path: root/c/src/lib/libbsp/m68k/gen68360 (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Patch from Eric Norum <eric@skatter.usask.ca> to improve parsing ofJoel Sherrill1999-03-231-11/+18
| | | | | network interface names. This change does not introduce any compatibility problems.
* Towards automake XI patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-03-1910-31/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is the most scary of all proposals I've been mailing to you this week until now. It consists of 3 parts: 1. a patch 2. a perl script (acpolish) 3. a shell script wrapper to invoke the perl-script. The perl-script reads in each Makefile.in and modifies them ("polishes/beautifies" them :-). These modifications are not easy to describe: Basically, it hard-codes some automake Makefile-variables and rules into RTEMS autoconf-Makefile.ins (Note: autoconf vs. automake!!) and converts some settings/variables to configure scripts' requirements (Yes, plural). E.g. it adds the automake standard variables $top_builddir and $subdir, adds dependency rules for automatic re-generation of Makefiles from Makefile.in, adds support variables for relative paths to multiple configure scripts etc. The patch is a one-line patch to enable the support of the new features added by acpolish. The shell script is a wrapper which pokes around inside of the source tree for Makefile.ins and invokes acpolish on all autoconf-Makefile.ins. acpolish is designed to be able to run several times on the same Makefile.in and may once become a more general tool to convert RTEMS Makefile.in to automake. Therefore, I'd like to keep it inside of source tree. (e.g. as contrib/acpolish or c/update-tools/acpolish). However, it doesn't make sense to export it outside of RTEMS. To apply this: cd <source-tree> patch -p1 -E < <path-to-patch>/rtems-rc-19990318-1.diff tar xzvf <path-to>/rtems-rc-polish.tar.gz ./rtems-polish.sh ./autogen Note: The path contrib/acpolish is hard-coded into rtems-polish.sh, if you decide to put it in an alternative place, please modify rtems-polish.sh to reflect this change. Later: cvs rm make/rtems.cfg (It isn't used anymore) cvs add contrib cvs add contrib/acpolish cvs commit I've tested this intensively, but naturally I can't exclude bugs. Ralf. PS.: Most probably, this is the last "Towards automake" patch. The next one probably will be a real automake patch.
* Towards automake X patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-03-191-0/+5
| | | | | | | | | | | | | | | | | | | This one once again changes the scheme to preinstall bsp_specs. It moves generating PROJECT_ROOT/lib/bsp_specs to libbsp/<cpu>/<bsp>/wrapup/Makefile.in. I.e. it decentralizes generation of bsp_specs to a bsp-dependent directory, because preinstalling bsp_specs in a centralized Makefile like it has been done until now does not harmonize well with spliting the toplevel configure script in cpu and bsp-dependent configure scripts and automake. First apply the patch (rtems-rc-19990318-0.diff) below, then run the reorg-bsp_specs.sh script. IMO, this one is comparatively harmless and eases automake support significantly.
* Part of the automake VI patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1999-02-1810-5/+25
| | | | | | | | | | | | | | | | > 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).
* Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to rename allJoel Sherrill1998-12-144-6/+6
| | | | | .s files to .S in conformance with GNU conventions. This is a minor step along the way to supporting automake.
* Removed per Eric NorumJoel Sherrill1998-10-281-62/+0
|
* Patch from Eric Norum.Joel Sherrill1998-10-221-4/+6
|
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1998-09-101-1/+6
| | | | | | If you're getting close to a new snaphot, here's something that might be useful to add to the BSP README notes for systems with networking.
* Cleanup patch from Eric Norum.Joel Sherrill1998-08-241-3/+0
|
* Update from Eric Norum.Joel Sherrill1998-08-211-3/+2
|
* Patches from Eric NorumJoel Sherrill1998-08-204-11/+11
|
* FreeBSD stack compiles for the first time (except libc/strsep.c)Joel Sherrill1998-08-204-433/+498
|
* Added call to console_reserve_resources back in.Joel Sherrill1998-05-221-0/+6
|
* Patch from Eric Norum to switch to termios callback structure andJoel Sherrill1998-05-041-15/+85
| | | | add support for changing the baudrate.
* removed warning for implicit declaration of resolve()Joel Sherrill1998-05-021-0/+1
|
* update from Eric NorumJoel Sherrill1998-04-152-16/+15
|
* Numerous changes which in total greatly reduced the amount of sourceJoel Sherrill1998-04-152-36/+0
| | | | | | | | | | | | code in each BSP's bspstart.c. These changes were: + confdefs.h now knows libio's semaphore requirements + shared/main.c now copies Configuration to BSP_Configuration + shared/main.c fills in the Cpu_table with default values This removed the need for rtems_libio_config() and the constant BSP_LIBIO_MAX_FDS in every BSP. Plus now the maximum number of open files can now be set on the gcc command line.
* Transitioned to shared bsp_libc_init() and cleaned up comments.Joel Sherrill1998-04-152-48/+15
|
* Per suggestion from Eric Norum, went from one initial extension setJoel Sherrill1998-04-151-13/+0
| | | | | | to multiple. This lets the stack check extension be installed at system initialization time and avoids the BSP having to even know about its existence.
* Stack checker extension now accounted for in confdefs.hJoel Sherrill1998-04-141-8/+0
|
* Now accounts for region used by RTEMS malloc and extension usedJoel Sherrill1998-04-141-14/+0
| | | | by newlib.
* Moved bsp_postdriver_hook() to a shared file and made it a commonJoel Sherrill1998-03-302-27/+3
| | | | component.
* Moved memcpy to newlib/libc/machine/m68kJoel Sherrill1998-03-251-1/+1
|
* m68k software interrupt stack support from Chris Johns and Eric Norum.Joel Sherrill1998-03-252-4/+4
|
* Patches from Eric Norum:Joel Sherrill1998-03-239-174/+85
| | | | | | | Here are some patches to the gen68360 BSP. The improvements include: Boot prom run-time selection of DRAM size (1/4/16 Mbytes) Full 32-bit ethernet address obtained from boot prom. Updated README.
* Switch to using a shared main() for all of the embedded BSPsJoel Sherrill1998-03-214-22/+4
| | | | | | | | based on the GNU tools. This usually involved correcting the type of bsp_start(), bsp_cleanup(), adjusting the start code to call the right start routine (the shared boot_card()), and then removing code from bsp_start() which was performed in the new boot_card()/main() path.
* Patch from Eric Norum:Joel Sherrill1998-02-231-1/+1
| | | | | | | | | Here's another small patch. The changes to socket.h are to provide some definitions that UNIX BSD socket programmers expect. The memcpy.c contains a memcpy routine optimized for the CPU32+. When I run the ttcp benchmark with this routine I get host->68360 transfers around 165 kbytes/sec (about a 25% improvement) and 68360->host transfers of around 290 kbytes/sec (about a 50% improvement).
* Patch from Eric Norum:Joel Sherrill1998-02-191-36/+42
| | | | | | | | | | While trying to work through this problem I decided that the build-time selection of the console I/O operation (polling or interrupt) was too clumsy. Here's a patch that allows run-time (actually init-time) selection of the console I/O mode. It also shows the need for another `flags' or `options' field in the rtems_driver_address_table structure...
* updated copyright to 1998Joel Sherrill1998-02-178-8/+8
|
* Added .eh_frame, C++ constructor, and C++ destructor sections.Joel Sherrill1998-02-171-0/+3
|
* Incorporated Ralf Corsepius' idea for new -q flags to properly supportJoel Sherrill1998-02-111-2/+7
| | | | "gmake debug".
* Big patch form Ralf Corsepius described in this email:Joel Sherrill1998-01-3010-40/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here is the result of my nightly work to get RTEMS_ROOT=$srcdir working with different shells and relative/absolute paths. What I did is relatively simple in principle: Instead of setting RTEMS_ROOT in configure.in and then let configure substitute @RTEMS_ROOT@ inside the Makefiles, I now let each Makefile set RTEMS_ROOT from each Makefile's @top_srcdir@ value. The difference is subtile, but with enormous side effects: - If RTEMS_ROOT is set in configure, then the same single value will be propagated to all Makefiles. This breaks using relative paths, as the relative path to the root of the source tree is used inside of all subdirectory Makefiles. - Now each Makefile.in sets RTEMS_ROOT = @top_srcdir@. top_srcdir is computed individually by configure for each single Makefile.in, hereby receiving the correct value, no matter if relative or absolute paths are used. To get this working, I needed to remove setting RTEMS_ROOT from target.cfg.in, because this overrides the value of RTEMS_ROOT from each individual Makefile. Furthermore, I removed RTEMS_CUSTOM from the Makefiles and replaced all "include $(RTEMS_CUSTOM)" directives with"include $(RTEMS_ROOT)/make/custom/$(RTEMS_BSP)". Perhaps you don't like this, but I think, to have one variable less is clearer and easier to understand than having several variables refering to the next one. I enclose a small patch to this mail, which - fixes the config.h problem (to finally clearify misunderstands) - removes assignment/subsitution of RTEMS_ROOT from configure.in - contains a workaround for the application Makefile's RTEMS_ROOT problem (reported by Eric) - removes some unused lines from the toplevel Makefile.in - removes assignment of RTEMS_ROOT from make/target.cfg.in
* Added information about multilib problems.Joel Sherrill1998-01-231-0/+8
|
* Removed CONFIG_DIR and PROJECT_HOME directories.Joel Sherrill1998-01-2010-10/+10
|
* Updates from Eric Norum. Changed CPU CFLAG and went to a common nameJoel Sherrill1998-01-061-150/+112
| | | | for the network driver attach entry point.
* Fixes from Eric Norum. C++ support added in previous version was broken:Joel Sherrill1997-12-223-291/+272
| | | | | | | | | | | | | | | | | | 1) In my haste to add C++ constructor/destructors to the 68360 linkcmds scripts I managed to break all existing 68360 programs. Linker scripts which actually produce a working executable are contained below. The problem was that the constructor/destructors weren't included before the etext symbol. On top of that Eric and I appear to have problems with attachments: 2) In deciphering the above problem I think I stumbled across the reason you've had with patches mailed from me. I noticed that the linkcmds (and linkcmds.bootp) scripts in the latest distribution have a control-M (carriage return) at the end of each line. Could you check the files below before installing them in the distribution and see that there aren't returns in the files? Maybe if I send everything as a tar attatchment things will work better.
* Corrected prototypes for all termios console write driver entries toJoel Sherrill1997-12-221-2/+2
| | | | properly reflect the const on the buffer pointer being passed in.
* Moved -qnolinkcmds option so arguments passed on the command line areJoel Sherrill1997-12-201-2/+2
| | | | | | | | | | | | | | | | | | | | | interpreted at the right point per Eric Norum's discovery: The problem with the my previous `fix' for adding linker commands was with the ordering of the options to the linker. For example, to make a larger heap size, the application Makefile would CFLAGS_LD = -Wl,--defsym -Wl,HeapSize=0x40000 The command passed to the linker would be : m68k-rtems-ld .... -T xxx/linkcmds .... --defsym HeapSize=0x40000 ..... This doesn't work because the script in linkcmds inserts a default value for HeapSize if HeapSize is not defined by the time the linker looks at the linkcmds script. The solution seems to be to move the -T linkcmds%s in the bsp_specs file out of the link specfication and into the lib specification -- a little unorthodox, perhaps, but it seems to work!
* Update from Eric Norum to include C++ support.Joel Sherrill1997-12-203-239/+281
|
* Modified bsp_specs per Eric Norum's suggestion to handle -qnolinkcmdsJoel Sherrill1997-12-191-1/+1
| | | | switch which lets the user specify a different linker script.
* Modified a lot of files to take a first cut at supporting building fromJoel Sherrill1997-12-1010-10/+40
| | | | | any directory in the build tree. The only variable which must be set before the command "gmake" is invoked is RTEMS_BSP (e.g. RTEMS_BSP=erc32).
* Changed from DOS style CR/LF to Unix style.Joel Sherrill1997-11-181-534/+534
|
* interrupt driven change from Eric NorumJoel Sherrill1997-11-151-11/+43
|
* Removed GEN68360_INIT.Joel Sherrill1997-10-231-8/+0
|
* Update from Eric Norum.Joel Sherrill1997-10-231-161/+153
|
* New version of this file from Eric Norum.Joel Sherrill1997-10-131-536/+534
|
* Modified to search RTEMS library before Newlib C library.Joel Sherrill1997-10-081-1/+1
|
* Update from Eric Norum:Joel Sherrill1997-10-082-530/+540
| | | | | Change label names so they can be seen from the debugger. Provide a start symbol -- gets rid of a loader warning message.
* Fixed typo in the pointer to the license terms.Joel Sherrill1997-10-088-16/+16
|
* Removed include directory at "build" point and the link of this directoryJoel Sherrill1997-10-081-2/+2
| | | | | | to lib/include. Went to using a PROJECT_INCLUDE variable.