Message ID | 20161103140841.28789-1-ludovic.desroches@atmel.com |
---|---|
State | Accepted |
Headers | show |
Hello, On Thu, 3 Nov 2016 15:08:38 +0100, Ludovic Desroches wrote: > Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both > NAND flash and SD card. > > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> > --- > board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ > board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ > configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ > configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ So after this patch, we would have: at91sam9x5ek_defconfig at91sam9x5ek_dev_defconfig at91sam9x5ek_mmc_dev_defconfig But no minimal MMC configuration. That's a lot of configurations for a single board. Can we rationalize a bit, and chose one configuration only (either NAND or MMC), for which we have the minimal and dev configurations? Thanks, Thomas
On Fri, Nov 04, 2016 at 11:48:40AM +0100, Thomas Petazzoni wrote: > Hello, > > On Thu, 3 Nov 2016 15:08:38 +0100, Ludovic Desroches wrote: > > Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both > > NAND flash and SD card. > > > > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> > > --- > > board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ > > board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ > > configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ > > configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ > > So after this patch, we would have: > > at91sam9x5ek_defconfig > at91sam9x5ek_dev_defconfig > at91sam9x5ek_mmc_dev_defconfig > > But no minimal MMC configuration. > > That's a lot of configurations for a single board. Can we rationalize a > bit, and chose one configuration only (either NAND or MMC), for which > we have the minimal and dev configurations? > I have in mind, but maybe I am wrong since the conversion is not recent, you told me having several defconfigs for the same board won't be an issue. The concern was more about having a dev_defconfig. Without a defconfig targetted to NAND or MMC, the customer will have to recompile the at91bootstrap and u-boot, this is something we would like to avoid. I think u-boot case could be handled because the difference is mainly about environment variables. Concerning at91bootstrap, it is more complex. If you have any suggestion to handle this case and so reducing the number of defconfig variants, I would be happy. Thanks Ludovic > Thanks, > > Thomas > -- > Thomas Petazzoni, CTO, Free Electrons > Embedded Linux and Kernel engineering > http://free-electrons.com
On 04/11/2016 at 14:14:08 +0100, Ludovic Desroches wrote : > On Fri, Nov 04, 2016 at 11:48:40AM +0100, Thomas Petazzoni wrote: > > Hello, > > > > On Thu, 3 Nov 2016 15:08:38 +0100, Ludovic Desroches wrote: > > > Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both > > > NAND flash and SD card. > > > > > > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> > > > --- > > > board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ > > > board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ > > > configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ > > > configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ > > > > So after this patch, we would have: > > > > at91sam9x5ek_defconfig > > at91sam9x5ek_dev_defconfig > > at91sam9x5ek_mmc_dev_defconfig > > > > But no minimal MMC configuration. > > > > That's a lot of configurations for a single board. Can we rationalize a > > bit, and chose one configuration only (either NAND or MMC), for which > > we have the minimal and dev configurations? > > > > I have in mind, but maybe I am wrong since the conversion is not recent, > you told me having several defconfigs for the same board won't be an issue. > The concern was more about having a dev_defconfig. > > Without a defconfig targetted to NAND or MMC, the customer will have to > recompile the at91bootstrap and u-boot, this is something we would like > to avoid. I think u-boot case could be handled because the difference is > mainly about environment variables. Concerning at91bootstrap, it is more > complex. If you have any suggestion to handle this case and so reducing > the number of defconfig variants, I would be happy. > I think the best would be to be able to merge defconfigs. So, you'd get one iminimal defconfig per machine plus only one for the development image.
Hello, On Fri, 4 Nov 2016 14:14:08 +0100, Ludovic Desroches wrote: > > That's a lot of configurations for a single board. Can we rationalize a > > bit, and chose one configuration only (either NAND or MMC), for which > > we have the minimal and dev configurations? > > I have in mind, but maybe I am wrong since the conversion is not recent, > you told me having several defconfigs for the same board won't be an issue. > The concern was more about having a dev_defconfig. Well, the issue is the overall multiplication of defconfigs, so both the fact that you have separate defconfigs for MMC and NAND, and the fact that you want to have those "dev_defconfig" contribute to the multiplication of defconfigs. > Without a defconfig targetted to NAND or MMC, the customer will have to > recompile the at91bootstrap and u-boot, this is something we would like > to avoid. I think u-boot case could be handled because the difference is > mainly about environment variables. Concerning at91bootstrap, it is more > complex. If you have any suggestion to handle this case and so reducing > the number of defconfig variants, I would be happy. Is it possible to have a single at91bootstrap for both the NAND and MMC scenarios? I guess you can decide depending on the boot source whether you should load u-boot from NAND or from MMC. However, this means you need to have both the NAND code and MMC code compiled in the same at91bootstrap image. Maybe this makes the at91bootstrap image too big? I'm not sure what are the constraints of the ROM code in terms of first stage bootloader size on this SoC. Thomas
On Fri, Nov 04, 2016 at 02:53:49PM +0100, Thomas Petazzoni wrote: > Hello, > > On Fri, 4 Nov 2016 14:14:08 +0100, Ludovic Desroches wrote: > > > > That's a lot of configurations for a single board. Can we rationalize a > > > bit, and chose one configuration only (either NAND or MMC), for which > > > we have the minimal and dev configurations? > > > > I have in mind, but maybe I am wrong since the conversion is not recent, > > you told me having several defconfigs for the same board won't be an issue. > > The concern was more about having a dev_defconfig. > > Well, the issue is the overall multiplication of defconfigs, so both > the fact that you have separate defconfigs for MMC and NAND, and the > fact that you want to have those "dev_defconfig" contribute to the > multiplication of defconfigs. > > > Without a defconfig targetted to NAND or MMC, the customer will have to > > recompile the at91bootstrap and u-boot, this is something we would like > > to avoid. I think u-boot case could be handled because the difference is > > mainly about environment variables. Concerning at91bootstrap, it is more > > complex. If you have any suggestion to handle this case and so reducing > > the number of defconfig variants, I would be happy. > > Is it possible to have a single at91bootstrap for both the NAND and MMC > scenarios? I guess you can decide depending on the boot source whether > you should load u-boot from NAND or from MMC. However, this means you > need to have both the NAND code and MMC code compiled in the same > at91bootstrap image. Maybe this makes the at91bootstrap image too big? > I'm not sure what are the constraints of the ROM code in terms of first > stage bootloader size on this SoC. No, it is not possible to get a single at91bootstrap to manage several boot medias. The boot media selection is an exclusive choice. Removing this constraint rises two potential issues: - the size, we may have a binary too big as you said for some SoCs (only 24KB) - we need to decide at execution time the boot media but we have no guarantee that all components are on the same media. Ludovic
Hello, On Thu, 3 Nov 2016 15:08:38 +0100, Ludovic Desroches wrote: > Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both > NAND flash and SD card. > > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> > --- > board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ > board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ > configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ > configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ > 4 files changed, 255 insertions(+) > create mode 100644 board/atmel/at91sam9x5ek_mmc/genimage.cfg > create mode 100755 board/atmel/at91sam9x5ek_mmc/post-image.sh > create mode 100644 configs/at91sam9x5ek_dev_defconfig > create mode 100644 configs/at91sam9x5ek_mmc_dev_defconfig In the end, I've applied your commit. But before doing so, I've added a at91sam9x5ek_mmc_defconfig, i.e a minimal defconfig for the MMC configuration. Please check that everything is still OK on your side. Thanks! Thomas
Hi, On 03/07/2017 09:59 PM, Thomas Petazzoni wrote: > Hello, > > On Thu, 3 Nov 2016 15:08:38 +0100, Ludovic Desroches wrote: >> Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both >> NAND flash and SD card. >> >> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> >> --- >> board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ >> board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ >> configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ >> configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ >> 4 files changed, 255 insertions(+) >> create mode 100644 board/atmel/at91sam9x5ek_mmc/genimage.cfg >> create mode 100755 board/atmel/at91sam9x5ek_mmc/post-image.sh >> create mode 100644 configs/at91sam9x5ek_dev_defconfig >> create mode 100644 configs/at91sam9x5ek_mmc_dev_defconfig > > In the end, I've applied your commit. But before doing so, I've added a > at91sam9x5ek_mmc_defconfig, i.e a minimal defconfig for the MMC > configuration. Thanks to add it, it is in line with defconfigs provided for other boards. > > Please check that everything is still OK on your side. > We have not release a new version of linux4sam yet, so it's ok. Thanks Ludovic > Thanks! > > Thomas >
diff --git a/board/atmel/at91sam9x5ek_mmc/genimage.cfg b/board/atmel/at91sam9x5ek_mmc/genimage.cfg new file mode 100644 index 0000000..46c2dc9 --- /dev/null +++ b/board/atmel/at91sam9x5ek_mmc/genimage.cfg @@ -0,0 +1,34 @@ +# Image for SD card boot on Atmel at91sam9x5ek boards +# +image boot.vfat { + vfat { + files = { + "zImage", + "at91sam9g15ek.dtb", + "at91sam9g25ek.dtb", + "at91sam9g35ek.dtb", + "at91sam9x25ek.dtb", + "at91sam9x35ek.dtb", + "boot.bin", + "u-boot.bin" + } + } + size = 16M +} + +image sdcard.img { + hdimage { + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + size = 512M + } +} diff --git a/board/atmel/at91sam9x5ek_mmc/post-image.sh b/board/atmel/at91sam9x5ek_mmc/post-image.sh new file mode 100755 index 0000000..b560fd3 --- /dev/null +++ b/board/atmel/at91sam9x5ek_mmc/post-image.sh @@ -0,0 +1,20 @@ +#!/bin/sh + +BOARD_DIR="$(dirname $0)" +GENIMAGE_CFG="${BOARD_DIR}/genimage.cfg" +GENIMAGE_TMP="${BUILD_DIR}/genimage.tmp" + +rm -rf "${GENIMAGE_TMP}" + +echo --rootpath "${TARGET_DIR}" +echo --tmppath "${GENIMAGE_TMP}" +echo --inputpath "${BINARIES_DIR}" +echo --outputpath "${BINARIES_DIR}" +echo --config "${GENIMAGE_CFG}" + +genimage \ + --rootpath "${TARGET_DIR}" \ + --tmppath "${GENIMAGE_TMP}" \ + --inputpath "${BINARIES_DIR}" \ + --outputpath "${BINARIES_DIR}" \ + --config "${GENIMAGE_CFG}" diff --git a/configs/at91sam9x5ek_dev_defconfig b/configs/at91sam9x5ek_dev_defconfig new file mode 100644 index 0000000..279ce3d --- /dev/null +++ b/configs/at91sam9x5ek_dev_defconfig @@ -0,0 +1,99 @@ +# Architecture +BR2_arm=y +BR2_arm926t=y + +# Toolchain +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y +# Needed for some packages +BR2_TOOLCHAIN_BUILDROOT_WCHAR=y +# Needed for gdb +BR2_PTHREAD_DEBUG=y +# Needed for some packages +BR2_TOOLCHAIN_BUILDROOT_CXX=y + +# System Configuration +# Needed for usb-utils +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_GIT=y +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/linux4sam/linux-at91.git" +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="linux4sam_5.5" +BR2_LINUX_KERNEL_DEFCONFIG="at91_dt" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91sam9g15ek at91sam9g25ek at91sam9g35ek at91sam9x25ek at91sam9x35ek" + +# Packages +BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y +BR2_PACKAGE_ALSA_UTILS=y +BR2_PACKAGE_ALSA_UTILS_ALSACONF=y +BR2_PACKAGE_ALSA_UTILS_APLAY=y +BR2_PACKAGE_FFMPEG=y +BR2_PACKAGE_FFMPEG_GPL=y +BR2_PACKAGE_FFMPEG_SWSCALE=y +BR2_PACKAGE_MPG123=y +BR2_PACKAGE_BZIP2=y +BR2_PACKAGE_GZIP=y +BR2_PACKAGE_UNZIP=y +BR2_PACKAGE_XZ=y +BR2_PACKAGE_ZIP=y +BR2_PACKAGE_GDB=y +BR2_PACKAGE_LMBENCH=y +BR2_PACKAGE_DOSFSTOOLS=y +BR2_PACKAGE_DOSFSTOOLS_FATLABEL=y +BR2_PACKAGE_DOSFSTOOLS_FSCK_FAT=y +BR2_PACKAGE_DOSFSTOOLS_MKFS_FAT=y +BR2_PACKAGE_MMC_UTILS=y +BR2_PACKAGE_MTD=y +BR2_PACKAGE_WILC1000_FIRMWARE=y +BR2_PACKAGE_DEVMEM2=y +BR2_PACKAGE_EVTEST=y +BR2_PACKAGE_I2C_TOOLS=y +BR2_PACKAGE_SETSERIAL=y +BR2_PACKAGE_SPI_TOOLS=y +BR2_PACKAGE_USBUTILS=y +BR2_PACKAGE_LIBDRM=y +BR2_PACKAGE_LIBDRM_INSTALL_TESTS=y +BR2_PACKAGE_DTC=y +BR2_PACKAGE_DTC_PROGRAMS=y +BR2_PACKAGE_BLUEZ_UTILS=y +BR2_PACKAGE_BRIDGE_UTILS=y +BR2_PACKAGE_CAN_UTILS=y +BR2_PACKAGE_DROPBEAR=y +BR2_PACKAGE_ETHTOOL=y +BR2_PACKAGE_IPERF=y +BR2_PACKAGE_IPROUTE2=y +BR2_PACKAGE_IPTABLES=y +BR2_PACKAGE_IW=y +BR2_PACKAGE_LRZSZ=y +BR2_PACKAGE_MII_DIAG=y +BR2_PACKAGE_OPENSSH=y +BR2_PACKAGE_WGET=y +BR2_PACKAGE_WIRELESS_TOOLS=y +BR2_PACKAGE_WPA_SUPPLICANT=y +BR2_PACKAGE_BASH=y +BR2_PACKAGE_HTOP=y +BR2_PACKAGE_VIM=y + +# Filesystem +BR2_TARGET_ROOTFS_UBIFS=y +BR2_TARGET_ROOTFS_UBIFS_LEBSIZE=0x1f000 +BR2_TARGET_ROOTFS_UBI=y +BR2_TARGET_ROOTFS_UBI_SUBSIZE=2048 + +# Bootloaders +BR2_TARGET_AT91BOOTSTRAP3=y +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="https://github.com/linux4sam/at91bootstrap.git" +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="v3.8.7" +BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="at91sam9x5eknf_uboot" +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_GIT=y +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/linux4sam/u-boot-at91.git" +BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="linux4sam_5.5" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="at91sam9x5ek_nandflash" + +# Host packages +BR2_PACKAGE_HOST_SAM_BA=y diff --git a/configs/at91sam9x5ek_mmc_dev_defconfig b/configs/at91sam9x5ek_mmc_dev_defconfig new file mode 100644 index 0000000..103b457 --- /dev/null +++ b/configs/at91sam9x5ek_mmc_dev_defconfig @@ -0,0 +1,102 @@ +# Architecture +BR2_arm=y +BR2_arm926t=y + +# Toolchain +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y +# Needed for some packages +BR2_TOOLCHAIN_BUILDROOT_WCHAR=y +# Needed for gdb +BR2_PTHREAD_DEBUG=y +# Needed for some packages +BR2_TOOLCHAIN_BUILDROOT_CXX=y + +# System Configuration +# Needed for usb-utils +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y +# Creation of the SD card image +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/atmel/at91sam9x5ek_mmc/post-image.sh" + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_GIT=y +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/linux4sam/linux-at91.git" +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="linux4sam_5.5" +BR2_LINUX_KERNEL_DEFCONFIG="at91_dt" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91sam9g15ek at91sam9g25ek at91sam9g35ek at91sam9x25ek at91sam9x35ek" + +# Packages +BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y +BR2_PACKAGE_ALSA_UTILS=y +BR2_PACKAGE_ALSA_UTILS_ALSACONF=y +BR2_PACKAGE_ALSA_UTILS_APLAY=y +BR2_PACKAGE_FFMPEG=y +BR2_PACKAGE_FFMPEG_GPL=y +BR2_PACKAGE_FFMPEG_SWSCALE=y +BR2_PACKAGE_MPG123=y +BR2_PACKAGE_BZIP2=y +BR2_PACKAGE_GZIP=y +BR2_PACKAGE_UNZIP=y +BR2_PACKAGE_XZ=y +BR2_PACKAGE_ZIP=y +BR2_PACKAGE_GDB=y +BR2_PACKAGE_LMBENCH=y +BR2_PACKAGE_DOSFSTOOLS=y +BR2_PACKAGE_DOSFSTOOLS_FATLABEL=y +BR2_PACKAGE_DOSFSTOOLS_FSCK_FAT=y +BR2_PACKAGE_DOSFSTOOLS_MKFS_FAT=y +BR2_PACKAGE_MMC_UTILS=y +BR2_PACKAGE_MTD=y +BR2_PACKAGE_WILC1000_FIRMWARE=y +BR2_PACKAGE_DEVMEM2=y +BR2_PACKAGE_EVTEST=y +BR2_PACKAGE_I2C_TOOLS=y +BR2_PACKAGE_SETSERIAL=y +BR2_PACKAGE_SPI_TOOLS=y +BR2_PACKAGE_USBUTILS=y +BR2_PACKAGE_LIBDRM=y +BR2_PACKAGE_LIBDRM_INSTALL_TESTS=y +BR2_PACKAGE_DTC=y +BR2_PACKAGE_DTC_PROGRAMS=y +BR2_PACKAGE_BLUEZ_UTILS=y +BR2_PACKAGE_BRIDGE_UTILS=y +BR2_PACKAGE_CAN_UTILS=y +BR2_PACKAGE_DROPBEAR=y +BR2_PACKAGE_ETHTOOL=y +BR2_PACKAGE_IPERF=y +BR2_PACKAGE_IPROUTE2=y +BR2_PACKAGE_IPTABLES=y +BR2_PACKAGE_IW=y +BR2_PACKAGE_LRZSZ=y +BR2_PACKAGE_MII_DIAG=y +BR2_PACKAGE_OPENSSH=y +BR2_PACKAGE_WGET=y +BR2_PACKAGE_WIRELESS_TOOLS=y +BR2_PACKAGE_WPA_SUPPLICANT=y +BR2_PACKAGE_BASH=y +BR2_PACKAGE_HTOP=y +BR2_PACKAGE_VIM=y + +# Filesystem +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y + +# Bootloaders +BR2_TARGET_AT91BOOTSTRAP3=y +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="https://github.com/linux4sam/at91bootstrap.git" +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="v3.8.7" +BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="at91sam9x5eksd_uboot" +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_GIT=y +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/linux4sam/u-boot-at91.git" +BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="linux4sam_5.5" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="at91sam9x5ek_mmc" + +# Host packages +# Needed to generate the SD card image +BR2_PACKAGE_HOST_DOSFSTOOLS=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MTOOLS=y
Add development rootfs based on linux4sam_5.4 for at91sam9x5ek for both NAND flash and SD card. Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com> --- board/atmel/at91sam9x5ek_mmc/genimage.cfg | 34 ++++++++++ board/atmel/at91sam9x5ek_mmc/post-image.sh | 20 ++++++ configs/at91sam9x5ek_dev_defconfig | 99 ++++++++++++++++++++++++++++ configs/at91sam9x5ek_mmc_dev_defconfig | 102 +++++++++++++++++++++++++++++ 4 files changed, 255 insertions(+) create mode 100644 board/atmel/at91sam9x5ek_mmc/genimage.cfg create mode 100755 board/atmel/at91sam9x5ek_mmc/post-image.sh create mode 100644 configs/at91sam9x5ek_dev_defconfig create mode 100644 configs/at91sam9x5ek_mmc_dev_defconfig