Timeline



02/01/20:

14:42 Changeset in rtems [9e4f21b9]5 by Sebastian Huber <sebastian.huber@…>
score: Optimize per-processor data placement Only align per-processor data in SMP configurations.
14:03 Ticket #3800 (termios - Add Capability to Generate SIGINTR and SIGQUIT) reopened by Sebastian Huber
The implementation breaks the canonical input mode as shown by test case termios09.

01/30/20:

20:05 Changeset in rtems [265c2e6]5 by Mateusz Guzik <mjg@…>
Remove duplicated empty lines from kern/*.c No functional changes.
20:05 Changeset in rtems [ae5b0b2] by Mateusz Guzik <mjg@…>
Remove duplicated empty lines from kern/*.c No functional changes.

01/29/20:

23:59 Ticket #3859 (No output from joel scripts in telnet) created by Chris Johns
Running a joel script in a telnet session results in the output …
21:56 Ticket #3858 (PC386 BSP serial console outputs garbage on real hardware) created by Lou Woods
= Problem description When the RTEMS ticker test, possibly others, is …
08:32 Changeset in rtems [90f11edd]5 by Sebastian Huber <sebastian.huber@…>
termios: Fix input canonical mode Canonical input processing was broken by 667501a314ba75f80f1c13c6b43dd35d0a00efd1 as shown by test case termios09. Update #3800.

01/28/20:

14:03 Changeset in rtems [b4387313]5 by Sebastian Huber <sebastian.huber@…>
psxmsgq03: Adjust test case Commit e22554535796fc29a7ed7c5e2338128e324a621d changed the error status from ENOMEM to EAGAIN. Update #3857.
13:38 Changeset in rtems [e7a7e6c]5 by Sebastian Huber <sebastian.huber@…>
smptests/smpmulticast01: Fix test configuration Problem introduced by 77ac1519e863b7095f69c976353f7647c6f6f63b.
12:44 Changeset in rtems [754f78fa]5 by Sebastian Huber <sebastian.huber@…>
libtest: Fix T_check_task_context() Fix T_check_task_context() in RTEMS_SMP with RTEMS_DEBUG configurations.

01/25/20:

17:14 Changeset in rtems-docs [5763454]5 by G S Niteesh <gsnb.gn@…>
doc/raspberrypi: Added instructions for raspberrypi Added instructions to run examples on raspberrypi.

01/24/20:

14:49 Ticket #3857 (Use EAGAIN for POSIX mq wait in ISR error) closed by Martin Erik Werner <martinerikwerner@…>
fixed: In e225545/rtems: […]
13:59 Changeset in rtems-docs [565df31]5 by Joel Sherrill <joel@…>
posix-users/message_passing.rst: Add status for cannot block in ISR Updates #3857.
13:59 Ticket #3857 (Use EAGAIN for POSIX mq wait in ISR error) created by Joel Sherrill
POSIX message queues which are about to block in an ISR currently …
09:57 Changeset in rtems-tools [18d3daa]5 by Vijay Kumar Banerjee <vijaykumar9597@…>
covoar/wscript: Install covoar.css and table.js
09:57 Changeset in rtems-tools [2852cac]5 by Vijay Kumar Banerjee <vijaykumar9597@…>
rtemstoolkit/path: Add support to copy single file

01/21/20:

03:46 Changeset in rtems-source-builder [599c4d7]5 by Chris Johns <chrisj@…>
freebsd: Fix GDB building on some 12 and higher versions

01/20/20:

04:12 Ticket #3691 (RTEMS Testing TFTP Proxy Project) closed by Chris Johns
fixed: A Python command has been added to RTEMS Tools ... ​https://git.rtems.org/rtems-tools/tree/misc/rtems-tftp-proxy

01/19/20:

15:11 Changeset in rtems [e2255453]5 by Martin Erik Werner <martinerikwerner@…>
Use EAGAIN for POSIX mq wait in ISR error Modify the status code returned by _CORE_message_queue_Submit() when it detects a wait about to happen in an ISR (which would be deadly) to return a status which translated to EAGAIN instead of ENOMEM. This is only relevant for POSIX message queues, since Classic API message queues cannot block on send. The motivation is to match the "most related" errno value returned from mq_send() and mq_timedsend() according to POSIX, via Open Group: [EAGAIN] The O_NONBLOCK flag is set in the message queue description associated with mqdes, and the specified message queue is full. or via the RTEMS POSIX users documentation EAGAIN The message queue is non-blocking, and there is no room on the queue for another message as specified by the mq_maxmsg. Neither of these matches the case ofi avoided ISR wait perfectly, but they seem to be the closest equivalent, unless it is desirable to keep a new non-standard error for this case. It is presumed that this is not desirable. The previously returned ENOMEM error value is not documented in either the Open Group or the RTEMS POSIX uses documentation. A companion patch corrects the documentation to include this error condition. Based on the discussion in: ​https://lists.rtems.org/pipermail/devel/2020-January/056891.html closes #3857. Message-Id: <CAF9ehCW5P12ZkZja4UPYTbdBFUyC1VKVL-tU7nyUtvK1Lz2Z3g@…>
Note: See TracTimeline for information about the timeline view.