public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] kirkwood (openrd): saveenv will not work with environment in NAND
Date: Wed, 30 Sep 2009 10:17:51 +0200	[thread overview]
Message-ID: <20090930101751.2fcf29b5@marrow.netinsight.se> (raw)
In-Reply-To: <200909301015.35321.dk-arm-linux@gmx.de>

On Wed, 30 Sep 2009 10:15:35 +0200
Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:

> > > is there anywhere a document how to build open source u-boot for sheevaplug which explains all these details?
> > > (haven't found some documentation about this)
> > 
> > (Wearing my Prafulla hat): I guess this should be described on the
> > plugwiki:
> > 
> >   http://www.openplug.org/plugwiki/index.php/Das_U-boot_plug_support#Open_U-boot_support_for_SheevaPlug
> Yes - I know this page but there are no information regarding the latest u-boot changes (e.g. openrd support, movement from git.marvell.com to denx , the
> toolchain problems...)

It's a wiki (hint, hint!) :-)

// Simon

  reply	other threads:[~2009-09-30  8:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 13:55 [U-Boot] kirkwood (openrd): saveenv will not work with environment in NAND Dieter Kiermaier
2009-09-29 15:16 ` Dieter Kiermaier
2009-09-30  6:21   ` Simon Kagstrom
2009-09-30  7:02     ` Dieter Kiermaier
2009-09-30  7:08       ` Simon Kagstrom
2009-09-30  7:40         ` Dieter Kiermaier
2009-09-30  7:57           ` Simon Kagstrom
2009-09-30  8:15             ` Dieter Kiermaier
2009-09-30  8:17               ` Simon Kagstrom [this message]
2009-09-30  8:25                 ` Dieter Kiermaier
2009-09-30  9:28                   ` [U-Boot] Flash sanity checks Prafulla Wadaskar
2009-09-30  9:58                     ` Dieter Kiermaier
2009-09-30 12:19                       ` Stefan Roese
2009-10-06 17:16                   ` [U-Boot] kirkwood (openrd): saveenv will not work with environment in NAND Prafulla Wadaskar
2009-09-30 20:32             ` Wolfgang Denk
2009-10-01  7:29               ` [U-Boot] [PATCH] Make arm926ejs use -mabi=apcs-gnu to avoid EABI problems Simon Kagstrom
2009-10-01  9:56                 ` Prafulla Wadaskar
2009-10-01 18:27                   ` Wolfgang Denk
2009-10-02 14:44                     ` Simon Kagstrom
2009-10-05 13:23                     ` [U-Boot] [PATCH] arm926ejs: 16-byte align stack to avoid LDRD/STRD problems Simon Kagstrom
2009-10-05 14:30                       ` Andrew Dyer
2009-10-05 14:35                         ` Stefan Roese
2009-10-05 14:53                           ` [U-Boot] [PATCH v2] " Simon Kagstrom
2009-10-05 15:44                             ` Dieter Kiermaier
2009-10-05 18:37                             ` Tom
2009-10-06  7:07                               ` Simon Kagstrom
2009-10-05 22:07                             ` Måns Rullgård
2009-10-06  4:13                             ` Prafulla Wadaskar
2009-10-06  6:44                             ` [U-Boot] [PATCH v3] arm926ejs: 8-byte " Simon Kagstrom
2009-10-06 16:50                               ` Tom
2009-10-18  2:15                               ` Tom
2009-10-05 14:40                         ` [U-Boot] [PATCH] arm926ejs: 16-byte " Simon Kagstrom

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=20090930101751.2fcf29b5@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --cc=u-boot@lists.denx.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