| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
by Jiri Gaisler <jgais@ws.estec.esa.nl> when using this
driver on a SPARC.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> 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).
|
|
|
|
|
|
| |
portion is now in the libchip tree and the dmv177 configuration is in
the dmv177 bsp. The performance impact of libchip'ing this driver
was minimal.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
overhaul of the RTEMS system call interface. This base file system is
the "In-Memory File System" aka IMFS.
The design and implementation was done by the following people:
+ Joel Sherrill (joel@OARcorp.com)
+ Jennifer Averett (jennifer@OARcorp.com)
+ Steve "Mr Mount" Salitasc (salitasc@OARcorp.com)
+ Kerwin Wade (wade@OARcorp.com)
PROBLEMS
========
+ It is VERY likely that merging this will break the UNIX port. This
can/will be fixed.
+ There is likely some reentrancy/mutual exclusion needed.
+ Eventually, there should be a "mini-IMFS" description table to
eliminate links, symlinks, etc to save memory. All you need to
have "classic RTEMS" functionality is technically directories
and device IO. All the rest could be left out to save memory.
|
|
|
|
| |
with libchip.
|
|
|
|
| |
of the SONIC driver to the new FreeBSD stack instead of KA9Q.
|
|
|
|
| |
Fixed a comment.
|
|
|
|
|
| |
busy. This type of behavior perturbs the tests and many of them will
not pass.
|
| |
|
| |
|
|
|
|
|
| |
Corrected prototypes to reflect unsigned32 values being passed around
instead of unsigned8's.
|
|
|
|
| |
Renamed port table.
|
| |
|
|
|
|
|
|
| |
Set time->ticks to 0.
Added function table.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
version compiles cleanly but there is not a BSP with a configuration
table to utilize it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and manage the interrupt sources like the other drivers. This
let use remove the ns16550_flush() routine.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Reworked transmit interrupt processing to remove ring buffer and
to mask the TX empty interrupt when it was not expected. This code
now uses termios to buffer TX output.
|
| |
|
| |
|
|
|
|
| |
rather than doing repeated table lookups.
|
| |
|
|
|
|
| |
and to correctly set the TX active indicator.
|
|
|
|
| |
than with a disable/enable pair.
|
|
|
|
| |
Move some code around.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|