mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Doug Brainard <dbrainard@brainardinsight.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method.
Date: Wed, 11 Feb 2015 09:53:25 -0700	[thread overview]
Message-ID: <CA+nEJik9t78SE16mv4a5kexSYStQ+6n5Rvx-wYQrxSfB4DUsAA@mail.gmail.com> (raw)
In-Reply-To: <20150211084315.GJ12209@pengutronix.de>

Sascha,

>> bootargs.base is unused, this file should be removed.

My next patch attempt will have "bootargs.base" removed, and it will
attempt to boot from "nand" and then fall back to "net" if the nand is
not programmed.

Just waiting on clarification on the "nand0." question when you get in tomorrow.

Thanks,

Doug

On Wed, Feb 11, 2015 at 1:43 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Wed, Feb 11, 2015 at 10:34:32AM +0800, Bo Shen wrote:
>> >diff --git a/arch/arm/boards/sama5d4ek/env/nv/bootargs.base b/arch/arm/boards/sama5d4ek/env/nv/bootargs.base
>> >new file mode 100644
>> >index 0000000..476b1fb
>> >--- /dev/null
>> >+++ b/arch/arm/boards/sama5d4ek/env/nv/bootargs.base
>> >@@ -0,0 +1 @@
>> >+console=ttyS0,115200
>>
>> Till now, I don't know the difference between "bootargs.base" (here
>> maybe linux.bootargs.base (?)) and "linux.bootargs.console"
>
> bootargs.base is unused, this file should be removed.
>
> 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

  reply	other threads:[~2015-02-11 16:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 14:28 [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Doug Brainard
2015-02-10 14:28 ` [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method Doug Brainard
2015-02-11  2:34   ` Bo Shen
2015-02-11  4:00     ` Doug Brainard
2015-02-11  5:06       ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  7:26         ` Bo Shen
2015-02-11  8:35           ` Sascha Hauer
2015-02-11  8:54             ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  9:12               ` Eric Bénard
2015-02-11  9:19               ` Sascha Hauer
2015-02-11 12:03                 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 14:33                   ` Sascha Hauer
2015-02-11  8:43     ` Sascha Hauer
2015-02-11 16:53       ` Doug Brainard [this message]
2015-02-11 16:38     ` Doug Brainard
2015-02-11 17:39       ` Doug Brainard
2015-02-12  9:13         ` Sascha Hauer
2015-02-13  2:57           ` Doug Brainard
2015-02-13  5:32           ` Doug Brainard
2015-02-11  1:30 ` [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Bo Shen
2015-02-11  4:02   ` Doug Brainard
2015-02-11  7:23     ` Bo Shen
2015-02-11  5:04 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11  7:42   ` Sascha Hauer

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=CA+nEJik9t78SE16mv4a5kexSYStQ+6n5Rvx-wYQrxSfB4DUsAA@mail.gmail.com \
    --to=dbrainard@brainardinsight.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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