mdnie: Switchable sharpness fix (V2)

credits to Hardcore for mdnie tables
mdnie: Switchable sharness fix

- replaced Boeffla-Kernel with MDNIE-PRESET generic dmesg entries
- fixed sysfs show printout
mdnie: black crush fix (XXUGMK6)

credits to AndreiLux
ported to Samsung 4.3 Android XXUGMK6 firmware by andip71
Yank555.lu v4.1a config
Revert "mmc: Enable support for Triangle Away"

This reverts commit 2bc7af06b046457a43b61b53f6a2ce776bb2c8d1.
Revert "mdnie: Switchable sharness fix"

This reverts commit 6a565f1ee782e90bd81c654d0664cc1a05c8951b.
Revert "mdnie: black crush fix (XXUGMK6)"

This reverts commit 5228a0f23d9380da67a5faca28c7a3785c94a880.
Revert "mdnie: Switchable sharpness fix (V2)"

This reverts commit 85c2fc4a48a7ecf8d74cf3038b1eb70a33ca810b.
mdnie : mdnie mode hijack (Yank555.lu)

 * SysFs interface :
 *
 * /sys/class/mdnie/mdnie/hijack : 0 = disbaled / 1 = enabled
 *
 *    Enable / Disable hijacking of mdnie settings (default = disabled)
 *
 * /sys/class/mdnie/mdnie/sharpen : 0 = disbaled / 1 = enabled
 *
 *    Enable / Disable screen sharpness (default = enabled, stock Samsung Update 12+)
 *
 * /sys/class/mdnie/mdnie/black : -128 to +128
 *
 *    Global black level, will shift black RGB setting by this value (default = 0)
 *
 *    NB: Effectively applied values for black will never be below 0 nor above 255 !
 *
 *        So there is no use setting Black RGB to (0,0,0) and this to -10, the result
 *        will still be (0,0,0).
 *
 * /sys/class/mdnie/mdnie/{color}_red   : 0 to 255
 * /sys/class/mdnie/mdnie/{color}_green : 0 to 255
 * /sys/class/mdnie/mdnie/{color}_blue  : 0 to 255
 *
 *    Allows to set the RGB values for the base colors :
 *
 *      - red
 *      - green
 *      - blue
 *      - cyan
 *      - magenta
 *      - yellow
 *      - black
 *      - white
 *
 *    (default = Samsung's natural mode)
ramfs: update mini busybox
cifs: enable mounting cifs drives visible to all apps (tomkasick)

Restrict slave mountspace so Dalvik apps can mount system-wide volumes

Android 4.2 implements multi-user storage using per-process mount
namespaces. Everything under "/" (the entire filesystem hierarchy) is
marked as a recursive-slave mountspace for all zygote instances. This is
done so that user-storage sandbox mounts under /storage/emulated are hidden
from other apps and users.

Unfortunately this means that any Dalvik app (actually, any program whose
clone/fork ancestry includes a Dalvik zygote, which is everything except
services spawned directly from init) cannot mount system-wide volumes.
Thus, apps like CifsManager are effectively broken in Android 4.2, since
its cifs mounts are only visible to the CifsManager app itself. All other
apps see empty mountpoints instead of the mounted volume. Furthermore,
Linux provides no provision for a process to "escape" a recursive-slave
mountspace in versions prior to Linux 3.8 (setns syscall).

Here, we restrict rootfs-slave calls to /storage (and, due to a possible
kernel bug, /mnt/shell/emulated) so that Dalvik apps can mount system-wide
volumes elsewhere (with appropriate permission, as in earlier versions of
Android), while retaining full multi-user storage compatibility. It is
made available as a kernel-based workaround for instances where libdvm can
not be modified.

This change requires that a tmpfs volume is mounted as /storage in init.rc.
If this volume is unavailable, then we falls back to the previous behavior
of marking the entire filesystem hierarchy as slave.

*** Do not commit to CyanogenMod Project kernels, as a similar workaround
for this problem is patched in Zygote/Dalvik/libdvm instead. ***
ramfs: Include mount point to enable CIFS mounts to be visible to all apps
Boeffla-Sound: Engine 1.6.5 (AndiP71)

- allow speaker minimum level of 20
ramfs : update to latest ML4