All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 11 Jan 2016 07:59:47 +0000	[thread overview]
Message-ID: <1452499187.3277.3.camel@synopsys.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075F4E843B4@us01wembx1.internal.synopsys.com>

Hi Vineet,

On Mon, 2016-01-11@07:47 +0000, Vineet Gupta wrote:
> On Saturday 09 January 2016 05:55 AM, Carlos Palminha wrote:
> > Hi Alexey,
> > 
> > Probably my e-mail comments before the patch mislead you...
> > If you download the kernel source and try to compile it, it won't work because of the INITRAMFS pointing to a non
> > -existing directory. (check log below)
> > 
> > That's why that option should be removed from the standard kernel.
> 
> Since the axs101 DT cmdline lacks any reference to root device - how does this
> unmodified kernel boot anyways w/o changing DT. Does uboot provide the cmdline for
> rootfs ?

Indeed if initramfs is not built-in vmlinux/uImage then kernel command-line
must be adjusted to point to real root device.

This could be done in 2 ways:

 [1] Manually modify "bootargs" value in arch/arc/boot/dts/axs10{1|3}.dts
 [2] In case of U-Boot it's possible to load device tree blob together with uImage
     and in that case U-Boot's "bootargs" env variable will override the one in .dtb

-Alexey

  reply	other threads:[~2016-01-11  7:59 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
2016-01-09  0:25   ` Carlos Palminha
2016-01-11  7:47     ` Vineet Gupta
2016-01-11  7:59       ` Alexey Brodkin [this message]
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=1452499187.3277.3.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.