sptests/sp02: Fix maximum task count
rtems: Simplify rtems_task_mode()
score: Add _Chain_Insert_ordered_unprotected()
score: Add and use _Thread_Dispatch_is_enabled()

Delete _Thread_Dispatch_in_critical_section() and
_Thread_Is_dispatching_enabled().
score: Add and use _Thread_Dispatch_if_necessary()

Delete _Thread_Evaluate_is_dispatch_needed().

Use _Thread_Dispatch_is_enabled() in rtems_task_mode() instead of the
system state to determine if a thread dispatch is allowed.  Signales are
now delivered in rtems_task_mode() even if preemption is disabled.  This
is in line with rtems_signal_send().
score: Rename rtems_smp_get_number_of_processors()

Rename in rtems_smp_get_processor_count().  Always provide
<rtems/score/smp.h> and <rtems/rtems/smp.h>.  Add
_SMP_Get_processor_count().  This function will be a compile time
constant defined to be one on uni-processor configurations.  This allows
iterations over all processors without overhead on uni-processor
configurations.
score: Simplify _Thread_Create_idle()
scheduler: Add start idle thread operation

Add and use _Scheduler_Start_idle().
scheduler: Specify thread of yield operation

The yielding thread of the yield operation is now specified by a
parameter.  The tick operation may be performed for each executing
thread in a SMP configuration.
scheduler: Add and use _Scheduler_default_Tick()

Delete _Scheduler_priority_Tick().  Use _SMP_Get_processor_count() for
default tick operation.  Delete _Scheduler_simple_smp_Tick().
scheduler: Simplify simple scheduler

Add and use _Scheduler_simple_Insert_priority_fifo_order(),
_Scheduler_simple_Insert_priority_lifo_order(),
_Scheduler_simple_Insert_priority_fifo() and
_Scheduler_simple_Insert_priority_lifo().
scheduler: New simple SMP scheduler implementation

The new Simple SMP Scheduler allocates a processor for the processor
count highest priority ready threads.  The thread priority and position
in the ready chain are the only information to determine the scheduling
decision.  Threads with an allocated processor are in the scheduled
chain.  After initialization the scheduled chain has exactly processor
count nodes.  Each processor has exactly one allocated thread after
initialization.  All enqueue and extract operations may exchange threads
with the scheduled chain.  One thread will be added and another will be
removed.  The scheduled and ready chain is ordered according to the
thread priority order.  The chain insert operations are O(count of ready
threads), thus this scheduler is unsuitable for most real-time
applications.

The thread preempt mode will be ignored.
smptests/smpschedule01: New test
documentation: Fix Doxygen comments
bsps: Add missing include
bsps: Provide simple console selection
Revert "sptests/sp02: Fix maximum task count"

This reverts commit 6f8adb073b0c1b4d2a638f99710fda4e99938332.

The resource count was correct.
smptests/smpschedule01: Update due to API change
bsp/xilinx-zynq: Use second UART for console

This is in now line with the evaluation board.
Update from automake-1.13.3.