This configuration is not obsolete since it is still used for named
semaphores.
Update #3116.
---
c-user/configuring_a_system.rst | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system
Update #2674.
Close #3112.
Close #3113.
Close #3114.
Close #3115.
Close #3116.
---
cpukit/sapi/include/confdefs.h | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/cpukit/sapi/include/confdefs.h b/cpukit/sapi/include/confdefs.h
index 0abe450ec5..753c1d3
rtems_rfs_dir_read searches the directory inode's entries list starting
at the specified offset until an empty entry (last entry) is encountered. It
fills in a struct dirent with the name of the entry, length of the name, ino of
the entry, and the absolute offset of the entry in the parent director
The bitmap allocation accounting logic in rtems-rfs-bitmaps.c is flawed
around control->free. Specifically:
In rtems_rfs_bitmap_map_set():
control->free is only decremented when its corresponding search bit is
toggled. This is wrong and will miss on average 31/32 set updates.
In rtems_rfs_bitmap_
In rtems_rfs_bitmap_map_clear_all(), control->free is set to 'elements',
which is the number of elements in the bitmap. This is incorrect, as
control->free should contain the number of free bits, not elements.
This change fixes the logic and resets control->free to a correct value.
---
cpukit/lib
This change fixes https://devel.rtems.org/ticket/3089.
Briefly, rtems_rfs_group.c contains conflicting conversions between
block numbers and group number and bit offset pairs. This caused the
actual bit stored on the bitmask to be one bit displaced from its
intended location.
For more details, pl
On Tue, Oct 10, 2017 at 12:43 AM, Sebastian Huber wrote:
> index 6a3b625..26ab28d 100644
> --- a/cpukit/posix/src/pthreadattrcompare.c
> +++ b/cpukit/posix/src/pthreadattrcompare.c
> @@ -32,7 +32,10 @@ int rtems_pthread_attribute_compare(
>if ( attr1->is_initialized != attr2->is_initialized
I am glad you asked about this. I have remembered to bring this up
every time I am not in a position to send email.
Yes. We should add warnings for them. Anything we can do to help users
correctly configure a system.
Are there warnings for the old BDBUF ones?
On Tue, Oct 10, 2017 at 12:52 AM, Se
Use Processor_mask instead.
Update #2514.
---
cpukit/posix/src/pthread.c | 1 -
cpukit/posix/src/pthreadsetaffinitynp.c| 1 -
cpukit/rtems/src/schedulergetprocessorset.c| 1 -
cpukit/rtems/src/taskgetaffinity.c | 1 -
cpukit/rtem
Update #2514.
---
cpukit/posix/src/pthreadcreate.c | 9 ++---
cpukit/score/src/schedulerpriorityaffinitysmp.c | 19 ---
testsuites/smptests/smppsxaffinity02/init.c | 6 +++---
.../smptests/smppsxaffinity02/smppsxaffinity02.scn| 8
---
cpukit/posix/include/rtems/posix/muteximpl.h | 8 ++--
cpukit/posix/src/pthreadsetschedparam.c | 4 +---
cpukit/posix/src/pthreadsetschedprio.c | 4 +---
cpukit/rtems/src/semsetpriority.c| 4 +---
cpukit/rtems/src/taskdelete.c|
Hello,
the registration deadline is close:
we are planning an open RTEMS class "RTEMS Application Development" in
Munich/Germany to start on
November 27th, 2017.
This class has is main focus on application development based on the
RTEMS kernel.
Maybe you or some of your colleag
12 matches
Mail list logo