From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "François Perrad" <francois.perrad@gadz.org>
Cc: buildroot <buildroot@busybox.net>, Francois Perrad <fperrad@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 2/3] package/qoriq-cadence-dp-firmware: add install in target
Date: Wed, 3 Aug 2022 22:19:13 +0200 [thread overview]
Message-ID: <20220803221913.470cbf7a@windsurf> (raw)
In-Reply-To: <CAB0FRssCzSJocBF3yee4nOEf-z=92Dm93OLaKoM7sCn+5jGgzA@mail.gmail.com>
On Wed, 3 Aug 2022 21:45:48 +0200
François Perrad <francois.perrad@gadz.org> wrote:
> in v1, the commit message was :
Why has the v2 commit message changed, to remove information?
> this firmware must be installed with the kernel,
> > there are 2 cases:
> >
> - in $(TARGET_DIR)/boot
> > - in $(BINARIES), in order to be bundled into a boot partition
This doesn't explain the *why*. How is the firmware being used from
$(TARGET_DIR)/boot ?
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
next prev parent reply other threads:[~2022-08-03 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 7:43 [Buildroot] [PATCH v2 0/3] new board LS1028ARDB Francois Perrad
2022-08-03 7:43 ` [Buildroot] [PATCH v2 1/3] boot/arm-trusted-firmware: allow to generate BL2 from RCW Francois Perrad
2022-08-03 15:46 ` Giulio Benetti
2022-08-03 15:47 ` Giulio Benetti
2022-08-03 7:43 ` [Buildroot] [PATCH v2 2/3] package/qoriq-cadence-dp-firmware: add install in target Francois Perrad
2022-08-03 15:56 ` Giulio Benetti
2022-08-03 16:32 ` Thomas Petazzoni via buildroot
2022-08-03 19:45 ` François Perrad
2022-08-03 20:19 ` Thomas Petazzoni via buildroot [this message]
2022-08-04 11:21 ` François Perrad
2022-08-03 7:43 ` [Buildroot] [PATCH v2 3/3] board/freescale/ls1028ardb: new board Francois Perrad
2022-08-03 16:11 ` 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=20220803221913.470cbf7a@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
--cc=francois.perrad@gadz.org \
--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.