From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: partitions
Date: Mon, 28 Feb 2011 09:57:04 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00D61@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20110228084753.GH2667@jasper.tkos.co.il>
> -----Original Message-----
> From: Baruch Siach [mailto:baruch@tkos.co.il]
> Sent: maandag 28 februari 2011 9:48
> To: Vanalme Filip
> Cc: barebox@lists.infradead.org
> Subject: Re: partitions
>
> HI Vanalme,
>
> On Mon, Feb 28, 2011 at 09:36:14AM +0100, Vanalme Filip wrote:
> > barebox:/ erase /dev/nand0.kernel.bb
> > stat /dev/nand0.kernel.bb: No such file or directory
> > barebox:/
> >
> > and
> >
> > barebox:/ tftp zImage /dev/nand0.kernel.bb
> > open: Read-only file system
> > barebox:/
> >
> >
> > Is there any documentation that handles/describes this ? (e.g. what's the
> extension .bb ?)
>
> The .bb extension means a bad block aware partition. Use the 'nand -a' command
> to create one from a raw NAND partition, e.g. 'nand -a /dev/nand0.kernel'.
>
> baruch
[Filip] Thanks !
>
> --
> ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-02-28 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 8:36 partitions Vanalme Filip
2011-02-28 8:47 ` partitions Baruch Siach
2011-02-28 8:57 ` Vanalme Filip [this message]
2011-02-28 15:05 ` partitions Vanalme Filip
2011-02-28 8:57 ` partitions Juergen Beisert
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=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00D61@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.com \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/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