lxfb: properly alloc cmap in all cases and don't leak the memory
lxfb: properly alloc cmap in all cases and don't leak the memory

We weren't properly allocating the cmap for depths greater than 8bpp,
which caused pain for things like DirectFB.  Also, we never freed the cmap
memory upon module unload..

[3945bcf5fa0c9ecb9066fe0f9d287073618c06cc@debian.org: dropped unnecessary code and clean up patch]
[3945bcf5fa0c9ecb9066fe0f9d287073618c06cc@debian.org: add error checking and handling]
Signed-off-by: Andres Salomon <3945bcf5fa0c9ecb9066fe0f9d287073618c06cc@debian.org>
Cc: Jordan Crouse <1cb5bd5a9e45420321f44c72da5d90d7f0432ffb@cosmicpenguin.net>
Signed-off-by: Andrew Morton <5c1e68b099950c134891f0b6e179498a8ebe9cf9@linux-foundation.org>
Signed-off-by: Linus Torvalds <69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org>

KristFoundation/Programs,TeamVee-Kanas/android_kernel_samsung_kanas,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,TeamVee-Kanas/android_kernel_samsung_kanas,KristFoundation/Programs,TeamVee-Kanas/android_kernel_samsung_kanas,TeamVee-Kanas/android_kernel_samsung_kanas,KristFoundation/Programs,TeamVee-Kanas/android_kernel_samsung_kanas