From: Vineet Gupta <vineet.gupta1@synopsys.com>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>,
"clabbe@baylibre.com" <clabbe@baylibre.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alexey.brodkin@synopsys.com" <alexey.brodkin@synopsys.com>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 2/2] arc: hsdk_defconfig: enable CONFIG_ARC_UBOOT_SUPPORT
Date: Tue, 5 Feb 2019 16:42:28 +0000 [thread overview]
Message-ID: <C2D7FE5348E1B147BCA15975FBA23075014642EBE9@US01WEMBX2.internal.synopsys.com> (raw)
In-Reply-To: 1549366931.27724.26.camel@synopsys.com
On 2/5/19 3:42 AM, Eugeniy Paltsev wrote:
> Hi Corentin,
>
> In case of devboards (like HSDK) we really often disable bootloader and load
> Linux image in memory via JTAG. Enabling CONFIG_ARC_UBOOT_SUPPORT by
> default will break it as we will try to interpret some junk in a registers
> as a pointers to bootargs/etc which aren't set by anyone in case of JTAG using.
>
> So it isn't a good idea to have CONFIG_ARC_UBOOT_SUPPORT enabled by default.
Right.
It is difficult to accommodate everyone's needs (often conflicting) in a single
defconfig.
Can you folks create an out-of-tree defconfig or some such.
-Vineet
WARNING: multiple messages have this Message-ID (diff)
From: vineet.gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 2/2] arc: hsdk_defconfig: enable CONFIG_ARC_UBOOT_SUPPORT
Date: Tue, 5 Feb 2019 16:42:28 +0000 [thread overview]
Message-ID: <C2D7FE5348E1B147BCA15975FBA23075014642EBE9@US01WEMBX2.internal.synopsys.com> (raw)
In-Reply-To: 1549366931.27724.26.camel@synopsys.com
On 2/5/19 3:42 AM, Eugeniy Paltsev wrote:
> Hi Corentin,
>
> In case of devboards (like HSDK) we really often disable bootloader and load
> Linux image in memory via JTAG. Enabling CONFIG_ARC_UBOOT_SUPPORT by
> default will break it as we will try to interpret some junk in a registers
> as a pointers to bootargs/etc which aren't set by anyone in case of JTAG using.
>
> So it isn't a good idea to have CONFIG_ARC_UBOOT_SUPPORT enabled by default.
Right.
It is difficult to accommodate everyone's needs (often conflicting) in a single
defconfig.
Can you folks create an out-of-tree defconfig or some such.
-Vineet
next prev parent reply other threads:[~2019-02-05 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 8:32 [PATCH 0/2] arc: hsdk_defconfig: permit kernelci jobs Corentin Labbe
2019-02-05 8:32 ` Corentin Labbe
2019-02-05 8:32 ` [PATCH 1/2] arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM Corentin Labbe
2019-02-05 8:32 ` Corentin Labbe
2019-02-05 8:32 ` [PATCH 2/2] arc: hsdk_defconfig: enable CONFIG_ARC_UBOOT_SUPPORT Corentin Labbe
2019-02-05 8:32 ` Corentin Labbe
2019-02-05 11:42 ` Eugeniy Paltsev
2019-02-05 11:42 ` Eugeniy Paltsev
2019-02-05 16:42 ` Vineet Gupta [this message]
2019-02-05 16:42 ` Vineet Gupta
2019-02-05 16:51 ` Alexey Brodkin
2019-02-05 16:51 ` Alexey Brodkin
2019-02-05 20:14 ` Kevin Hilman
2019-02-05 20:14 ` Kevin Hilman
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=C2D7FE5348E1B147BCA15975FBA23075014642EBE9@US01WEMBX2.internal.synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=alexey.brodkin@synopsys.com \
--cc=clabbe@baylibre.com \
--cc=eugeniy.paltsev@synopsys.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
/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.