[OpenWrt-Devel] [PATCH v3 1/2] mvebu: config-4.1: make mmc drivers builtin

[Josua Mayer]

Hi Andrej,

Am 28.04.2016 um 23:59 schrieb Andrej Vlasic:

> Hi Josua,
>
> On 28.04.2016 17:03, josua.mayer97 at gmail.com wrote:
>> From: Josua Mayer <privacy at not.given>
>>
>> This is especially useful on the Clearfog board which boots from mmc by
>> default.
>>
>> Signed-off-by: Josua Mayer <josua.mayer97 at gmail.com>
>> ---
>>  target/linux/mvebu/config-4.1 | 24 ++++++++++++++++++++++++
>>  1 file changed, 24 insertions(+)
>>
>> diff --git a/target/linux/mvebu/config-4.1 
>> b/target/linux/mvebu/config-4.1
>> index ee5c983..73319dd 100644
>> --- a/target/linux/mvebu/config-4.1
>> +++ b/target/linux/mvebu/config-4.1
>> @@ -362,3 +362,27 @@ CONFIG_ZBOOT_ROM_TEXT=0x0
>>  CONFIG_ZLIB_DEFLATE=y
>>  CONFIG_ZLIB_INFLATE=y
>>  CONFIG_ZONE_DMA_FLAG=0
>> +CONFIG_MMC=y
>> +CONFIG_MMC_BLOCK=y
>> +CONFIG_MMC_BLOCK_BOUNCE=y
>> +CONFIG_MMC_BLOCK_MINORS=8
>> +CONFIG_MMC_CB710=n
>> +CONFIG_MMC_CLKGATE=n
>> +CONFIG_MMC_DEBUG=n
>> +CONFIG_MMC_DW=n
>> +CONFIG_MMC_MVSDIO=y
>> +CONFIG_MMC_SDHCI=n
>> +CONFIG_MMC_TEST=n
>> +CONFIG_MMC_TIFM_SD=n
>> +CONFIG_MMC_TOSHIBA_PCI=n
>> +CONFIG_MMC_USDHI6ROL0=n
>> +CONFIG_MMC_USHC=n
>> +CONFIG_MMC_VIA_SDMMC=n
>> +CONFIG_MMC_VUB300=n
>> +CONFIG_MMC_SDHCI=y
>> +CONFIG_MMC_SDHCI_F_SDH30=n
>> +CONFIG_MMC_SDHCI_OF_ARASAN=n
>> +CONFIG_MMC_SDHCI_PCI=n
>> +CONFIG_MMC_SDHCI_PLTFM=y
>> +CONFIG_MMC_SDHCI_PXAV3=y
>> +CONFIG_SDIO_UART=n
>>
>
> Instead of adding those config options to default kernel config, it 
> would be better to create new mvebu subtarget, maybe called "harddisk" 
> that has support for external boot devices.
Personally I would prefer not to create a new target, just for different 
boot storage. There can be spi flash, sdcard, emmc, sata, who-knows-what 
other flavours. But I suppose there are mvebu devices out there with 
very limited flash memory?

So what do you think about making a new target mvebu_fat, which includes 
all the storage drivers that the supported SoCs have?
I came up with the name because my target device, the clearfog has 
plenty of storage so it does not mind if the OpenWRT image grows fat.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel