| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added support for bsd "install" ($(BSDINSTALL)) to host.cfg.in, i.e.
the standard "install" program that most packages (including automake)
use. In Makefiles outside of rtems, "install" normally is referenced by
$(INSTALL), but rtems already uses $(INSTALL) for install-if-change,
hence I used $(BSDINSTALL) instead to keep up backward compatibility.
* Removed references to @GREP@ etc. from host.cfg.in, as configure.in
doesn't check for them (Minor cleanup).
* Added installation flags INST*FLAGS to host.cfg.in, which should
replace -m XXXX flags for installation calls.
*Changes to gcc.cfg to enable it to build host programs from multiple
sources files.
Should not disturb existing sources, but neccessary.
* There was a not-so-minor bug in the configuration files: "make
install" and "make debug_install" don't work in all subdirectories!! I
tried to fix this by adding "install" to MTARGETS in main.cfg, which
seems to solve most of the problems. But there still seem to be rare (?)
cases where "make debug_install" still seems to have problems.
* Changes to many host related tool-Makefiles to demonstrate the
abilities of INST*FLAGS, BSDINSTALL and the new rules in gcc.cfg.
..of cause ... but BSDINSTALL is THE standard method to install files
in most program packages besides rtems. This part of the patch fixes
some minor protection setting problems, but doesn't support
TARGET_VARIANTS
NOTE:
I hope you will like the BSDINSTALL, INST*FLAGS stuff. It is a step to
get rid of "install-if-change" and to rely on a more standard
installation procedure. If you don't like BSDINSTALL, removing it from
the patch isn't difficult- just grep for BSDINSTALL and replace
BSDINSTALL with INSTALL or MKDIR.
FINALLY:
I still have another patch pending (well, not a complete patch yet, it's
a partial patch to demonstrate the principle), which adds automatic
rebuilding of files generated by autoconf/configure. At the moment I
don't dare to submit it, because integrating this patch would require to
modify all Makefile.ins because we'd need to add a new "include " line
to each Makefile.in.
|
| |
|
| |
|
|
|
|
|
| |
* c/src/lib/libbsp/sh/gensh1/scitab - NEW DIRECTORY
Location for building the table generated by shgen
|
|
|
|
|
|
|
|
|
|
|
| |
* c/src/exec/score/tools/sh - NEW DIRECTORY - contains shgen
Most of it should be self-explanatory. I am a little bit concerned about
host-dependent features (getopt, floating point libraries). This
shouldn't disturb much now, as this tool should be compileable on all
gnu-based hosts and is only applicable for the sh. But in case somebody
complains, we may need to add autoconf checks or even restructurize
parts of rtems (IMO, rtems needs to be restructurized - remember the
"turning rtems upside down" issue).
|
|
|
|
|
|
|
|
|
| |
Haven't had a chance to do an extensive shake-out of 980710, but it
builds just fine on FreeBSD 2.2.5 (after termios is fixed using the
attached patch), and the tests run fine. FYI: FreeBSD doesn't support
System V IPC out of the box, but one only needs to add three options
to the kernel build configuration file, recompile the kernel, and
you're ready.
|
| |
|
| |
|
|
|
|
|
|
| |
size of the minimum mc68681 driver. The clock speed field can not
now be configured as NULL but must instead specify the address of
the default table.
|
|
|
|
| |
register access routines.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Added prototype for mc68681_build_imr(), mc68681_process(), and
mc68681_enable_interrupts().
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the need for the ringbuffer manipulation in this driver. It should
also allow the removal of mc68681_flush. This greatly simplified the
interrupt processing.
Reworked Interrupt Mask Register handling. Added imr field to the device
context. This handling makes sure that the IMR accurately reflects the
state of the port in use and its mate. This required the reworking of
the mc68681_enable_interrupts() routine to allow for the specification
of which interrupt sources were being enabled/disabled.
Reworked initialization to reset using port address rather than chip
base address. Basically we were always resetting port 0.
Added deviceType field which allows for multiple chips of the same
class to have the same vector number.
|
| |
|
| |
|
|
|
|
| |
Added proper headers to routines.
|
| |
|
|
|
|
| |
interrupt vector can be shared by multiple chips of varying types.
|
|
|
|
| |
The scheme used in the mc68681 is the one to follow.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
compilation section which used CONSOLE_USE_INTERRUPTS to switch all
ports between interrupt and polled mode.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
driven.
Redid "mate determination" code to check that the chip base address was
the same but the port address was different.
Moved mc68681_process and mc68681_build_imr to the bottom of the file
so they would not be inlined.
Removed the code which forced mc68681_build_imr to always return 0 which
resulted in interrupts never being enabled from the chip.
Corrected spacing in prototype of mc68681_write_support_int.
|
| |
|
|
|
|
|
|
|
|
| |
<corsepiu@faw.uni-ulm.de> and his comments are below:
Joel, obviously you did apply my previous patch to
gcc-target-default.cfg -- This should have been gcc.cfg
(gcc-target-default.cfg should NOT contain any EXEEXT).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
c/src/lib/libbsp/i386/pc386/console/console.c
__assert() modified so it prints on selected console instead of
PC console
c/src/lib/libbsp/i386/pc386/console/inch.c
inch_sleep() modified, so it does not depend upon tmacros.h
c/src/lib/libbsp/i386/pc386/pc386dev/GDB.HOWTO
description updated
c/src/lib/libbsp/i386/pc386/startup/exit.c
last output before call to exit() will be printed properly on
serial console
c/src/lib/libbsp/i386/pc386/startup/irq.c
re-submitted bug fix for problem in irqs over 7.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> It seems that rules for %{EXEEXT} don't exist in gcc-target-default.cfg
No, gcc-target-default.cfg is used to compile executables for the target
only, not for the host.
EXEEXT may only be used for programs to be run on the host.
> What should I add please?
This was a bug in my initial configuration patch to rtems-980616. A
correction to this patch I had sent to Joel at 26.06.98 doesn't seem to
have made it into the snapshot.
Please find attached the patch I had sent to Joel, hopefully this patch
fixes this problem.
|
|
|
|
| |
Switched to shared default probe.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Renamed sersupp.c so we could have one routine per file to decrease
the baggage pulled into an application by default.
|
|
|
|
| |
with this ROM monitor.
|
| |
|
|
|
|
| |
Still need to address default terminal settings.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Temporarily "if 0" of code which enables interrupts.
Moved setting of command registers at open but the current implementation
is questionable.
Added reset of RX errors while polling TX.
Read polled character as unsigned.
Baud rate mask must be in upper and lower nibble.
|