From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH v3 08/10] MIPS: port all mach* to multiimage
Date: Thu, 6 Dec 2018 10:15:45 +0100 [thread overview]
Message-ID: <20181206091545.6s72qpyz7q3q6rfx@pengutronix.de> (raw)
In-Reply-To: <ea5bfd0c-c90f-bf9d-2c42-d745cb31a403@rempel-privat.de>
On Wed, Dec 05, 2018 at 02:58:12PM +0100, Oleksij Rempel wrote:
> Am 05.12.18 um 09:50 schrieb Antony Pavlov:
> > I suppose there is a problem with simultaneous debug_ll support for AR9344 and AR9331 in one binary.
> > the Kconfig DEBUG_AR9331_UART and DEBUG_AR9344_UART options are mutually exclusive.
> >
> > Your approach makes it possible to build barebox binary image for AR9331 board with debug_ll code for AR9344
> > and vice versa.
>
> yes, same issues as with most of DEBUG_LL related configurations in
> common/Kconfig. It is possible to misconfigure the DEBUG_LL for board or
> SoC. Currently I don't have a solution except of remove DEBUG_LL support
> completely from Kconfig for MIPS, or introduce some dynamic
> configuration, which is not related to this patch set.
At least on ARM with multi image support you have to make sure to chose
the correct DEBUG_LL UART that fits the board. Or to put the other way
round: Enabling DEBUG_LL limits the build to a single board only, thus it
should only be enabled during debugging.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-12-06 9:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 9:19 [PATCH v3 00/10] MIPS: migrate to multiimage support Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 01/10] images: piggy: use "a" instead of #alloc flag Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 02/10] MIPS: add arch/mips/lib/pbl.lds.S Oleksij Rempel
2018-11-30 7:41 ` Sascha Hauer
2018-11-27 9:19 ` [PATCH v3 03/10] pbl: enable MIPS for PBL_RELOCATABLE Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 04/10] MIPS: start: preserve DTB pointer for later use Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 05/10] MIPS: multiimage: add ENTRY_FUNCTION macros Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 06/10] MIPS: mutliimage: pass devicetree from PBL to the main_entry Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 07/10] MIPS: put main_entry to __bare_init section Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 08/10] MIPS: port all mach* to multiimage Oleksij Rempel
2018-12-05 8:50 ` Antony Pavlov
2018-12-05 13:58 ` Oleksij Rempel
2018-12-06 9:15 ` Sascha Hauer [this message]
2018-12-07 7:09 ` Oleksij Rempel
2018-12-11 11:31 ` Antony Pavlov
2018-12-13 7:10 ` Sascha Hauer
2018-11-27 9:19 ` [PATCH v3 09/10] MIPS: remove HAS_NO_BOARD_HL_CODE support Oleksij Rempel
2018-11-27 9:19 ` [PATCH v3 10/10] MIPS: remove useless board files Oleksij Rempel
2018-11-30 7:46 ` [PATCH v3 00/10] MIPS: migrate to multiimage support Sascha Hauer
2018-11-30 9:41 ` Antony Pavlov
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=20181206091545.6s72qpyz7q3q6rfx@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.de \
--cc=o.rempel@pengutronix.de \
/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