All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] configs/beaglev: enable host jh71xx-tools
Date: Sat, 15 May 2021 14:16:47 +0200	[thread overview]
Message-ID: <20210515121647.GG2506@scaer> (raw)
In-Reply-To: <20210514220316.1942381-3-thomas.petazzoni@bootlin.com>

Thomas, All,

On 2021-05-15 00:03 +0200, Thomas Petazzoni spake thusly:
> This host utility is useful to recover the bootloader.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  board/beaglev/readme.txt  | 4 +++-
>  configs/beaglev_defconfig | 1 +
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/board/beaglev/readme.txt b/board/beaglev/readme.txt
> index bbdb9b12ef..60678059e1 100644
> --- a/board/beaglev/readme.txt
> +++ b/board/beaglev/readme.txt
> @@ -119,4 +119,6 @@ bootloaders, so if you flash non-working versions, you'll have to go
>  through a recovery process. This requires wiring up to a separate
>  debug UART, which pins are located near the HDMI connector. See
>  https://wiki.seeedstudio.com/BeagleV-Update-bootloader-ddr-init-boot-uboot-Recover-bootloader/
> -section "Recover the bootloader" for more details.
> +section "Recover the bootloader" for more details. The instructions
> +make use of a jh7100-recover tool, which Buildroot has built as part
> +of this defconfig: it is available as output/host/bin/jh7100-recover.
> diff --git a/configs/beaglev_defconfig b/configs/beaglev_defconfig
> index 8943ce9c34..bbb69ca268 100644
> --- a/configs/beaglev_defconfig
> +++ b/configs/beaglev_defconfig
> @@ -35,3 +35,4 @@ BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
>  BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,starfive-tech,u-boot,3f3ac01a29ad1cd5fa519d86f81daead2447f1d4)/uboot-3f3ac01a29ad1cd5fa519d86f81daead2447f1d4.tar.gz"
>  BR2_TARGET_UBOOT_BOARD_DEFCONFIG="starfive_vic7100_beagle_v_smode"
>  BR2_PACKAGE_HOST_GENIMAGE=y
> +BR2_PACKAGE_HOST_JH71XX_TOOLS=y
> -- 
> 2.31.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2021-05-15 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 22:03 [Buildroot] [PATCH 0/2] Add jh71xx-tools package Thomas Petazzoni
2021-05-14 22:03 ` [Buildroot] [PATCH 1/2] package/jh71xx-tools: new package Thomas Petazzoni
2021-05-15  0:05   ` Bin Meng
2021-05-15 12:15   ` Yann E. MORIN
2021-05-18 15:45     ` Thomas Petazzoni
2021-05-14 22:03 ` [Buildroot] [PATCH 2/2] configs/beaglev: enable host jh71xx-tools Thomas Petazzoni
2021-05-15  0:05   ` Bin Meng
2021-05-15 12:16   ` Yann E. MORIN [this message]

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=20210515121647.GG2506@scaer \
    --to=yann.morin.1998@free.fr \
    --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.