From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] configs: add defconfig for Telit EVK-PRO3
Date: Wed, 1 May 2013 23:13:16 +0200 [thread overview]
Message-ID: <20130501231316.35d6652f@skate> (raw)
In-Reply-To: <1366184503-16875-3-git-send-email-fabio.porcedda@gmail.com>
Dear Fabio Porcedda,
On Wed, 17 Apr 2013 09:41:42 +0200, Fabio Porcedda wrote:
> For more info, please find board/telit/evk-pro3/readme.txt
>
> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
> ---
> ...04.0-0001-watchdog-add-keep-alive-support.patch | 88 ++++++++
> ...02-watchdog-add-at91sam9-watchdog-support.patch | 228 +++++++++++++++++++++
> ...0003-at91sam9260-9g20-add-wathdog-support.patch | 40 ++++
> ...0004-at91sam9260-9g20-fix-wathdog-support.patch | 26 +++
> ...13.04.0-0005-watchdog-enable-for-evk-pro3.patch | 26 +++
> ...t91-at91_dt_defconfig-update-for-evk-pro3.patch | 44 ++++
That's quite a number of patches. I suppose they are all already
upstream, correct? If so, then maybe using a Git version would allow to
get rid of those patches in Buildroot, and then you could later on
submit a patch to update Barebox to the next stable version that
contains those patches? Maybe even Barebox 2013.05 will be released
soon with those patches?
> diff --git a/configs/telit_evk_pro3_defconfig b/configs/telit_evk_pro3_defconfig
> new file mode 100644
> index 0000000..f7df1e4
> --- /dev/null
> +++ b/configs/telit_evk_pro3_defconfig
> @@ -0,0 +1,16 @@
> +BR2_arm=y
> +BR2_PREFER_STATIC_LIB=y
This choice shouldn't be part of the defconfig.
> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y
This one generally isn't either, but I think we can be flexible on this
one.
> +BR2_PACKAGE_BUSYBOX_WATCHDOG=y
> +BR2_TARGET_ROOTFS_UBIFS=y
> +BR2_TARGET_ROOTFS_UBI=y
> +BR2_TARGET_BAREBOX=y
> +BR2_TARGET_BAREBOX_CUSTOM_VERSION=y
> +BR2_TARGET_BAREBOX_CUSTOM_VERSION_VALUE="2013.04.0"
> +BR2_TARGET_BAREBOX_CUSTOM_PATCH_DIR="board/telit/evk-pro3"
> +BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="telit_evk_pro3"
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_PATCH="board/telit/evk-pro3"
> +BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
> +BR2_LINUX_KERNEL_APPENDED_ZIMAGE=y
> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="evk-pro3"
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-01 21:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 7:41 [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-04-17 7:41 ` [Buildroot] [PATCH v2 1/3] barebox: add custom version option Fabio Porcedda
2013-05-01 21:10 ` Thomas Petazzoni
2013-05-03 6:49 ` Fabio Porcedda
2013-05-03 7:57 ` Fabio Porcedda
2013-05-03 8:55 ` Thomas Petazzoni
2013-05-03 9:17 ` Fabio Porcedda
2013-05-03 10:11 ` Thomas Petazzoni
2013-05-03 16:46 ` Arnout Vandecappelle
2013-05-06 14:15 ` Peter Korsgaard
2013-05-03 10:50 ` Peter Korsgaard
2013-05-03 11:26 ` Fabio Porcedda
2013-04-17 7:41 ` [Buildroot] [PATCH v2 2/3] configs: add defconfig for Telit EVK-PRO3 Fabio Porcedda
2013-05-01 21:13 ` Thomas Petazzoni [this message]
2013-05-01 22:14 ` Fabio Porcedda
2013-05-02 9:58 ` Thomas Petazzoni
2013-04-17 7:41 ` [Buildroot] [PATCH v2 3/3] configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot Fabio Porcedda
2013-05-01 21:14 ` Thomas Petazzoni
2013-05-01 22:04 ` Fabio Porcedda
2013-05-02 9:59 ` Thomas Petazzoni
2013-05-01 6:57 ` [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-05-03 8:24 ` Fabio Porcedda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130501231316.35d6652f@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.