at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3
|
|
|
|
|
bool "AT91 Bootstrap 3"
|
2018-04-01 07:08:35 +02:00
|
|
|
depends on BR2_arm926t || BR2_cortex_a5
|
at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
help
|
|
|
|
|
AT91Bootstrap is a first level bootloader for the Atmel AT91
|
|
|
|
|
devices. It integrates algorithms for:
|
2018-04-01 07:08:41 +02:00
|
|
|
- Device initialization such as clock configuration, PIO
|
|
|
|
|
settings...
|
at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
- Peripheral drivers such as PIO, PMC or SDRAMC...
|
2018-04-01 07:08:41 +02:00
|
|
|
- Physical media algorithm such as DataFlash, NandFlash, NOR
|
|
|
|
|
Flash...
|
at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
|
2018-09-20 15:24:48 +02:00
|
|
|
https://www.at91.com/linux4sam/bin/view/Linux4SAM/AT91Bootstrap
|
|
|
|
|
|
at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
if BR2_TARGET_AT91BOOTSTRAP3
|
|
|
|
|
|
2015-06-02 10:46:20 +02:00
|
|
|
choice
|
|
|
|
|
|
|
|
|
|
prompt "AT91 Bootstrap 3 version"
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
|
2019-07-11 22:13:30 +02:00
|
|
|
bool "3.8.13"
|
2015-06-02 10:46:20 +02:00
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
|
|
|
|
|
bool "Custom Git repository"
|
|
|
|
|
help
|
2018-04-01 07:08:41 +02:00
|
|
|
This option allows Buildroot to get the AT91 Bootstrap 3
|
|
|
|
|
source code from a Git repository.
|
2015-06-02 10:46:20 +02:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL
|
|
|
|
|
string "URL of custom repository"
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION
|
|
|
|
|
string "Custom repository version"
|
|
|
|
|
help
|
|
|
|
|
Revision to use in the typical format used by Git
|
|
|
|
|
E.G. a sha id, a tag, branch, ..
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_VERSION
|
|
|
|
|
string
|
2019-07-11 22:13:30 +02:00
|
|
|
default "v3.8.13" if BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
|
2015-06-02 10:46:20 +02:00
|
|
|
default BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION \
|
|
|
|
|
if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
|
|
|
|
|
|
at91bootstrap3: new package
Note that this new package, at91bootstrap3, is being added alongside the
existing at91bootstrap. This was suggested by Thomas Petazzoni, whose
comments on the mailing list are quoted below.
For this package, I am not sure we can do a simple version bump. Since
there is (was?) no upstream for AT91Bootstrap 1.x, many
vendors/companies had to maintain their patches on top of AT91Bootstrap
1.x. See for example
board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch. Therefore,
removing AT91Bootstrap 1.x from the tree will prevent those platforms
to work. I know people should upgrade, but AT91Bootstrap 3.x is quite
significantly different, so the porting effort is not that simple.
Therefore, I'm wondering whether we should kee at91bootstrap as it is,
and create a separate package at91bootstrap3 for the 3.x generation.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-17 10:36:23 +02:00
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_PATCH_DIR
|
|
|
|
|
string "custom patch dir"
|
|
|
|
|
help
|
|
|
|
|
If your board requires custom patches, add the path to the
|
|
|
|
|
directory containing the patches here. The patches must be
|
|
|
|
|
named at91bootstrap3-<something>.patch.
|
|
|
|
|
|
|
|
|
|
Most users may leave this empty
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Configuration selection
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "AT91 Bootstrap 3 configuration"
|
|
|
|
|
default BR2_TARGET_AT91BOOTSTRAP3_USE_DEFCONFIG
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_USE_DEFCONFIG
|
|
|
|
|
bool "Using a defconfig"
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG
|
|
|
|
|
bool "Using a custom config file"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG
|
|
|
|
|
string "Defconfig name"
|
|
|
|
|
depends on BR2_TARGET_AT91BOOTSTRAP3_USE_DEFCONFIG
|
|
|
|
|
help
|
|
|
|
|
Name of the at91bootstrap3 defconfig file to use, without the
|
|
|
|
|
trailing _defconfig. The defconfig is located at
|
|
|
|
|
board/<processor>/<board>_defconfig in the at91bootstrap3
|
|
|
|
|
tree.
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE
|
|
|
|
|
string "Configuration file path"
|
|
|
|
|
depends on BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG
|
|
|
|
|
help
|
|
|
|
|
Path to the at91bootstrap3 configuration file
|
|
|
|
|
|
|
|
|
|
endif # BR2_TARGET_AT91BOOTSTRAP3
|
