#4005: Remove RTEMS_MP_NOT_CONFIGURED error condition -----------------------------+------------------------------ Reporter: Sebastian Huber | Owner: Sebastian Huber Type: enhancement | Status: assigned Priority: normal | Milestone: 5.1 Component: rtems | Version: 5 Severity: normal | Resolution: Keywords: | Blocked By: Blocking: | -----------------------------+------------------------------
Comment (by Sebastian Huber <sebastian.huber@…>): In [changeset:"46c23871813618e7a16050068041b3d33551cd0d/rtems" 46c23871/rtems]: {{{ #!CommitTicketReference repository="rtems" revision="46c23871813618e7a16050068041b3d33551cd0d" rtems: Remove RTEMS_MP_NOT_CONFIGURED error Some objects can be created with a local or global scope in a multiprocessing network. In non-multiprocessing configurations setting the scope to local or global had no effect since such a system can be viewed as a multiprocessing network with just one node. One and all nodes is the same in such a network. However, if multiprocessing was configured, creation of a global object in a single node network resulted in an RTEMS_MP_NOT_CONFIGURED error. Remove this error condition for symmetry to the non-multiprocessing setup. This is in line with the task affinity behaviour in SMP systems. Update #4005. }}} -- Ticket URL: <http://devel.rtems.org/ticket/4005#comment:1> RTEMS Project <http://www.rtems.org/> RTEMS Project
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs