From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot defconfig issues
Date: Fri, 12 Feb 2021 09:24:58 +0100 [thread overview]
Message-ID: <20210212092458.165a3ec7@windsurf.home> (raw)
In-Reply-To: <582a548d-b9e3-39dc-f234-10a31e0a355d@mind.be>
Hello,
On Fri, 12 Feb 2021 09:17:53 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> I propose to just remove this defconfig. We're not really happy with those
> non-minimal defconfigs, right. I think it only makes sense to keep something
> like that if there really is something board-specific in there, which is not the
> case here I think.
Well, we've got several of these "development" defconfigs for
Atmel/Microchip platforms:
at91sam9x5ek_dev_defconfig
at91sam9x5ek_mmc_dev_defconfig
atmel_sama5d27_som1_ek_mmc_dev_defconfig
atmel_sama5d2_xplained_mmc_dev_defconfig
atmel_sama5d3_xplained_dev_defconfig
atmel_sama5d3_xplained_mmc_dev_defconfig
atmel_sama5d4_xplained_dev_defconfig
atmel_sama5d4_xplained_mmc_dev_defconfig
microchip_sam9x60ek_mmc_dev_defconfig
microchip_sama5d27_wlsom1_ek_mmc_dev_defconfig
There was quite some debate back then on whether we wanted them or not
in upstream Buildroot. Microchip has its own BR2_EXTERNAL layer at
https://github.com/linux4sam/buildroot-external-microchip with a bunch
of other defconfigs.
But Arnout, I thought you were inclined to having "demo" defconfigs in
Buildroot upstream. Have you changed your mind ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-02-12 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6025e87c3e3ce_c6a70d4128370@gitlab-sidekiq-catchall-v1-bb68c6455-8rbvh.mail>
2021-02-12 8:13 ` [Buildroot] Buildroot defconfig issues Thomas Petazzoni
2021-02-12 8:17 ` Arnout Vandecappelle
2021-02-12 8:24 ` Thomas Petazzoni [this message]
2021-02-12 9:41 ` Arnout Vandecappelle
2021-02-12 9:50 ` Thomas Petazzoni
2021-02-17 13:58 ` Ludovic.Desroches at microchip.com
2021-02-17 13:58 ` Ludovic.Desroches at microchip.com
2021-02-12 8:43 ` Peter Korsgaard
2021-02-13 15:12 ` Peter Seiderer
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=20210212092458.165a3ec7@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;
as well as URLs for NNTP newsgroup(s).