mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Zoltán Kócsi" <zoltan@bendor.com.au>
To: barebox@lists.infradead.org
Subject: More Mini2440 questions...
Date: Mon, 4 Apr 2011 21:02:45 +1000	[thread overview]
Message-ID: <20110404210245.16f269f7@manocska.bendor.com.au> (raw)

Thanks for all the answers for my previous questions!

The 'next' branch indeed boots from the NAND FLASH like a charm.

What I'm looking for now is a crash-course, or at least a pointer to
some web-based one, on barebox itself, from the usage point of view. I
created the docs and read the User's Manual, but I'm none the wiser. 

How do I boot a kernel from FLASH or via TFTP? I figured that I
can set the Ethernet MAC address by eth0.ethaddr=xx:xx:xx:xx:xx:xx
(although I don't know if that actually changes the MAC) but how can I
save that so that next time I reset the board it is there? 

Same with other environment variables, such as bootargs. The command
'saveenv' says that it saved the environment. According to its docs, it
saved it in /dev/env0. According the the docs of loadenv, that
command should load the saved environment, but I could not get any
of my changes back.

Any help regarding to how to use barebox would be most welcome.

Thanks,

Best Regards,

Zoltan


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2011-04-04 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 11:02 Zoltán Kócsi [this message]
2011-04-04 11:13 ` Juergen Beisert
2011-04-04 12:13   ` Zoltán Kócsi
2011-04-04 12:26     ` Juergen Beisert
2011-04-04 12:52       ` Marc Kleine-Budde
2011-04-05  3:09         ` Zoltán Kócsi
2011-04-05  3:07       ` Zoltán Kócsi

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=20110404210245.16f269f7@manocska.bendor.com.au \
    --to=zoltan@bendor.com.au \
    --cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox