mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Boaz Ben-David <boaz.bd@wellsense-tech.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: bareboxenv usage
Date: Tue, 13 Sep 2011 11:59:03 +0300	[thread overview]
Message-ID: <4E6F1B57.7060507@wellsense-tech.com> (raw)
In-Reply-To: <4E6E0F25.7060403@wellsense-tech.com>

On 09/12/11 16:54, Boaz Ben-David wrote:
> Hi
>
> I am using bareboxenv on a MLC NAND chip for reading and writing the
> barebox environment on my imx35 board.
> Up until now I have been using it with the mtdblock devices and suddenly
> I noticed I get an error while reading (-l) the env(I/O error).
> Using bareboxenv with the same partition but in the /dev/mtd form the
> read works.
> For some reason I assumed that I need to use the bareboxenv with
> mtdblock devices.
> Question is, what is the CORRECT way to use it on a nand partition?
>
> Thanks,
>
> Boaz.
>
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

I see no one answered this, maybe I need to shorten my question (:

All I am asking is: do I need to use /dev/mtdblock or /dev/mtd when 
loading and saving envs

with bareboxenv?


Thanks,

Boaz.


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

  reply	other threads:[~2011-09-13  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 13:54 Boaz Ben-David
2011-09-13  8:59 ` Boaz Ben-David [this message]
2011-09-13  9:14   ` Marc Kleine-Budde
2011-09-13  9:48     ` Boaz Ben-David
2011-09-13 11:25       ` Boaz Ben-David
2011-09-13 12:00         ` Marc Kleine-Budde
2011-09-13 12:01       ` Marc Kleine-Budde
2011-09-13 12:07         ` Boaz Ben-David

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=4E6F1B57.7060507@wellsense-tech.com \
    --to=boaz.bd@wellsense-tech.com \
    --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