All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kilian.zinnecker--- via buildroot" <buildroot@buildroot.org>
To: kilian.zinnecker@mail.de, buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Robert Nelson <robertcnelson@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/xuantie-bins: new package
Date: Sun, 11 Feb 2024 13:15:35 +0100	[thread overview]
Message-ID: <6015348.lOV4Wx5bFT@laptop> (raw)
In-Reply-To: <08b6187c-94f2-4cbc-b0e8-0066ca687796@benettiengineering.com>

Hello Giulio, all,

[--SNIP--]
> can you please provide a separate patch to alphabetize?

I did so: https://gitlab.com/buildroot.org/buildroot/-/commit/
53fad3242d74b9fad11978429d6cc2879f783f4b

However, unfortunately Thomas de-alphabetized it again when he applied my 
RZBoard V2L patches: https://gitlab.com/buildroot.org/buildroot/-/commit/
f003675119c9ca503afa19c04074e81c49538baf

I just send a v3 of the BeagleV-Ahead patches. After we get this series 
applied, I will then again send a single patch to alphabetize.

[--SNIP--]
> > --- /dev/null
> > +++ b/package/xuantie-bins/Config.in
> > @@ -0,0 +1,6 @@
> > +config BR2_PACKAGE_XUANTIE_BINS
> > +	bool "xuantie-bins"
> > +	depends on BR2_riscv
> > +	help
> > +	  This package provides binary blobs, needed for the
> > +	  BeagleV-Ahead's SoC (TH1520).
> 
> Can you please describe a bit what those binaries are meant for?


I gave a brief description, but I don't know much about these. Maybe Robert 
can give even more information, if more is needed?

[--SNIP--]
> > +XUANTIE_BINS_FPGA_BIN_FILENAME = "bins/light_aon_fpga.bin"
> > +XUANTIE_BINS_AUDIO_BIN_FILENAME = "bins/light_c906_audio.bin"
> > +
> > +define XUANTIE_BINS_INSTALL_IMAGES_CMDS
> > +	$(foreach f, \
> > +		$(XUANTIE_BINS_FPGA_BIN_FILENAME) \
> > +		$(XUANTIE_BINS_AUDIO_BIN_FILENAME) \
> > +		, \
> > +		$(INSTALL) -D -m 0644 -t $(BINARIES_DIR) $(@D)/$(f)
> > +	)
> > +endef
> 
> Being only 2 files to be installed I'd prefer to see 2 lines instead of
> foreach loop. Can you please change it accordingly?

I unrolled the loop in my v3 of the patches.

Thanks for reviewing and best regards,
Kilian



_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-02-11 12:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 23:12 [Buildroot] [PATCH v2 0/2] Add board support for the BeagleV-Ahead kilian.zinnecker--- via buildroot
2023-12-04 23:12 ` [Buildroot] [PATCH v2 1/2] package/xuantie-bins: new package kilian.zinnecker--- via buildroot
2024-02-06 16:56   ` Giulio Benetti
2024-02-10 15:22     ` kilian.zinnecker--- via buildroot
2024-02-11 12:38       ` Thomas Petazzoni via buildroot
2024-02-11 12:15     ` kilian.zinnecker--- via buildroot [this message]
2024-02-13 18:19       ` Giulio Benetti
2023-12-04 23:12 ` [Buildroot] [PATCH v2 2/2] configs/beaglev_ahead: new defconfig kilian.zinnecker--- via buildroot
2024-02-06 16:31   ` Giulio Benetti
2024-02-11 12:24     ` kilian.zinnecker--- via buildroot
2024-02-13 18:17       ` Giulio Benetti

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=6015348.lOV4Wx5bFT@laptop \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kilian.zinnecker@mail.de \
    --cc=robertcnelson@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 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.