Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
	"Frager, Neal" <neal.frager@amd.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>,
	romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/zynq_zc702_defconfig: new defconfig
Date: Mon, 13 Nov 2023 18:10:23 +0100	[thread overview]
Message-ID: <20231113181023.34bf6492@booty> (raw)
In-Reply-To: <87bkce21br.fsf@48ers.dk>

Hi,

On Tue, 31 Oct 2023 17:39:36 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Frager," == Frager, Neal <neal.frager@amd.com> writes:  
> 
> Hi,
> 
>  > The remaining question is just a matter of how many zynq, zynqmp and
>  > versal defconfigs is the right amount for buildroot?  I would like to
>  > be able to support the following 11 boards, if it would be ok for the
>  > buildroot community.  5 of these 11 are already included in
>  > buildroot.  
> 
>  > zynq_zc702
>  > zynq_zc706
>  > zynqmp_zcu102
>  > zynqmp_zcu104
>  > zynqmp_zcu106
>  > zynqmp_kria_kd240
>  > zynqmp_kria_kr260
>  > zynqmp_kria_kv260
>  > versal_vck190
>  > versal_vek280 (coming next year)
>  > versal_vmk180  
> 
>  > In exchange, I would be ok with dropping the zynq_qmtech board and
>  > possibly one of the zynq_zed
>  > boards.  
> 
> I think the main issue with a lot of defconfigs is maintaining them (but
> you already do that) and the CI overhead from building all of them.
> 
> I guess we could come up with some logic to skip some of the zynq*
> defconfigs from the Gitlab CI setup. Romain, any good ideas?

After the discussion it seems quite clear that the patch is useful, and
the CI aspects can perhaps be sorted out, so:

Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-11-13 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 11:13 [Buildroot] [PATCH v2 1/1] configs/zynq_zc702_defconfig: new defconfig Neal Frager via buildroot
2023-10-31 11:12 ` Luca Ceresoli via buildroot
2023-10-31 12:12   ` Frager, Neal via buildroot
2023-10-31 12:34     ` Thomas Petazzoni via buildroot
     [not found]       ` <8a0d97bb-2fe5-4e09-8e95-b928a431ce1e@amd.com>
2023-10-31 13:30         ` Frager, Neal via buildroot
2023-10-31 16:39           ` Peter Korsgaard
2023-11-13 17:10             ` Luca Ceresoli via buildroot [this message]
2023-11-13 21:42               ` Peter Korsgaard

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=20231113181023.34bf6492@booty \
    --to=buildroot@buildroot.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.com \
    --cc=peter@korsgaard.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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