mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <>
To: Trent Piepho <>
Subject: Re: Board specific environments and broken configs
Date: Mon, 17 May 2021 09:38:30 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Trent,

On Fri, May 14, 2021 at 11:46:38PM -0700, Trent Piepho wrote:
> The 12 boards with apparently unused envs:
> chumby_falconwing
> crystalfontz-cfa10036
> datamodul-edm-qmx6
> delphi-poc20
> dss11
> efika-mx-smartbook
> generic
> karo-tx25
> karo-tx51
> mx31moboard
> skov-imx6
> technexion-wandboard
> An issue with CONFIG_DEFAULT_ENVIRONMENT_PATH is that it applies to
> all boards in a config.  If multiple boards are built at once, e.g.
> imx_v7_defconfig, then there is no way for each board to have a
> different extra env this way.

Thanks for spotting this. It shows some points that could be cleaned up.
Generally I suggest to remove the unused files. When they are unused
nobody should miss them. For some boards we could think about removing
them as well, like for example the i.MX boards that are still not
converted to multiimage support.
I just sent a series starting this, but that's just a start...


Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

barebox mailing list

  reply	other threads:[~2021-05-17  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15  6:46 Trent Piepho
2021-05-17  7:38 ` Sascha Hauer [this message]
2021-05-17 20:57   ` Trent Piepho
2021-05-18 11:40     ` Sascha Hauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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