From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] arc: Removed local initramfs source file from axs101 configuration.
Date: Thu, 7 Jan 2016 23:20:22 +0000 [thread overview]
Message-ID: <1452208821.18725.9.camel@synopsys.com> (raw)
In-Reply-To: <1451919315-18115-1-git-send-email-palminha@synopsys.com>
Hi Carlos,
On Mon, 2016-01-04@14:55 +0000, palminha@synopsys.com wrote:
> From: Carlos Palminha <palminha at synopsys.com>
>
> Cannot compile kernel with INITRAMFS SOURCE option.
> Please move this option to a buildroot patch.
First of all if your problem is only related to Buildroot then
there's not much sense in adding linux-snps-arc at lists.infradead.org
which is used for pure Linux kernel discussions.
Then even in case of Buildroot CONFIG_INITRAMFS_SOURCE could be a problem
only if you don't set Buildroot's BR2_TARGET_ROOTFS_INITRAMFS=y, see
how it is done in snps_axs101_defconfig here
https://git.busybox.net/buildroot/tree/configs/snps_axs101_defconfig#n7
What happens if BR2_TARGET_ROOTFS_INITRAMFS=y then existing in kernel's
defconfig CONFIG_INITRAMFS_SOURCE gets overridden with new value, see
https://git.busybox.net/buildroot/tree/linux/linux.mk#n217
Now if you really want to not use built-in kernel initramfs then simplest
thing to do is to run "make linux-menuconfig" from your Buildroot's folder
and disable or set with nothing CONFIG_INITRAMFS_SOURCE.
-Alexey
next prev parent reply other threads:[~2016-01-07 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 14:55 [PATCH] arc: Removed local initramfs source file from axs101 configuration CARLOS.PALMINHA
2016-01-07 23:20 ` Alexey Brodkin [this message]
2016-01-09 0:25 ` Carlos Palminha
2016-01-11 7:47 ` Vineet Gupta
2016-01-11 7:59 ` Alexey Brodkin
2016-01-13 1:13 ` Carlos Palminha
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=1452208821.18725.9.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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.