mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nataraj S Narayan <natarajsn@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Barebox: Nand flash
Date: Sat, 28 Aug 2010 16:13:26 +0200	[thread overview]
Message-ID: <20100828141326.GH1473@pengutronix.de> (raw)
In-Reply-To: <AANLkTikVJ7wU7neSsep=OG23tstrv4f=LpQ_YptFu1Cd@mail.gmail.com>

On Sat, Aug 28, 2010 at 05:45:17PM +0530, Nataraj S Narayan wrote:
> Hi
> 
> on commit a74a26f25477ec65229a57ca15e0f2c56396c69a
> 
> I don't find nand0.rootfs.
> 
> 9263-EK:/  ls /dev/
> 
> /dev/zero           /dev/defaultenv     /dev/mem
> /dev/ram0           /dev/nand0          /dev/nand_oob0
> /dev/phy0           /dev/self_raw       /dev/self0
> /dev/env_raw        /dev/env0

/dev/nand0 is there, so there's only partitioning missing. Try something
like

addpart /dev/nand0 256k(barebox),256k(bareboxenv),2M(kernel),-(rootfs)
nand -a /dev/nand0.*

Normally your environment does this for you.

Note that /dev/nand0.rootfs is not intended for direct use, instead use
/dev/nand0.rootfs.bb. The .bb devices automatically skip bad blocks
while writing on it or reading from it.

Regards,
  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:[~2010-08-28 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 12:15 Nataraj S Narayan
2010-08-28 14:13 ` Sascha Hauer [this message]

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=20100828141326.GH1473@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=natarajsn@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