barebox new option and new boards
v2 cover barebox new option and new boards
Hi all,
this patch set is for adding to barebox a custom version option and use this new option to add suppport for two new boards.
v2:
- Telit EVK-PRO3: use barebox custom version option
Best regards
Fabio Porcedda (3):
barebox: add custom version option
configs: add defconfig for Telit EVK-PRO3
configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot
.../linux-ARM-at91-enable-nand-ubifs-boot.patch | 44 ++++ ...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 ++++ board/telit/evk-pro3/readme.txt | 28 +++ boot/barebox/Config.in | 26 ++- configs/at91sam9260eknf_defconfig | 15 ++ configs/telit_evk_pro3_defconfig | 16 ++ 11 files changed, 567 insertions(+), 14 deletions(-) create mode 100644 board/atmel/at91sam9260ek/linux-ARM-at91-enable-nand-ubifs-boot.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0001-watchdog-add-keep-alive-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0002-watchdog-add-at91sam9-watchdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0003-at91sam9260-9g20-add-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0004-at91sam9260-9g20-fix-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0005-watchdog-enable-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/linux-0001-ARM-at91-at91_dt_defconfig-update-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/readme.txt create mode 100644 configs/at91sam9260eknf_defconfig create mode 100644 configs/telit_evk_pro3_defconfig
Signature · 1 line
1.8.1.4
PATCH v2 1/3 barebox: add custom version option
Add custom version option as used in the linux kernel. This way we can easily specify newer and older version. Remove the list of the older versions because is obsoleted by the new custom version option that is more flexible.
--- boot/barebox/Config.in | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-)
boot/barebox/Config.in +12 -14
@@ -12,18 +12,14 @@ choice help Select the specific Barebox version you want to use -config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0" - -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0" +config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions + config BR2_TARGET_BAREBOX_CUSTOM_TARBALL bool "Custom tarball"
@@ -32,6 +28,10 @@ config BR2_TARGET_BAREBOX_CUSTOM_GIT endchoice +config BR2_TARGET_BAREBOX_CUSTOM_VERSION_VALUE + string "Barebox version" + depends on BR2_TARGET_BAREBOX_CUSTOM_VERSION + if BR2_TARGET_BAREBOX_CUSTOM_TARBALL config BR2_TARGET_BAREBOX_CUSTOM_TARBALL_LOCATION
@@ -41,10 +41,8 @@ endif config BR2_TARGET_BAREBOX_VERSION string - default "2013.01.0" if BR2_TARGET_BAREBOX_2013_01 - default "2013.02.0" if BR2_TARGET_BAREBOX_2013_02 - default "2013.03.0" if BR2_TARGET_BAREBOX_2013_03 - default "2013.04.0" if BR2_TARGET_BAREBOX_2013_04 + default "2013.04.0" if BR2_TARGET_BAREBOX_LATEST_VERSION + default $BR2_TARGET_BAREBOX_CUSTOM_VERSION_VALUE if BR2_TARGET_BAREBOX_CUSTOM_VERSION default "custom" if BR2_TARGET_BAREBOX_CUSTOM_TARBALL default $BR2_TARGET_BAREBOX_CUSTOM_GIT_VERSION if BR2_TARGET_BAREBOX_CUSTOM_GIT
Signature · 1 line
1.8.1.4
PATCH v2 1/3 barebox: add custom version option
Dear Fabio Porcedda,
Quoted 8 lines · Fabio Porcedda
boot/barebox/Config.in +0
-8-config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0"
boot/barebox/Config.in choice · line 22
Quoted 10 lines
boot/barebox/Config.in +6
-2- -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0" +config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions +
We need to have something that is consistent between U-Boot, Barebox and the kernel. Currently U-Boot has a version selection, the Linux kernel allows to chose the latest version (but with an option named after the version itself, so the name of the option changes when the version changes) or a custom version, and now for Barebox you're proposing yet another solution: select the latest version (with an option name that never changes) or a custom version.
So, I'm fine doing changes on this, but they should be consistent across packages.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 1/3 barebox: add custom version option
Quoted 1 line · Thomas Petazzoni
Dear Fabio Porcedda,
Hi Thomas,
thanks for reviewing.
Quoted 15 lines · Fabio Porcedda
Quoted 14 lines
boot/barebox/Config.in +1
-10-config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0" - -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0"
Quoted 13 lines
boot/barebox/Config.in choice · line 22
Quoted 5 lines
boot/barebox/Config.in +5
-0+config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions +We need to have something that is consistent between U-Boot, Barebox and the kernel. Currently U-Boot has a version selection, the Linux kernel allows to chose the latest version (but with an option named after the version itself, so the name of the option changes when the version changes) or a custom version, and now for Barebox you're proposing yet another solution: select the latest version (with an option name that never changes) or a custom version.
I think it's easier to have a option name that doesn't change. If there isn't a specific reason to have a option name that changes then I will send a patch to change the linux kernel option name.
BR2_LINUX_KERNEL_3_9 -> BR2_LINUX_KERNEL_LATEST_VERSION
Best regards
Fabio Porcedda
Quoted 4 lines
So, I'm fine doing changes on this, but they should be consistent across packages.
Quoted 8 lines
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
Fabio Porcedda
PATCH v2 1/3 barebox: add custom version option
Quoted 36 lines · Fabio Porcedda
Quoted 1 line · Thomas Petazzoni
Dear Fabio Porcedda,
Hi Thomas,
thanks for reviewing.Quoted 15 lines · Fabio Porcedda
Quoted 14 lines
boot/barebox/Config.in +1
-10-config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0" - -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0"Quoted 13 lines
boot/barebox/Config.in choice · line 22
Quoted 5 lines
boot/barebox/Config.in +5
-0+config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions +We need to have something that is consistent between U-Boot, Barebox and the kernel. Currently U-Boot has a version selection, the Linux kernel allows to chose the latest version (but with an option named after the version itself, so the name of the option changes when the version changes) or a custom version, and now for Barebox you're proposing yet another solution: select the latest version (with an option name that never changes) or a custom version.
Quoted 5 lines
I think it's easier to have a option name that doesn't change. If there isn't a specific reason to have a option name that changes then I will send a patch to change the linux kernel option name.
BR2_LINUX_KERNEL_3_9->BR2_LINUX_KERNEL_LATEST_VERSION
In the toolchain/kernel-headers/Config.in
there are many BR2_KERNEL_HEADERS_3_X options,
for headers is impossible to change the option names and use only one.
So I must use BR2_TARGET_BAREBOX_2013_04 for barebox?
Best regards
Fabio Porcedda
Quoted 18 lines
Best regards
Fabio PorceddaQuoted 4 lines
So, I'm fine doing changes on this, but they should be consistent across packages.
Quoted 8 lines
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
Quoted 2 lines
--
Fabio Porcedda
--
Fabio Porcedda
PATCH v2 1/3 barebox: add custom version option
In reply to Fabio PorceddaDear Fabio Porcedda,
Quoted 29 lines · Fabio Porcedda
Quoted 15 lines · Fabio Porcedda
Quoted 14 lines
boot/barebox/Config.in +1
-10-config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0" - -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0"Quoted 13 lines
boot/barebox/Config.in choice · line 22
Quoted 5 lines
boot/barebox/Config.in +5
-0+config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions +We need to have something that is consistent between U-Boot, Barebox and the kernel. Currently U-Boot has a version selection, the Linux kernel allows to chose the latest version (but with an option named after the version itself, so the name of the option changes when the version changes) or a custom version, and now for Barebox you're proposing yet another solution: select the latest version (with an option name that never changes) or a custom version.
Quoted 5 lines
I think it's easier to have a option name that doesn't change. If there isn't a specific reason to have a option name that changes then I will send a patch to change the linux kernel option name.
BR2_LINUX_KERNEL_3_9->BR2_LINUX_KERNEL_LATEST_VERSION
I don't really have a strong opinion about this thing, probably Peter and Arnout have more ideas than I do on this.
The only thing I care about is to not make modifications specifically on Barebox that are inconsistent with what is done on U-Boot, the kernel, or other version-selectable components. For example, U-Boot still allows to chose between several recent versions, which would make it inconsistent with the patches you're proposing, and that's the thing I don't like.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 1/3 barebox: add custom version option
Quoted 42 lines · Thomas Petazzoni
Dear Fabio Porcedda,
Quoted 29 lines · Fabio Porcedda
Quoted 15 lines · Fabio Porcedda
Quoted 14 lines
boot/barebox/Config.in +1
-10-config BR2_TARGET_BAREBOX_2013_01 - bool "2013.01.0" - -config BR2_TARGET_BAREBOX_2013_02 - bool "2013.02.0" - -config BR2_TARGET_BAREBOX_2013_03 - bool "2013.03.0" - -config BR2_TARGET_BAREBOX_2013_04 +config BR2_TARGET_BAREBOX_LATEST_VERSION bool "2013.04.0"Quoted 13 lines
boot/barebox/Config.in choice · line 22
Quoted 5 lines
boot/barebox/Config.in +5
-0+config BR2_TARGET_BAREBOX_CUSTOM_VERSION + bool "Custom version" + help + This option allows to use a specific official versions +We need to have something that is consistent between U-Boot, Barebox and the kernel. Currently U-Boot has a version selection, the Linux kernel allows to chose the latest version (but with an option named after the version itself, so the name of the option changes when the version changes) or a custom version, and now for Barebox you're proposing yet another solution: select the latest version (with an option name that never changes) or a custom version.
Quoted 5 lines
I think it's easier to have a option name that doesn't change. If there isn't a specific reason to have a option name that changes then I will send a patch to change the linux kernel option name.
BR2_LINUX_KERNEL_3_9->BR2_LINUX_KERNEL_LATEST_VERSIONI don't really have a strong opinion about this thing, probably Peter and Arnout have more ideas than I do on this.
Quoted 6 lines
The only thing I care about is to not make modifications specifically on Barebox that are inconsistent with what is done on U-Boot, the kernel, or other version-selectable components. For example, U-Boot still allows to chose between several recent versions, which would make it inconsistent with the patches you're proposing, and that's the thing I don't like.
In the patch set v3 barebox is consistent with the kernel.
If you are speaking just about consistency, I can send a patch for U-Boot too. IMHO the kernel way is more flexible, so if we must choose only one method, the kernel way is better.
A problem with having only the latest three version available is that barebox and u-boot release frequency are very different. Barebox have 12 release per year, U-Boot only 4.
The latest three release of U-Boot cover nine months but the latest three release of barebox cover only three months.
So if a defconfig use a specific barebox version, that defconfig can be used only for three months.
I think that three months is not enough.
It's better if i send patch for U-Boot too?
Best regards
Fabio Porcedda
Quoted 8 lines
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
Fabio Porcedda
PATCH v2 1/3 barebox: add custom version option
Dear Fabio Porcedda,
Quoted 6 lines · Fabio Porcedda
In the patch set v3 barebox is consistent with the kernel.
If you are speaking just about consistency, I can send a patch for U-Boot too. IMHO the kernel way is more flexible, so if we must choose only one method, the kernel way is better.
Quoted 8 lines
A problem with having only the latest three version available is that barebox and u-boot release frequency are very different. Barebox have 12 release per year, U-Boot only 4.
The latest three release of U-Boot cover nine months but the latest three release of barebox cover only three months.
So if a defconfig use a specific barebox version, that defconfig can be used only for three months.
I think that three months is not enough.
I think what you say makes sense.
Quoted 1 line
It's better if i send patch for U-Boot too?
Yes. I would however maybe wait for the opinion of others like Arnout, Peter or Gustavo. Maybe they disagree with my opinion, and I don't want you to do extra work that may not be accepted in the end.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 1/3 barebox: add custom version option
In reply to Fabio PorceddaQuoted 2 lines · Fabio Porcedda
On Fri, May 3, 2013 at 10:55 AM, Thomas Petazzoni
<[email protected]> wrote:
[snip]
Quoted 2 lines
Quoted 2 lines
I don't really have a strong opinion about this thing, probably Peter and Arnout have more ideas than I do on this.
I don't. I started to reply this morning, then realized that I couldn't
formulate it consistently, so I gave up.
The _LATEST symbol name has the disadvantage that your build is not
reproducible when you update buildroot, because the meaning of "latest" will have changed. However, this is already the case for all other packages (which don't allow choosing the version).
With the version number in the symbol name, at least you are warned by
make oldconfig when the version has changed, because it will offer the choice again.
That said, I find this disadvantage so minor that it is not worth the
effort of changing the symbol name all the time. So either option is fine for me.
Quoted 13 lines
Quoted 6 lines
The only thing I care about is to not make modifications specifically on Barebox that are inconsistent with what is done on U-Boot, the kernel, or other version-selectable components. For example, U-Boot still allows to chose between several recent versions, which would make it inconsistent with the patches you're proposing, and that's the thing I don't like.
In the patch set v3 barebox is consistent with the kernel.
If you are speaking just about consistency, I can send a patch for U-Boot too. IMHO the kernel way is more flexible, so if we must choose only one method, the kernel way is better.
Quoted 8 lines
A problem with having only the latest three version available is that barebox and u-boot release frequency are very different. Barebox have 12 release per year, U-Boot only 4.
The latest three release of U-Boot cover nine months but the latest three release of barebox cover only three months.
So if a defconfig use a specific barebox version, that defconfig can be used only for three months.
I think that three months is not enough.
I agree with that one. In fact, I don't think it makes much sense to
have the option to go for an earlier version, also for U-Boot. If you need an earlier version (e.g. because you have patches that won't apply to the current version), chances are that it is not one of the few that are offered by buildroot. BTW, a nice addition would be to require _CUSTOM_VERSION before you can specify a patch directory, so that this consistency is guaranteed to some extent.
So I think that Fabio's basic approach (offer only the latest version,
but also have the option to specify the version) is the best one.
Quoted 1 line
It's better if i send patch for U-Boot too?
I would say yes, that would be nice.
But let's hear what Peter has to say as well.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH v2 1/3 barebox: add custom version option
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle <[email protected]> writes:
Hi,
Quoted 1 line
Quoted 1 line
It's better if i send patch for U-Boot too?
Arnout> I would say yes, that would be nice.
Arnout> But let's hear what Peter has to say as well.
I agree completely. _LATEST + custom version makes sense.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/3 barebox: add custom version option
In reply to Fabio PorceddaQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Fabio" == Fabio Porcedda <[email protected]> writes:
Hi,
Fabio> I think it's easier to have a option name that doesn't change. Fabio> If there isn't a specific reason to have a option name that Fabio> changes then I will send a patch to change the linux kernel Fabio> option name.
Fabio> BR2_LINUX_KERNEL_3_9 -> BR2_LINUX_KERNEL_LATEST_VERSION
Agreed. With the _3_9 option people often don't realize that it will only exist for a few months, and that they should use the CUSTOM_VERSION stuff to really fix the version.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/3 barebox: add custom version option
Quoted 9 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Fabio" == Fabio Porcedda <[email protected]> writes:
Hi,
Fabio> I think it's easier to have a option name that doesn't change. Fabio> If there isn't a specific reason to have a option name that Fabio> changes then I will send a patch to change the linux kernel Fabio> option name.
Quoted 8 lines
Fabio>
BR2_LINUX_KERNEL_3_9->BR2_LINUX_KERNEL_LATEST_VERSIONAgreed. With the _3_9 option people often don't realize that it will only exist for a few months, and that they should use the
CUSTOM_VERSIONstuff to really fix the version.--
Bye, Peter Korsgaard
Ok good, I will send a v4 adding that patch.
Best regards
--
Fabio Porcedda
PATCH v2 2/3 configs: add defconfig for Telit EVK-PRO3
In reply to Fabio PorceddaFor more info, please find board/telit/evk-pro3/readme.txt
--- ...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 ++++ board/telit/evk-pro3/readme.txt | 28 +++ configs/telit_evk_pro3_defconfig | 16 ++ 8 files changed, 496 insertions(+) create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0001-watchdog-add-keep-alive-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0002-watchdog-add-at91sam9-watchdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0003-at91sam9260-9g20-add-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0004-at91sam9260-9g20-fix-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0005-watchdog-enable-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/linux-0001-ARM-at91-at91_dt_defconfig-update-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/readme.txt create mode 100644 configs/telit_evk_pro3_defconfig
board/telit/evk-pro3/barebox-2013.04.0-0001-watchdog-add-keep-alive-support.patch new file +88 -0
@@ -0,0 +1,88 @@ +From b5e57a9f158a293b1151638336478af8a5aad0f0 Mon Sep 17 00:00:00 2001 +From: Jean-Christophe PLAGNIOL-VILLARD <[email protected]> +Date: Wed, 14 Nov 2012 19:16:35 +0800 +Subject: [PATCH 1/5] watchdog: add keep alive support + +this will allow to ping the watchdog via poller + +Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]> +--- + drivers/watchdog/Kconfig | 1 + + drivers/watchdog/wd_core.c | 21 +++++++++++++++++++++ + include/watchdog.h | 2 ++ + 3 files changed, 24 insertions(+) + +diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig +index 2e2900c..0b4dc84 100644 +--- a/drivers/watchdog/Kconfig ++++ b/drivers/watchdog/Kconfig +@@ -4,6 +4,7 @@ config WATCHDOG_IMX_RESET_SOURCE + + menuconfig WATCHDOG + bool "Watchdog support" ++ select GENERIC_POLLER + help + Many platforms support a watchdog to keep track of a working machine. + This framework provides routines to handle these watchdogs. +diff --git a/drivers/watchdog/wd_core.c b/drivers/watchdog/wd_core.c +index 3d0cfc6..a1b9e28 100644 +--- a/drivers/watchdog/wd_core.c ++++ b/drivers/watchdog/wd_core.c +@@ -17,18 +17,39 @@ + #include <errno.h> + #include <linux/ctype.h> + #include <watchdog.h> ++#include <poller.h> + + /* + * Note: this simple framework supports one watchdog only. + */ + static struct watchdog *watchdog; + ++static void watchdog_poller_func(struct poller_struct *poller) ++{ ++ watchdog->keep_alive(watchdog); ++} ++ ++static struct poller_struct watchdog_poller = { ++ .func = watchdog_poller_func, ++}; ++ + int watchdog_register(struct watchdog *wd) + { + if (watchdog != NULL) + return -EBUSY; + + watchdog = wd; ++ ++ if (watchdog->keep_alive) { ++ int ret; ++ ++ ret = poller_register(&watchdog_poller); ++ if (ret) { ++ watchdog = NULL; ++ return ret; ++ } ++ } ++ + return 0; + } + EXPORT_SYMBOL(watchdog_register); +diff --git a/include/watchdog.h b/include/watchdog.h +index 3e2d08e..d5ecf2f 100644 +--- a/include/watchdog.h ++++ b/include/watchdog.h +@@ -13,8 +13,10 @@ + #ifndef INCLUDE_WATCHDOG_H + # define INCLUDE_WATCHDOG_H + ++ + struct watchdog { + int (*set_timeout)(struct watchdog *, unsigned); ++ void (*keep_alive)(struct watchdog *); + }; + + int watchdog_register(struct watchdog *); +-- +1.8.1.4 +
board/telit/evk-pro3/barebox-2013.04.0-0002-watchdog-add-at91sam9-watchdog-support.patch new file +228 -0
228 lines not on this page · raw message
board/telit/evk-pro3/barebox-2013.04.0-0003-at91sam9260-9g20-add-wathdog-support.patch new file +40 -0
@@ -0,0 +1,40 @@ +From 3338bcb05479f1149420d4a0ea3904cb9e42eef5 Mon Sep 17 00:00:00 2001 +From: Jean-Christophe PLAGNIOL-VILLARD <[email protected]> +Date: Wed, 14 Nov 2012 19:18:22 +0800 +Subject: [PATCH 3/5] at91sam9260/9g20: add wathdog support + +Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[email protected]> +--- + arch/arm/mach-at91/at91sam9260_devices.c | 12 ++++++++++++ + 1 file changed, 12 insertions(+) + +diff --git a/arch/arm/mach-at91/at91sam9260_devices.c b/arch/arm/mach-at91/at91sam9260_devices.c +index 1c375ee..5885f91 100644 +--- a/arch/arm/mach-at91/at91sam9260_devices.c ++++ b/arch/arm/mach-at91/at91sam9260_devices.c +@@ -10,6 +10,7 @@ + * + */ + #include <common.h> ++#include <init.h> + #include <sizes.h> + #include <asm/armlinux.h> + #include <asm/hardware.h> +@@ -397,3 +398,14 @@ void at91_add_device_mci(short mmc_id, struct atmel_mci_platform_data *data) + #else + void at91_add_device_mci(short mmc_id, struct atmel_mci_platform_data *data) {} + #endif ++ ++#ifdef CONFIG_WATCHDOG_AT91SAM9X ++static int at91_add_device_watchdog(void) ++{ ++ add_generic_device("at91sam9_wdt", DEVICE_ID_SINGLE, NULL, ++ AT91_WDT + AT91_BASE_SYS, 16, IORESOURCE_MEM, NULL); ++ ++ return 0; ++} ++coredevice_initcall(at91_add_device_watchdog); ++#endif +-- +1.8.1.4 +
board/telit/evk-pro3/barebox-2013.04.0-0004-at91sam9260-9g20-fix-wathdog-support.patch new file +26 -0
@@ -0,0 +1,26 @@ +From e03bf0e3ad24898019b89eb9a6935d159c60268f Mon Sep 17 00:00:00 2001 +From: Fabio Porcedda <[email protected]> +Date: Thu, 17 Jan 2013 11:32:35 +0100 +Subject: [PATCH 4/5] at91sam9260/9g20: fix wathdog support + +Signed-off-by: Fabio Porcedda <[email protected]> +--- + arch/arm/mach-at91/at91sam9260_devices.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm/mach-at91/at91sam9260_devices.c b/arch/arm/mach-at91/at91sam9260_devices.c +index 5885f91..df675d2 100644 +--- a/arch/arm/mach-at91/at91sam9260_devices.c ++++ b/arch/arm/mach-at91/at91sam9260_devices.c +@@ -403,7 +403,7 @@ void at91_add_device_mci(short mmc_id, struct atmel_mci_platform_data *data) {} + static int at91_add_device_watchdog(void) + { + add_generic_device("at91sam9_wdt", DEVICE_ID_SINGLE, NULL, +- AT91_WDT + AT91_BASE_SYS, 16, IORESOURCE_MEM, NULL); ++ AT91_BASE_WDT, 16, IORESOURCE_MEM, NULL); + + return 0; + } +-- +1.8.1.4 +
board/telit/evk-pro3/barebox-2013.04.0-0005-watchdog-enable-for-evk-pro3.patch new file +26 -0
@@ -0,0 +1,26 @@ +From 98c96ea36a4b3bb9b92dde849db5e8d6918b5168 Mon Sep 17 00:00:00 2001 +From: Fabio Porcedda <[email protected]> +Date: Thu, 17 Jan 2013 11:32:59 +0100 +Subject: [PATCH 5/5] watchdog: enable for evk-pro3 + +Signed-off-by: Fabio Porcedda <[email protected]> +--- + arch/arm/configs/telit_evk_pro3_defconfig | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/arch/arm/configs/telit_evk_pro3_defconfig b/arch/arm/configs/telit_evk_pro3_defconfig +index 050d176..436cecf 100644 +--- a/arch/arm/configs/telit_evk_pro3_defconfig ++++ b/arch/arm/configs/telit_evk_pro3_defconfig +@@ -68,6 +68,8 @@ CONFIG_MCI_ATMEL=y + CONFIG_LED=y + CONFIG_LED_GPIO=y + CONFIG_LED_TRIGGERS=y ++CONFIG_WATCHDOG=y ++CONFIG_WATCHDOG_AT91SAM9X=y + CONFIG_FS_TFTP=y + CONFIG_FS_FAT=y + CONFIG_FS_FAT_LFN=y +-- +1.8.1.4 +
board/telit/evk-pro3/linux-0001-ARM-at91-at91_dt_defconfig-update-for-evk-pro3.patch new file +44 -0
44 lines not on this page · raw message
board/telit/evk-pro3/readme.txt new file +28 -0
@@ -0,0 +1,28 @@ +Buildroot board support for Telit EVK-PRO3 with Telit GE863-PRO3 + +Official site: + http://www.telit.com/en/products.php?p_id=3&p_ac=show&p=10 + +Build images: + make telit_evk_pro3_defconfig + make + + images built: + - output/images/barebox.bin + - output/images/zImage + - output/images/rootfs.ubi + + +Flash built images: + The first time you need to bootstrap from Telit Official Release 221.07.1007, + at the U-Boot prompt type: + U-Boot> loadb + send buildroot/output/images/barebox.bin + U-Boot> go 0x20200000 + + flash updated images using barebox through tftp: + barebox:/ erase dev/self0; cp /mnt/tftp/barebox.bin /dev/self0 + barebox:/ erase /dev/nand0.kernel.bb; cp /mnt/tftp/zImage /dev/nand0.kernel.bb + barebox:/ erase /dev/nand0.rootfs.bb; cp /mnt/tftp/rootfs.ubi /dev/nand0.rootfs.bb + barebox:/ erase dev/env0 + barebox:/ reset
configs/telit_evk_pro3_defconfig new file +16 -0
@@ -0,0 +1,16 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=y +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y +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"
Signature · 1 line
1.8.1.4
PATCH v2 2/3 configs: add defconfig for Telit EVK-PRO3
Dear Fabio Porcedda,
Quoted 10 lines · Fabio Porcedda
For more info, please find
board/telit/evk-pro3/readme.txtSigned-off-by Fabio Porcedda <[email protected]>--- ...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?
configs/telit_evk_pro3_defconfig line 2
Quoted 8 lines
configs/telit_evk_pro3_defconfig new file +2
-0@@ -0,0 +1,16 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=y
This choice shouldn't be part of the defconfig.
configs/telit_evk_pro3_defconfig line 3
Quoted 1 line
configs/telit_evk_pro3_defconfig new file +1
-0+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y
This one generally isn't either, but I think we can be flexible on this one.
configs/telit_evk_pro3_defconfig line 16
Quoted 13 lines
configs/telit_evk_pro3_defconfig new file +13
-0+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
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 2/3 configs: add defconfig for Telit EVK-PRO3
Quoted 2 lines · Thomas Petazzoni
Dear Fabio Porcedda,
Hi Thomas,
thanks for reviewing.
Quoted 12 lines · Fabio Porcedda
Quoted 10 lines
For more info, please find
board/telit/evk-pro3/readme.txtSigned-off-by Fabio Porcedda <[email protected]>--- ...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 ++++
Quoted 6 lines
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?
Unfortunately they are not upstream, the original author is still working on it. If possible I will try to help the original author, but i don't know when those patches will be
included upstream.
Anyway If using a git version is the preferred solution,
I will create and use a git repostiory on github.com.
Quoted 10 lines
configs/telit_evk_pro3_defconfig line 2
Quoted 8 lines
configs/telit_evk_pro3_defconfig new file +2
-0@@ -0,0 +1,16 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=yThis choice shouldn't be part of the defconfig.
Ok.
Quoted 21 lines
configs/telit_evk_pro3_defconfig line 3
Quoted 1 line
configs/telit_evk_pro3_defconfig new file +1
-0+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=yThis one generally isn't either, but I think we can be flexible on this one.
configs/telit_evk_pro3_defconfig line 16
Quoted 13 lines
configs/telit_evk_pro3_defconfig new file +13
-0+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,
Quoted 6 lines
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
Best regards
--
Fabio Porcedda
PATCH v2 2/3 configs: add defconfig for Telit EVK-PRO3
Dear Fabio Porcedda,
Quoted 7 lines · Fabio Porcedda
Quoted 6 lines
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?
Quoted 6 lines
Unfortunately they are not upstream, the original author is still working on it. If possible I will try to help the original author, but i don't know when those patches will be
included upstream.
Anyway If using a git version is the preferred solution, I will create and use a git repostiory on github.com.
No, in this case, keeping patches is preferred, until they get merged upstream.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 3/3 configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot
In reply to Fabio PorceddaThis is a configuration that provides a basic setup for generating bootable nandflash images:
- at91bootstrap
- barebox
- kernel
- rootfs
--- .../linux-ARM-at91-enable-nand-ubifs-boot.patch | 44 ++++++++++++++++++++++ configs/at91sam9260eknf_defconfig | 15 ++++++++ 2 files changed, 59 insertions(+) create mode 100644 board/atmel/at91sam9260ek/linux-ARM-at91-enable-nand-ubifs-boot.patch create mode 100644 configs/at91sam9260eknf_defconfig
board/atmel/at91sam9260ek/linux-ARM-at91-enable-nand-ubifs-boot.patch new file +44 -0
@@ -0,0 +1,44 @@ +From 17f439282c3fc92587e60935ff9efd13ea78e353 Mon Sep 17 00:00:00 2001 +From: Fabio Porcedda <[email protected]> +Date: Tue, 15 Jan 2013 11:17:42 +0100 +Subject: [PATCH] ARM: at91: enable nand ubifs boot + +Signed-off-by: Fabio Porcedda <[email protected]> +--- + arch/arm/configs/at91sam9260_defconfig | 7 +++++++ + 1 file changed, 7 insertions(+) + +diff --git a/arch/arm/configs/at91sam9260_defconfig b/arch/arm/configs/at91sam9260_defconfig +index 505b376..a438192 100644 +--- a/arch/arm/configs/at91sam9260_defconfig ++++ b/arch/arm/configs/at91sam9260_defconfig +@@ -1,5 +1,6 @@ + CONFIG_EXPERIMENTAL=y + # CONFIG_LOCALVERSION_AUTO is not set ++CONFIG_KERNEL_LZO=y + # CONFIG_SWAP is not set + CONFIG_SYSVIPC=y + CONFIG_LOG_BUF_SHIFT=14 +@@ -43,6 +44,11 @@ CONFIG_IP_PNP_BOOTP=y + # CONFIG_INET_LRO is not set + # CONFIG_IPV6 is not set + CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" ++CONFIG_MTD=y ++CONFIG_MTD_CMDLINE_PARTS=y ++CONFIG_MTD_NAND=y ++CONFIG_MTD_NAND_ATMEL=y ++CONFIG_MTD_UBI=y + CONFIG_BLK_DEV_RAM=y + CONFIG_BLK_DEV_RAM_SIZE=8192 + CONFIG_SCSI=y +@@ -82,6 +88,7 @@ CONFIG_RTC_DRV_AT91SAM9=y + CONFIG_EXT2_FS=y + CONFIG_VFAT_FS=y + CONFIG_TMPFS=y ++CONFIG_UBIFS_FS=y + CONFIG_CRAMFS=y + CONFIG_NLS_CODEPAGE_437=y + CONFIG_NLS_CODEPAGE_850=y +-- +1.8.0.3 +
configs/at91sam9260eknf_defconfig new file +15 -0
@@ -0,0 +1,15 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=y +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y +BR2_PACKAGE_HOST_SAM_BA=y +BR2_TARGET_ROOTFS_UBIFS=y +BR2_TARGET_ROOTFS_UBI=y +BR2_TARGET_AT91BOOTSTRAP=y +BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9260ek" +BR2_TARGET_AT91BOOTSTRAP_NANDFLASH=y +BR2_TARGET_BAREBOX=y +BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="at91sam9260ek" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_PATCH="board/atmel/at91sam9260ek" +BR2_LINUX_KERNEL_DEFCONFIG="at91sam9260" +BR2_LINUX_KERNEL_ZIMAGE=y
Signature · 1 line
1.8.1.4
PATCH v2 3/3 configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot
Dear Fabio Porcedda,
Quoted 10 lines · Fabio Porcedda
This is a configuration that provides a basic setup for generating bootable nandflash images:
- at91bootstrap
- barebox
- kernel
- rootfsSigned-off-by Fabio Porcedda <[email protected]>--- .../linux-ARM-at91-enable-nand-ubifs-boot.patch | 44 ++++++++++++++++++++++
I think we generally prefer to store a kernel defconfig, rather than a patch against one of the intree kernel defconfigs.
configs/at91sam9260eknf_defconfig line 2
Quoted 8 lines
configs/at91sam9260eknf_defconfig new file +2
-0@@ -0,0 +1,15 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=y
This shouldn't be in a defconfig.
configs/at91sam9260eknf_defconfig line 15
Quoted 13 lines
configs/at91sam9260eknf_defconfig new file +13
-0+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y +BR2_PACKAGE_HOST_SAM_BA=y +BR2_TARGET_ROOTFS_UBIFS=y +BR2_TARGET_ROOTFS_UBI=y +BR2_TARGET_AT91BOOTSTRAP=y +BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9260ek" +BR2_TARGET_AT91BOOTSTRAP_NANDFLASH=y +BR2_TARGET_BAREBOX=y +BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="at91sam9260ek" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_PATCH="board/atmel/at91sam9260ek" +BR2_LINUX_KERNEL_DEFCONFIG="at91sam9260" +BR2_LINUX_KERNEL_ZIMAGE=y
Thanks!
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 3/3 configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot
Quoted 1 line · Thomas Petazzoni
Dear Fabio Porcedda,
Hi Thomas,
thanks for reviewing.
Quoted 8 lines · Fabio Porcedda
Quoted 7 lines
This is a configuration that provides a basic setup for generating bootable nandflash images:
- at91bootstrap
- barebox
- kernel
- rootfs
Quoted 6 lines
Quoted 3 lines
Signed-off-by Fabio Porcedda <[email protected]>--- .../linux-ARM-at91-enable-nand-ubifs-boot.patch | 44 ++++++++++++++++++++++I think we generally prefer to store a kernel defconfig, rather than a patch against one of the intree kernel defconfigs.
I prefer to modify the defconfig intree kernel to be able to use newer versions of
the kernel smoothly with little effort if not any effort.
IMHO if i store a custom defconfig i need to change it more often (maybe for every new kernel version),
instead patching the intree kernel defconfig is less work for me and for the buildroot maintainers.
IMHO storing a kernel defconfig is better when someone want to use a specific kernel version
and not the latest upstream version with little modifications.
Quoted 11 lines
configs/at91sam9260eknf_defconfig line 2
Quoted 9 lines
configs/at91sam9260eknf_defconfig new file +2
-0@@ -0,0 +1,15 @@ +BR2_arm=y +BR2_PREFER_STATIC_LIB=yThis shouldn't be in a defconfig.
Ok i will send a corrected version without it.
Quoted 17 lines
Quoted 4 lines
configs/at91sam9260eknf_defconfig new file +3
-0+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y +BR2_PACKAGE_HOST_SAM_BA=y +BR2_TARGET_ROOTFS_UBIFS=yconfigs/at91sam9260eknf_defconfig line 15
Quoted 10 lines
configs/at91sam9260eknf_defconfig new file +10
-0+BR2_TARGET_ROOTFS_UBI=y +BR2_TARGET_AT91BOOTSTRAP=y +BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9260ek" +BR2_TARGET_AT91BOOTSTRAP_NANDFLASH=y +BR2_TARGET_BAREBOX=y +BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="at91sam9260ek" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_PATCH="board/atmel/at91sam9260ek" +BR2_LINUX_KERNEL_DEFCONFIG="at91sam9260" +BR2_LINUX_KERNEL_ZIMAGE=yThanks!
Quoted 6 lines
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
Best regards
--
Fabio Porcedda
PATCH v2 3/3 configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot
Dear Fabio Porcedda,
Quoted 7 lines · Fabio Porcedda
Quoted 2 lines
I think we generally prefer to store a kernel defconfig, rather than a patch against one of the intree kernel defconfigs.
I prefer to modify the defconfig intree kernel to be able to use newer versions of
the kernel smoothly with little effort if not any effort.
Quoted 8 lines
IMHO if i store a custom defconfig i need to change it more often (maybe for every new kernel version),
instead patching the intree kernel defconfig is less work for me and for the buildroot maintainers.IMHO storing a kernel defconfig is better when someone want to use a specific kernel version
and not the latest upstream version with little modifications.
Well, fair enough. I'm not sure it's really easier to maintain, but I don't have a strong opinion on this.
Thanks,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
v2 cover barebox new option and new boards
In reply to Fabio PorceddaQuoted 36 lines · Fabio Porcedda
Hi all,
this patch set is for adding to barebox a custom version option and use this new option to add suppport for two new boards.v2:
- Telit EVK-PRO3: use barebox custom version optionBest regards
Fabio Porcedda (3):
barebox: add custom version option
configs: add defconfig for Telit EVK-PRO3
configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot.../linux-ARM-at91-enable-nand-ubifs-boot.patch | 44 ++++ ...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 ++++ board/telit/evk-pro3/readme.txt | 28 +++ boot/barebox/Config.in | 26 ++- configs/at91sam9260eknf_defconfig | 15 ++ configs/telit_evk_pro3_defconfig | 16 ++ 11 files changed, 567 insertions(+), 14 deletions(-) create mode 100644 board/atmel/at91sam9260ek/linux-ARM-at91-enable-nand-ubifs-boot.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0001-watchdog-add-keep-alive-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0002-watchdog-add-at91sam9-watchdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0003-at91sam9260-9g20-add-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0004-at91sam9260-9g20-fix-wathdog-support.patch create mode 100644 board/telit/evk-pro3/barebox-2013.04.0-0005-watchdog-enable-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/linux-0001-ARM-at91-at91_dt_defconfig-update-for-evk-pro3.patch create mode 100644 board/telit/evk-pro3/readme.txt create mode 100644 configs/at91sam9260eknf_defconfig create mode 100644 configs/telit_evk_pro3_defconfig
Quoted 3 lines
--
1.8.1.4
Ping
Best regards
--
Fabio Porcedda
v2 cover barebox new option and new boards
I've sent the v3
Best regards
--
Fabio Porcedda