All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@freescale.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] imx6sabresd: boot to /init in mfgtools mode
Date: Wed, 3 Sep 2014 19:14:47 +0200	[thread overview]
Message-ID: <54074C87.7030807@freescale.com> (raw)
In-Reply-To: <CADCpmyNfWhXzG2ud=XQFdZdpvvM2XhSM-ABM47TOy2kqDmLTgg@mail.gmail.com>

On 08/26/2014 06:13 AM, Gary Bisson wrote:
(..)
> The patch looks fine however shouldn't it be pushed to u-boot directly?
> Also, as it can be changed through u-boot commands I'm not sure it is
> necessary.

Hi Gary,

How are you?

Now it's my turn to apologize for the very late answer; I am sorry.

About pushing to upstream u-boot; I am a bit reluctant to push this
patch to upstream u-boot because I think that booting to the /init
wrapper when using a ramdisk is a buildroot specificity (from fs/cpio/init).
  I certainly would not like to break the default behavior in upstream
u-boot, even in mfgtools mode, which is to call /linuxrc right now.

You are also right that the same functionality can be obtained from the
u-boot command line, but that means a user interaction. The goal of
adding this u-boot patch at buildroot level is to allow a
fully-automated boot of a buildroot filesystem through USB without user
interaction.
  (See [1] for more details on the whole procedure.)

What is your opinion on that, please?

Also, now that I have been very slow to answer to your e-mail, a nice
patches series from Luca has been around [2], which renames the config file.
  After a quick try, rebasing with git seems to be free, but do you
prefer that I send a v2 rebased on those, just in case?

Best regards,

V.

[1] https://community.freescale.com/docs/DOC-101842
[2] http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/92418

  reply	other threads:[~2014-09-03 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  8:49 [Buildroot] [PATCH] imx6sabresd: boot to /init in mfgtools mode Vincent Stehlé
2014-08-26  4:13 ` Gary Bisson
2014-09-03 17:14   ` Vincent Stehlé [this message]
2014-09-19 13:48 ` Luca Ceresoli

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=54074C87.7030807@freescale.com \
    --to=vincent.stehle@freescale.com \
    --cc=buildroot@busybox.net \
    /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.