| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Ensure that the C++17 aligned new operator works.
Close #3666.
|
|
|
|
|
|
|
|
|
|
|
| |
Fix for:
- tftpfs did not mount, when device field in mount entry is empty
- tftpfs needs to allocate fs structure before it fills it (avoid use of
uninitialized pointer)
- tftpfs needs to skip initial slash before hostname
|
|
|
|
|
|
|
|
|
|
|
| |
Allocate the per-CPU data for secondary processors directly from the
heap areas before heap initialization and not via
_Workspace_Allocate_aligned(). This avoids dependency on the workspace
allocator. It fixes also a problem on some platforms (e.g. QorIQ) where
at this early point in the system initialization the top of the RAM is
used by low-level startup code on secondary processors (boot pages).
Update #3507.
|
|
|
|
|
|
|
| |
This configuration option was undocumented and not really helpful. To
debug issues in <rtems/confdefs.h> it is better to save the
preprocessesd file (GCC "-save-temps" option) and use the GCC "-Wp,-dD"
pre-processor option.
|
|
|
|
| |
Update #3254.
|
|
|
|
|
|
|
|
|
|
|
| |
Statically allocate the objects information together with the initial
set of objects either via <rtems/confdefs.h>. Provide default object
informations with zero objects via librtemscpu.a. This greatly
simplifies the workspace size estimate. RTEMS applications which do not
use the unlimited objects option are easier to debug since all objects
reside now in statically allocated objects of the right types.
Close #3621.
|
|
|
|
|
|
|
| |
Use functions instead of macros. Add missing
rtems_configuration_get_maximum_*() functions.
Update #3621.
|
|
|
|
|
|
|
| |
Use Objects_Information::objects_per_block to provide this information.
Add and use _Objects_Is_auto_extend().
Update #3621.
|
|
|
|
| |
This function is untested.
|
|
|
|
|
|
|
| |
Remove Objects_Information::the_class. This information is already
contained in Objects_Information::maximum_id.
Update #3621.
|
|
|
|
|
|
|
| |
This information is already present in Objects_Information::maximum_id.
Add and use _Objects_Get_maximum_index().
Update #3621.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the maximum ID for the ID to object translation. Using the maximum
ID gets rid of an additional load from the object information in
_Objects_Get(). In addition, object lookups fail for every ID in case
the object information is cleared to zero. This makes it a bit more
robust during system startup (see new tests in spconfig02).
The local table no longer needs a NULL pointer entry at array index
zero. Adjust all the object iteration loops accordingly.
Remove Objects_Information::minimum_id since it contains only redundant
information. Add _Objects_Get_minimum_id() to get the minimum ID.
Update #3621.
|
|
|
|
|
|
|
|
| |
Rename Objects_Information::allocation_size in
Objects_Information::objects_per_block. Adjust integer types in
_Objects_Shrink_information() and _Objects_Free().
Update #3621.
|
|
|
|
|
|
|
|
| |
Rename Objects_Information::size to Objects_Information::object_size.
Change its type from size_t to uint16_t and move it to reduce the size
of Objects_Information.
Update #3621.
|
|
|
|
|
|
| |
Use Objects_Information::name_length to store this information.
Update #3621.
|
|
|
|
| |
Update #3621.
|
|
|
|
| |
Update #3636.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to simplify the use of CPU counter values it is beneficial to
have monotonic increasing values within the range of the CPU counter
ticks data type, e.g. 32-bit unsigned integer. This eases the use of
CPU counter timestamps in external tools which do not know the details
of the CPU counter hardware. The CPU counter is the fastest way to get
a time on an RTEMS system.
Such a CPU counter may be also used as the timecounter. Use it on SPARC
for this purpose to simplify the clock drivers.
Update #3456.
|
|
|
|
|
|
|
|
|
|
| |
The sbintime_t is a non-POSIX type and not visible if strict standard
options are selected.
Move implementation details from <rtems/score/timestamp.h> to
<rtems/score/timestampimpl.h>.
Update #3598.
|
|
|
|
|
| |
Enable the use of RTEMS_DEVOLATILE() and RTEMS_DECONST() in strict ISO C
environments.
|
|
|
|
| |
Close #3637.
|
| |
|
| |
|
|
|
|
|
| |
The sbintime_t is an efficient time format. Add the ability to convert
CPU counter ticks to/from sbintime_t.
|
|
|
|
| |
Username: deuteriumoxide Email: jacobshin313@gmail.com
|
|
|
|
| |
Update #3358.
|
|
|
|
|
|
|
|
| |
The following rtems_cache_*_processor_set() cache manager API functions
are exotic, complex, very hard to use correctly, not used in the RTEMS
code base, and apparently unused by applications.
Close #3622.
|
| |
|
|
|
|
|
|
|
| |
Remove <rtems/score/chainimpl.h> include from
<rtems/score/smplockstats.h>.
Close #3598.
|
|
|
|
|
|
|
| |
Move Heap_Information_block to separate header file to hide heap
implementation details from <rtems.h>.
Update #3598.
|
|
|
|
| |
Closes #3581.
|
|
|
|
|
|
|
|
|
|
| |
Tracking references lets us manage when an object file can be
unloaded. If an object file has references to it, it cannot be
unloaded.
Modules that depend on each other cannot be unloaded.
Updates #3605
|
|
|
|
| |
Updates #3194
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The use of separate text and data results in uninitialised variables
being placed in the common section. There is no section in ELF for
the common variables so the loader needs to create the section and
allocate the variables in that section. This patch does that.
The patch adds a second pass over the symbols.
The issue can also be seen as a section 65522 error.
Updates #3604
|
| |
|
|
|
|
|
|
|
|
|
| |
The RTEMS_USE_16_BIT_OBJECT define is not set by an RTEMS port. Remove
support for 16-bit object identifiers. If someone really wants to use
RTEMS on a 16-bit target, then it is better to use self-contained
objects instead of playing around with object identifier optimizations.
Update #3603.
|
| |
|
|
|
|
| |
Update #3598.
|
|
|
|
| |
Close #3602.
|
|
|
|
| |
Close #3583.
|
|
|
|
| |
Update #3583.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|
|
|
|
| |
Update #3585.
|