From: Sascha Hauer <s.hauer@pengutronix.de>
To: Victor Rodriguez <vm.rod25@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Beagleboard and barebox problem
Date: Tue, 26 Oct 2010 05:39:58 +0200 [thread overview]
Message-ID: <20101026033958.GD6017@pengutronix.de> (raw)
In-Reply-To: <AANLkTimNiUjRq3GLNNa0gYRGGZjLaTrWbsNRKPU9=1mw@mail.gmail.com>
Hi Victor,
> I fix the problem of envfs: wrong magic on /dev/env0 with your thread
>
> http://www.mail-archive.com/u-boot-users@lists.sourceforge.net/msg10197.html
>
> And every thing works fine
>
> uboot> addpart /dev/nand0 256k(uboot),128k(env),2048k(kernel),-(rootfs)
I think on the beagle board the first space in Nand is occupied by the
xloader and xloader itself expects the second stage loader at offset
512k, but I don't know the exact situation off my head. Michael, maybe
you can comment on this?
>
> setenv bootargs console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
> rootfstype=ext2 rw rootdelay=1 nohz=off
>
> But is not working for bare box
>
> How do you save the boot args ?
have a look at /env/config (using the edit command). Every file there is
saved into the environment using saveenv.
>
> The next step will be
>
> uboot> tftp uImage-mx27ads /dev/nand0.kernel.bb
>
> And the same for a ram disk File System in the nand0.rootfs.bb right ?
Right, dont forget to erase the partitions with 'erase
/dev/nand0.kernel.bb' beforehand, otherwise you'll have garbage in your
nand.
>
> And
>
> uboot> bootm /dev/nand0.kernel.bb
In principle, yes. The normal process is to simply run 'boot' which is a
script under /env/bin. This will setup things like the commandline
correctly.
>
> But my second question is How the kernel know were is the File
> System, where should I set something similar to boot args ?
Have a look at the files under /env, I think this will answer your
questions (we have ls, cat and edit for this).
I'm sorry the situation on the beagle board is still a bit rough and
unclear. I hope we find time working on this.
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
next prev parent reply other threads:[~2010-10-26 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 17:55 Victor Rodriguez
2010-10-22 7:05 ` Sascha Hauer
2010-10-25 22:29 ` Victor Rodriguez
2010-10-26 3:39 ` Sascha Hauer [this message]
2010-10-26 4:07 ` Victor Rodriguez
2010-10-26 18:34 ` 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=20101026033958.GD6017@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=vm.rod25@gmail.com \
/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