3.4.81

Change-Id: Ib374ce3b28766f99ce9d91f250b9a5f645f244b0
3.4.82

Change-Id: I8567dbea63a1da2660c488c7a5e414eaf6ad6427
Signed-off-by: LaboDJ <jacopolabardi@gmail.com>
3.4.83

Change-Id: Ieea0e45476e53e7317596339c9fcbaa3d9b77b6b
3.4.84

Change-Id: I3693797bbfad684b0edaab2b2917e3befc9c6576
3.4.85

Change-Id: I10fdfd67cdc5c698126bc62db86921cb1efda154
3.4.86

Change-Id: Id20ec3ab89b55aecde8a9b5a64a585f3b4da7a4a
Makefile: remove the damn wrapper.

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Change-Id: I130a10d20715c9c03baa42a44cc9b7369dab67e0
ARM: add support for kernel mode NEON

In order to safely support the use of NEON instructions in
kernel mode, some precautions need to be taken:
- the userland context that may be present in the registers (even
  if the NEON/VFP is currently disabled) must be stored under the
  correct task (which may not be 'current' in the UP case),
- to avoid having to keep track of additional vfpstates for the
  kernel side, disallow the use of NEON in interrupt context
  and run with preemption disabled,
- after use, re-enable preemption and re-enable the lazy restore
  machinery by disabling the NEON/VFP unit.

This patch adds the functions kernel_neon_begin() and
kernel_neon_end() which take care of the above. It also adds
the Kconfig symbol KERNEL_MODE_NEON to enable it.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Paul Reioux <reioux@gmail.com>
Change-Id: If1f05d3201b6c285805ba2197d9f2f66294eba23
ARM: be strict about FP exceptions in kernel mode

The support code in vfp_support_entry does not care whether the
exception that caused it to be invoked occurred in kernel mode or
in user mode. However, neither condition that could trigger this
exception (lazy restore and VFP bounce to support code) is
currently allowable in kernel mode.

In either case, print a message describing the condition before
letting the undefined instruction handler run its course and trigger
an oops.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel at linaro.org>
Acked-by: Nicolas Pitre <nico at linaro.org>
Signed-off-by: Paul Reioux <reioux@gmail.com>
Change-Id: I71ae88e09e1cc116e3691db31d098a847318dd04
bitmap: compile with -Os

Change-Id: I335a1eb92cfc0b17f85b3a53f120cc407a0f293a
Add /dev/frandom

Change-Id: Iafb73f05e895fc73308411d0bd3174d718a03ce9
lib/memcopy: use glibc version

the kernel's memcpy and memmove is very inefficient. But the glibc version is
quite fast, in some cases it is 10 times faster than the kernel version. So I
introduce some memory copy macros and functions of the glibc to improve the
kernel version's performance.

The strategy of the memory functions is:
1. Copy bytes until the destination pointer is aligned.
2. Copy words in unrolled loops.  If the source and destination are not
   aligned in the same way, use word memory operations, but shift and merge
   two read words before writing.
3. Copy the few remaining bytes.

Signed-off-by: Miao Xie <miaox*******>
Signed-off-by: faux123 <reioux@gmail.com>
Change-Id: I9b323e512a90175fec7d61f48f272c4f47671955
lib/string: use glibc version

the performance of memcpy and memmove of the general version is very
inefficient, this patch improved them.

Signed-off-by: Miao Xie <miaox*******>
Signed-off-by: faux123 <reioux@gmail.com>
Change-Id: I470e001aa75ca672016c822f88d672afad1a0f75
kernel: Allow exfat module load without hassle

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Change-Id: I354b6dd60e762209774e651b228591c29a9788c4