According to the ALSA documentation, snd_pcm_readi() returns -ESTRPIPE
when a suspend event occured. But xrun_recovery() checks for -EAGAIN
instead.

If the ALSA client is connected to the ALSA loopback device, it leads to
an infinite loop in the client when the computer is resumed from sleep.
The client takes up to 99% of the CPU resources.

The problem is fixed by a proper error checking of snd_pcm_readi().

A word of caution however: on kernels prior to 3.8, it will trigger a
bug in the snd-aloop driver, and may lead to a kernel oops.
The kernel fix can be found there:
http://www.spinics.net/lists/stable-commits/msg23379.html

Signed-off-by: elboulangero <elboulangero@gmail.com>

Add aarch64 (64-bit arm) compile support

Conflicts:
	common/JackEngine.cpp
	common/JackServer.cpp

rd_acquire() is going to assert (or fail) anyway because connection will be NULL.

Patch by colinf via

   http://trac.jackaudio.org/attachment/ticket/227/typos.patch

Some python implementations report "linux3" on newer kernels. Of course,
we'll have to set IS_LINUX for those, too.

When compiling jack on aarch64, compilation fails because NGREGS is not
defined. Since this is only for debug output on segmentation faults, stub
the debug print out like it's been done for other platforms before.

Signed-off-by: Alexander Graf <agraf@suse.de>

( Added few lines to implement it, transition to
  JackMidiRawInputWriteQueue might be a better solution though )