Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Neal Frager <neal.frager@xilinx.com>,
	luca.ceresoli@bootlin.com, michal.simek@amd.com,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/3] add package/versal-firmware
Date: Sun, 21 Aug 2022 21:06:09 +0200	[thread overview]
Message-ID: <20220821210609.621500c5@windsurf> (raw)
In-Reply-To: <20220820151243.GM2167049@scaer>

Hello,

On Sat, 20 Aug 2022 17:12:43 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> > +config BR2_PACKAGE_VERSAL_FIRMWARE_LOCATION
> > +	string "versal firmware location"  
> 
> The prompt should be "Custom git repository"
> 
> > +	help
> > +	  Location of a versal firmware boot.bin.
> > +
> > +	  The value should be a git repository.  
> 
> So, there is not even a default location?

For Custom Git repository options, we do not want to have a default
location. We just removed such a default location in the Xenomai
package, see e4040d0d8e1d3d3b77de582b8354eca641a0613d.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-08-21 19:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  6:37 [Buildroot] [PATCH v1 1/3] add package/versal-firmware Neal Frager
2022-08-19  6:37 ` [Buildroot] [PATCH v1 2/3] add board/versal Neal Frager
2022-08-19  6:37 ` [Buildroot] [PATCH v1 3/3] add configs/versal_vck190_defconfig Neal Frager
2022-08-20 15:12 ` [Buildroot] [PATCH v1 1/3] add package/versal-firmware Yann E. MORIN
2022-08-20 17:52   ` Frager, Neal via buildroot
2022-08-20 19:17     ` Yann E. MORIN
2022-08-21  7:27       ` Frager, Neal via buildroot
2022-08-22 10:01       ` Frager, Neal via buildroot
2022-08-23 19:49         ` Arnout Vandecappelle
2022-08-24  6:43           ` Frager, Neal via buildroot
2022-08-21 19:06   ` Thomas Petazzoni via buildroot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-24 14:22 Neal Frager via buildroot
2022-11-02 16:11 ` Frager, Neal via buildroot
2022-11-02 16:44 ` Thomas Petazzoni via buildroot
2022-11-02 17:10   ` Frager, Neal via buildroot
2022-11-03  7:46 ` Luca Ceresoli via buildroot
2022-11-03  9:08   ` Frager, Neal via buildroot

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=20220821210609.621500c5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@xilinx.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox