On 3/11/19 5:20 PM, Thomas Petazzoni wrote: > This commit updates the Linux kernel configuration used on Marvell > platforms to support dm-verity.
How much bigger is the kernel image getting when these options are activated? All mvebu devices I know of have a lot of memory so it does not really matter for this target, but I would like to know. Hmm, would it make more sense to have a feature flag like this: FEATURES:=dm-verify for these targets and only allow dm-verify support if this is set. Hauke > Signed-off-by: Thomas Petazzoni <thomas.petazz...@bootlin.com> > --- > target/linux/mvebu/config-4.14 | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/target/linux/mvebu/config-4.14 b/target/linux/mvebu/config-4.14 > index 296da5a109..e904725e23 100644 > --- a/target/linux/mvebu/config-4.14 > +++ b/target/linux/mvebu/config-4.14 > @@ -65,7 +65,10 @@ CONFIG_ASYNC_TX_ENABLE_CHANNEL_SWITCH=y > CONFIG_ATA=y > CONFIG_ATAGS=y > CONFIG_AUTO_ZRELADDR=y > +CONFIG_BLK_DEV_DM=y > +CONFIG_BLK_DEV_DM_BUILTIN=y > CONFIG_BLK_DEV_LOOP=y > +# CONFIG_BLK_DEV_MD is not set > CONFIG_BLK_DEV_SD=y > CONFIG_BLK_MQ_PCI=y > CONFIG_BLK_SCSI_REQUEST=y > @@ -166,6 +169,13 @@ CONFIG_DMADEVICES=y > CONFIG_DMA_ENGINE=y > CONFIG_DMA_ENGINE_RAID=y > CONFIG_DMA_OF=y > +CONFIG_DM_BUFIO=y > +# CONFIG_DM_CRYPT is not set > +# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set > +# CONFIG_DM_MIRROR is not set > +# CONFIG_DM_SNAPSHOT is not set > +CONFIG_DM_VERITY=y > +# CONFIG_DM_VERITY_FEC is not set > CONFIG_DTC=y > CONFIG_EARLY_PRINTK=y > CONFIG_EDAC_ATOMIC_SCRUB=y > @@ -302,6 +312,7 @@ CONFIG_MACH_MVEBU_V7=y > CONFIG_MAGIC_SYSRQ=y > CONFIG_MANGLE_BOOTARGS=y > CONFIG_MARVELL_PHY=y > +CONFIG_MD=y > CONFIG_MDIO_BUS=y > CONFIG_MDIO_DEVICE=y > CONFIG_MDIO_I2C=y > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
