| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
included and we ended up with undefined references.
|
|
|
|
| |
and _POSIX_signals_Set_process_signals was done twice.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> 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).
|
| |
|
| |
|
|
|
|
| |
<jzamora@avellano.datsi.fi.upm.es>.
|
|
|
|
|
| |
object code that has to be loaded just for initializing the signal
manager.
|
|
|
|
| |
and eliminate a link error.
|
| |
|
|
|
|
| |
split into multiple files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
it work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Socket timeout field changed from `short' to `long'. This makes longer
timeouts possible. With a 1 kHz system clock the old system allowed
timeouts only up to a little over 30 seconds! This change is a
slightly cleaned-up version of the patch proposed by Ian Lance Taylor.
2) Major changes to BOOTP/DHCP reply handling. Now supports much of
RFC2132. These changes were done at the request of, and with the
assistance of, Erik Ivanenko.
If you're making changes, you might want to change the network
supplement Essentially just do a global search and replace of BOOTP
with BOOTP/DHCP.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
task to be deleted was created via the same API (i.e. were of the object
class created by this API). For example, a POSIX thread calling
the rtems_task_delete(SELF) directive would incorrectly update the RTEMS
object local pointer table.
Jennifer discovered this when moving tests implemented in C using the
Classic RTEMS API into a tree of Ada tests. The Ada tests were implicitly
using POSIX services. This lead to some unexpected behavior.
|
|
|
|
| |
so confdefs.h could see it.
|
|
|
|
|
|
|
| |
the system signals.h file.
Moved POSIX_signals_Siginfo_node type definition to this file to allow
confdefs.h to know the size per queued signal.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
it is arbitrarily assumed to be 1 clock tick.
|
| |
|
| |
|
|
|
|
| |
Ada interface where entry is a keyword.
|
|
|
|
| |
of switching to the modified GNU GPL.
|
|
|
|
|
| |
of lowest priority with the RTEMS IDLE thread. This was causing the lowest
priority GNAT Ada task to never run.
|
|
|
|
|
| |
cxe1001 of the ACVC 2.0.1. This allows gnat/rtems to pass the partition
tests.
|
| |
|
|
|
|
|
|
|
|
|
| |
argument indicates whether the task is to be placed at the head or tail of
its priority fifo when it is lowering its own priority. POSIX normally
follows the RTEMS API conventions but GNAT expects that all lowering of
a task's priority by the task itself will result in being placed at the
head of the priority FIFO. Normally, this would only occur as the result
of lose of inherited priority.
|
|
|
|
| |
get replaced as required.
|
|
|
|
| |
no one will ever get confused here again and try to enable dispatching. :(
|
| |
|
|
|
|
| |
stack size so more of acvc would pass.
|
| |
|
|
|
|
|
|
| |
to made signals sent to a particular thread from an ISR operated correctly.
This behavior was required by the exception detection/reporting code
in the gnat runtime.
|
|
|
|
|
|
|
|
| |
the timeout is given as a wall-time not an interval as was previously
implemented. Second, the interpretation of ETIMEDOUT behavior was
incorrect as all possible error cases needed to be checked before
this error was returned. This caused problems when the wall-time
specified was in the past.
|
| |
|
|
|
|
| |
visible to other files.
|
| |
|
|
|
|
| |
visible to other files.
|
|
|
|
|
|
|
|
|
|
|
|
| |
explicit to inherit scheduler to be consistent with FSU pthreads for gnat.
_POSIX_Threads_Create_extension: now inherit signal blocked mask from
creator if the new thread is a posix thread.
_POSIX_Threads_Initialize_user_threads: make sure posix initialization
threads start with a useful priority. If they inherit the priority
of the creating thread, they will end up at the same priority as the
idle thread. Since the idle thread does not yield, they will not run.
|
|
|
|
| |
not converted from core priority to posix priority.
|
|
|
|
| |
is changed into being a 0 delay.
|
|
|
|
|
| |
currently the only routine in this file simply returns the minimum stack
size for each thread.
|
| |
|
|
|
|
|
| |
later pthread_mutex_lock. This makes our behavior more compatible
with that of FSU pthreads.
|
| |
|