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: Passing kernel arguments - SAMA5D4EK
Date: Thu, 5 Feb 2015 15:19:08 -0700	[thread overview]
Message-ID: <CA+nEJinMJqBSaFBkAY26gb1SEueL+Fb_B7GCCM-tJLq+9NfQLA@mail.gmail.com> (raw)
In-Reply-To: <CA+nEJingM_3v2-d2OpOfARc-G6sVG_GFzjDh60xXQM4=2tgzSQ@mail.gmail.com>

Sascha,

Have you had a chance to look into what I need to do to convert to the
new environment?

Also, would it be beneficial to add the ability to load more than one
partition to the bootargs for the old environment setup?  I've almost
finished the boot script modifications to allow for it while still
being backwards compatible.  I can push it back up to the repository
when finished if interested.

Doug

On Tue, Feb 3, 2015 at 2:07 PM, Doug Brainard
<dbrainard@brainardinsight.com> wrote:
>> It comes from /env/bin/boot. You can checkout the sourcecode and grep
>> for it since we do not have any search function in barebox.
>
> Ah, that's the piece I was missing to understand how the bootargs were
> being created and what keywords did what.
>
>> Thanks. I'll prepare a mail tomorrow.
>
> I'll press pause on what I'm doing with this then, and I'll wait on
> receiving that.
>
> Thanks again for your help,
>
> Doug
>
>
> On Tue, Feb 3, 2015 at 12:33 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>> On Tue, Feb 03, 2015 at 10:21:45AM -0700, Doug Brainard wrote:
>>> > Couldn't you add "ubi.mtd=8 ubi.mtd=9" and rootfs_mtdblock_nand=10
>>> > instead?
>>>
>>> I had thought that barebox had a need to know where the rootfs was
>>> located, which is why I hadn't tried that.  Turns out that it worked
>>> perfectly for the ubi.mtd settings.  Thank you!  Any idea how
>>> "noinitrd" is getting added to the bootargs?  I need to replace that
>>> with a "rw".
>>
>> It comes from /env/bin/boot. You can checkout the sourcecode and grep
>> for it since we do not have any search function in barebox.
>>
>>>
>>> > Note that we started with trying to build a generic default environment
>>> > which at some point grew into a monster. We now have the 2nd version of
>>> > the generic default environment which is much better. Unfortunately
>>> > usage of this new default environment is board specific and your board
>>> > isn't converted yet. If you are interested I can show you the steps to
>>> > convert it.
>>>
>>> I would be interested in helping with this conversion.
>>
>> Thanks. I'll prepare a mail tomorrow.
>>
>> 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-05 22:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:58 Doug Brainard
2015-02-03  8:59 ` Sascha Hauer
2015-02-03  9:16   ` Bo Shen
2015-02-03 17:21     ` Doug Brainard
2015-02-03 19:33       ` Sascha Hauer
2015-02-03 21:07         ` Doug Brainard
2015-02-05 22:19           ` Doug Brainard [this message]
2015-02-06  7:35             ` Sascha Hauer
2015-02-06  7:33     ` Sascha Hauer
2015-02-07 18:55       ` Doug Brainard
2015-02-09  7:36         ` Sascha Hauer
2015-02-10  5:05           ` Doug Brainard
2015-02-10  9:48             ` 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+nEJinMJqBSaFBkAY26gb1SEueL+Fb_B7GCCM-tJLq+9NfQLA@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