From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] odroidc2_atf: new Package
Date: Thu, 3 Sep 2020 20:50:15 +0200 [thread overview]
Message-ID: <20200903205015.250c7dc3@windsurf.home> (raw)
In-Reply-To: <20200717164643.4702-2-daggs@gmx.com>
Hello Dagg,
On Fri, 17 Jul 2020 19:46:41 +0300
Dagg Stompler <daggs@gmx.com> wrote:
> introduce a package that holds the ATF for AmLogic's Odroid C2 boards
>
> Signed-off-by: Dagg Stompler <daggs@gmx.com>
So I applied this patch, but after doing significant rework:
- Instead of using your own custom repository, I used the Hardkernel
U-Boot repository as a source.
- I changed to a target package instead of a host package. I agree it
builds a host tool, but it also installs a bunch of firmware files
for the target, and that felt more "important" to me than the host
tool. Of course, this can be a never-ending discussion, as it's
difficult to draw the line.
- Renamed to odroidc2-firmware.
See the final commit at:
https://git.buildroot.org/buildroot/commit/?id=f0de62b7066c58a88207f0edf98ae49a23649421
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-03 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 16:46 [Buildroot] [PATCH 1/4] meson-tools: new Package Dagg Stompler
2020-07-17 16:46 ` [Buildroot] [PATCH 2/4] odroidc2_atf: " Dagg Stompler
2020-09-03 18:50 ` Thomas Petazzoni [this message]
2020-07-17 16:46 ` [Buildroot] [PATCH 3/4] board/odroidc2: add board Dagg Stompler
2020-09-03 18:53 ` Thomas Petazzoni
2020-07-17 16:46 ` [Buildroot] [PATCH 4/4] configs/odroidc2: add defconfig Dagg Stompler
2020-08-29 22:12 ` [Buildroot] [PATCH 1/4] meson-tools: new Package Thomas Petazzoni
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=20200903205015.250c7dc3@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox