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
|
boot/at91bootstrap3: add support for at91bootstrap 4.x series
The project at https://github.com/linux4sam/at91bootstrap was until
now releasing 3.x versions, which were packaged using
boot/at91bootstrap3/ in Buildroot. Microchip has now started a new
branch of at91bootstrap, called 4.x, which will only support the
following devices: sam9x60, sama5d2, sama5d3, sama5d4, sama7g5. A
number of older devices from Microchip will only be supported by the
existing 3.x series.
Therefore, we cannot simply remove support for the 3.x series, and
allow using only the 4.x series.
So what this commit does is extend the boot/at91bootstrap3 package to
support building both 3.x and 4.x versions. In detail, this implies:
* Having the BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION symbol point to
the latest 4.x version. Indeed, we want
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION to really point to the
latest upstream version, even if that means potential breakage for
users. Users who want to use a fixed version of at91bootstrap
should anyway not be using
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION.
* Introduce BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X for users who
would like to use the latest 3.x series.
* Adjust the installation logic, as images to install are now in
build/binaries/*.bin instead of binaries/*.bin. In order to not
have to differentiate 3.x and 4.x, we simply use $(wildcard ...) to
expand the list of files to install.
* To make it clear that boot/at91bootstrap3 supports both 3.x and
4.x, we also update the prompt of the package.
at911bootstrap does not carry a license file; so far we were using
main.c as the license file, as it carries the license blurb. Now that we
have a known alternate version, we would need a per-version hash for
that file. However, this is a bit too cumbersome to handle, so just drop
using main.c as the license file. When upstream introduces a proper
license file, we can revisit the situation.
Update the two defconfigs that were using the upstream 3.9.3 version;
all other defconfigs are using custom tarballs or custom git trees.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
[Thomas: while this patch is based on previous work by Eugen, it was
reworked quite significantly.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- drop main.c as license file, explain why
- update the two defconfigs
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-18 23:37:46 +02:00
|
|
|
bool "AT91 Bootstrap 3+"
|
2020-07-31 11:02:31 +02:00
|
|
|
depends on BR2_arm926t || BR2_cortex_a5 || BR2_cortex_a7
|
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
|
|
|
|
|
|
boot/at91bootstrap3: add support for at91bootstrap 4.x series
The project at https://github.com/linux4sam/at91bootstrap was until
now releasing 3.x versions, which were packaged using
boot/at91bootstrap3/ in Buildroot. Microchip has now started a new
branch of at91bootstrap, called 4.x, which will only support the
following devices: sam9x60, sama5d2, sama5d3, sama5d4, sama7g5. A
number of older devices from Microchip will only be supported by the
existing 3.x series.
Therefore, we cannot simply remove support for the 3.x series, and
allow using only the 4.x series.
So what this commit does is extend the boot/at91bootstrap3 package to
support building both 3.x and 4.x versions. In detail, this implies:
* Having the BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION symbol point to
the latest 4.x version. Indeed, we want
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION to really point to the
latest upstream version, even if that means potential breakage for
users. Users who want to use a fixed version of at91bootstrap
should anyway not be using
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION.
* Introduce BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X for users who
would like to use the latest 3.x series.
* Adjust the installation logic, as images to install are now in
build/binaries/*.bin instead of binaries/*.bin. In order to not
have to differentiate 3.x and 4.x, we simply use $(wildcard ...) to
expand the list of files to install.
* To make it clear that boot/at91bootstrap3 supports both 3.x and
4.x, we also update the prompt of the package.
at911bootstrap does not carry a license file; so far we were using
main.c as the license file, as it carries the license blurb. Now that we
have a known alternate version, we would need a per-version hash for
that file. However, this is a bit too cumbersome to handle, so just drop
using main.c as the license file. When upstream introduces a proper
license file, we can revisit the situation.
Update the two defconfigs that were using the upstream 3.9.3 version;
all other defconfigs are using custom tarballs or custom git trees.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
[Thomas: while this patch is based on previous work by Eugen, it was
reworked quite significantly.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- drop main.c as license file, explain why
- update the two defconfigs
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-18 23:37:46 +02:00
|
|
|
prompt "AT91 Bootstrap 3+ version"
|
2015-06-02 10:46:20 +02:00
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
|
boot/at91bootstrap3: add support for at91bootstrap 4.x series
The project at https://github.com/linux4sam/at91bootstrap was until
now releasing 3.x versions, which were packaged using
boot/at91bootstrap3/ in Buildroot. Microchip has now started a new
branch of at91bootstrap, called 4.x, which will only support the
following devices: sam9x60, sama5d2, sama5d3, sama5d4, sama7g5. A
number of older devices from Microchip will only be supported by the
existing 3.x series.
Therefore, we cannot simply remove support for the 3.x series, and
allow using only the 4.x series.
So what this commit does is extend the boot/at91bootstrap3 package to
support building both 3.x and 4.x versions. In detail, this implies:
* Having the BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION symbol point to
the latest 4.x version. Indeed, we want
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION to really point to the
latest upstream version, even if that means potential breakage for
users. Users who want to use a fixed version of at91bootstrap
should anyway not be using
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION.
* Introduce BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X for users who
would like to use the latest 3.x series.
* Adjust the installation logic, as images to install are now in
build/binaries/*.bin instead of binaries/*.bin. In order to not
have to differentiate 3.x and 4.x, we simply use $(wildcard ...) to
expand the list of files to install.
* To make it clear that boot/at91bootstrap3 supports both 3.x and
4.x, we also update the prompt of the package.
at911bootstrap does not carry a license file; so far we were using
main.c as the license file, as it carries the license blurb. Now that we
have a known alternate version, we would need a per-version hash for
that file. However, this is a bit too cumbersome to handle, so just drop
using main.c as the license file. When upstream introduces a proper
license file, we can revisit the situation.
Update the two defconfigs that were using the upstream 3.9.3 version;
all other defconfigs are using custom tarballs or custom git trees.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
[Thomas: while this patch is based on previous work by Eugen, it was
reworked quite significantly.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- drop main.c as license file, explain why
- update the two defconfigs
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-18 23:37:46 +02:00
|
|
|
bool "4.0.0-rc2"
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X
|
2021-05-18 23:37:47 +02:00
|
|
|
bool "3.10.2"
|
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
|
|
|
|
2019-12-16 16:06:34 +01:00
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
|
|
|
|
|
bool "Custom tarball"
|
|
|
|
|
|
2015-06-02 10:46:20 +02:00
|
|
|
endchoice
|
|
|
|
|
|
2019-12-16 16:06:34 +01:00
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL_LOCATION
|
|
|
|
|
string "URL of custom AT91Bootstrap tarball"
|
|
|
|
|
depends on BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
|
|
|
|
|
|
2015-06-02 10:46:20 +02:00
|
|
|
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
|
boot/at91bootstrap3: add support for at91bootstrap 4.x series
The project at https://github.com/linux4sam/at91bootstrap was until
now releasing 3.x versions, which were packaged using
boot/at91bootstrap3/ in Buildroot. Microchip has now started a new
branch of at91bootstrap, called 4.x, which will only support the
following devices: sam9x60, sama5d2, sama5d3, sama5d4, sama7g5. A
number of older devices from Microchip will only be supported by the
existing 3.x series.
Therefore, we cannot simply remove support for the 3.x series, and
allow using only the 4.x series.
So what this commit does is extend the boot/at91bootstrap3 package to
support building both 3.x and 4.x versions. In detail, this implies:
* Having the BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION symbol point to
the latest 4.x version. Indeed, we want
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION to really point to the
latest upstream version, even if that means potential breakage for
users. Users who want to use a fixed version of at91bootstrap
should anyway not be using
BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION.
* Introduce BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X for users who
would like to use the latest 3.x series.
* Adjust the installation logic, as images to install are now in
build/binaries/*.bin instead of binaries/*.bin. In order to not
have to differentiate 3.x and 4.x, we simply use $(wildcard ...) to
expand the list of files to install.
* To make it clear that boot/at91bootstrap3 supports both 3.x and
4.x, we also update the prompt of the package.
at911bootstrap does not carry a license file; so far we were using
main.c as the license file, as it carries the license blurb. Now that we
have a known alternate version, we would need a per-version hash for
that file. However, this is a bit too cumbersome to handle, so just drop
using main.c as the license file. When upstream introduces a proper
license file, we can revisit the situation.
Update the two defconfigs that were using the upstream 3.9.3 version;
all other defconfigs are using custom tarballs or custom git trees.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
[Thomas: while this patch is based on previous work by Eugen, it was
reworked quite significantly.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[yann.morin.1998@free.fr:
- drop main.c as license file, explain why
- update the two defconfigs
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-18 23:37:46 +02:00
|
|
|
default "v4.0.0-rc2" if BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
|
2021-05-18 23:37:47 +02:00
|
|
|
default "v3.10.2" if BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X
|
2015-06-02 10:46:20 +02:00
|
|
|
default BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION \
|
|
|
|
|
if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
|
2019-12-16 16:06:34 +01:00
|
|
|
default "custom" if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
|
2015-06-02 10:46:20 +02:00
|
|
|
|
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
|
|
|
|
|
|
2021-05-18 23:37:48 +02:00
|
|
|
config BR2_TARGET_AT91BOOTSTRAP3_NEEDS_PYTHON3
|
|
|
|
|
bool "needs host-python3"
|
|
|
|
|
help
|
|
|
|
|
Enable this option if the at91bootstrap build process needs
|
|
|
|
|
Python 3.x to be available on the host. This is needed in
|
|
|
|
|
some at91bootstrap configurations to use NAND/PMECC Python
|
|
|
|
|
scripts.
|
2021-05-19 14:34:58 +02:00
|
|
|
|
|
|
|
|
endif # BR2_TARGET_AT91BOOTSTRAP3
|
