[General Questions and Answers] :
I used B194 firmware boot.img. The trick here is to unpack boot.img using dtbtools. I'm not absolutely certain, but i think I used this code to unpack boot.

From kernel source code you are going to need this files too: msm_ion.h and msm_mdp.h

Take a look at this thread by crazytiti. You are just going to need it.

||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| EDIT|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

This is the BoardConfig.mk I used to build the CWM recovery.img

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/huawei/y530/BoardConfigVendor.mk

TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM_GPU := qcom-adreno302
TARGET_BOARD_PLATFORM := unknown
TARGET_ARCH := arm
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_SMP := true
TARGET_CPU_VARIANT := cortex-a7
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := y530

TARGET_GLOBAL_CFLAGS += -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS += -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=softfp
BOARD_KERNEL_SEPARATED_DT := true
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02000000 --tags_offset 0x01e00000 --dt device/huawei/y530/dt.img
# Graphics
TARGET_QCOM_DISPLAY_VARIANT := caf-new
#BOARD_EGL_CFG := device/zte/kis3/prebuilt/system/lib/egl/egl.cfg
USE_OPENGL_RENDERER := true
TARGET_USES_ION := true
NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3
OVERRIDE_RS_DRIVER := libRSDriver_adreno.so
MAX_EGL_CACHE_KEY_SIZE := 12*1024
MAX_EGL_CACHE_SIZE := 2048*1024

# PHilz touch
TARGET_SCREEN_HEIGHT := 854
TARGET_SCREEN_WIDTH := 480

# QCOM BSP
TARGET_USES_QCOM_BSP := true
COMMON_GLOBAL_CFLAGS += -DQCOM_BSP
# QCOM hardware
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
# Recovery
#TARGET_RECOVERY_FSTAB := device/huawei/y530/ramdisk/fstab.qcom

#size
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
# QCOM hardware
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
# Recovery
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

TARGET_PREBUILT_KERNEL := device/huawei/y530/kernel

# add for phicomm c230 msm8610
#TARGET_RECOVERY_LCD_BACKLIGHT_PATH := \"/sys/class/leds/lcd-backlight/brightness\"
BOARD_HAS_NO_SELECT_BUTTON := true

BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02000000 --tags_offset 0x01e00000 --dt device/huawei/y530/dt.img is very important, as it calls dt.img to build the kernel. So, after unpacking boot.img from original firmware with xialou's mkbootimg tools I put the resultant dt.img, zImag, ramdisk.gz and ramdisk folder inside cm11/device/huawei/y530 folder. After this, I took the msm_ion.h and msm_mdp.h files from kernel source code and put them inside /cm11/bootable/recovery/minui/linux.

The fstab file I used is exactly this:

#device	fstype	mount point	[device2] [length=]
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,length=-16384
/dev/block/mmcblk1p1 /storage/sdcard1 vfat nosuid,nodev	wait
/dev/block/mmcblk0p21 /storage/sdcard0 vfat nosuid,nodev	wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults

Man, I'm no developer, I may have done a lot of redundant things. But with these hints, you may build your own CWM recovery.img. I really am looking forward to see what you can accomplish with this information. Good luck!