U-boot integration fails on custom i.MX35 board

I still have one problem though regarding the u-boot environment:
It is directly in NAND where the mtd device u-boot-env lays, see the layout:

mxc_nand:512k(SBL1),512k(SBL2),1m(u-boot),1m(u-boot-env),2043m(ubi),2m(bbt)

But Mender thinks it’s in a ubi volume and therefore creates two volumes u-boot-env-1 and u-boot-env-2 in the resulting .ubimg file which I don’t need. Even worse, it overrides the custom fw_env.config file that I deploy in my custom u-boot-fw-utils recipe. See here the recipe:

SUMMARY = “U-Boot bootloader fw_printenv/setenv utilities”
require u-boot-common-imx.inc
require recipes-bsp/u-boot/u-boot-fw-utils-mender.inc

SRC_URI += " file://fw_env.config
"

INSANE_SKIP_${PN} = “already-stripped”
EXTRA_OEMAKE_class-target = ‘CROSS_COMPILE=${TARGET_PREFIX} CC=“${CC} ${CFLAGS} ${LDFLAGS}” HOSTCC=“${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}” V=1’
EXTRA_OEMAKE_class-cross = ‘ARCH=${TARGET_ARCH} CC=“${CC} ${CFLAGS} ${LDFLAGS} HOSTCC=”${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" V=1’

inherit uboot-config

do_compile () {
oe_runmake ${UBOOT_MACHINE}
oe_runmake env
}

do_install () {
install -d ${D}${base_sbindir}
install -d ${D}${sysconfdir}
install -m 755 ${S}/tools/env/fw_printenv ${D}${base_sbindir}/fw_printenv
install -m 755 ${S}/tools/env/fw_printenv ${D}${base_sbindir}/fw_setenv
install -m 0644 ${WORKDIR}/fw_env.config ${D}${sysconfdir}/fw_env.config
}

do_install_class-cross () {
install -d ${D}${bindir_cross}
install -m 755 ${S}/tools/env/fw_printenv ${D}${bindir_cross}/fw_printenv
install -m 755 ${S}/tools/env/fw_printenv ${D}${bindir_cross}/fw_setenv
install -m 0644 ${WORKDIR}/fw_env.config ${D}${sysconfdir}/fw_env.config
}

SYSROOT_PREPROCESS_FUNCS_class-cross = “uboot_fw_utils_cross”
uboot_fw_utils_cross() {
sysroot_stage_dir ${D}${bindir_cross} ${SYSROOT_DESTDIR}${bindir_cross}
}

PACKAGE_ARCH = “${MACHINE_ARCH}”
BBCLASSEXTEND = “cross”

PROVIDES_${PN} = “u-boot-fw-utils”
RPROVIDES_${PN} = “u-boot-fw-utils”

How can I tell Mender not to take care of where the u-boot environment is stored, since I do this myself?