From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: partitions
Date: Mon, 28 Feb 2011 09:57:57 +0100 [thread overview]
Message-ID: <201102280957.57164.jbe@pengutronix.de> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00D51@SRV-VS06.TELEVIC.COM>
Vanalme Filip wrote:
> I'm not that familiar with partitions in Barebox. On my i.MX27 board, I now
> have :
>
> barebox:/ devinfo
>
> devices:
> |----imx_serial0
> |----cs0
> |----ramfs0
> |----devfs0
> |----mem0 (defaultenv)
> |----mem1 (mem)
> |----imx_spi1
> |----mc137830 (pmic)
> |----mem2 (ram0)
> |----imx_nand0
> |----nand0 (nand0, nand_oob0, self_raw, env_raw, nand0.barebox,
> | nand0.bareboxenv, nand0.kernel, nand0.root) ----fec_imx0
> |----miidev0 (phy0)
> |----eth0
>
> drivers:
> imx_serial
> ramfs
> devfs
> fec_imx
> miidev
> imx_nand
> cfi_flash
> imx_spi
> imxfb
> mc13783
> mem
> barebox:/
>
> and :
>
> barebox:/ ls -l /dev
> cr-------- 4294967295 zero
> crw------- 6125 defaultenv
> crw------- 4294967295 mem
> crw------- 256 pmic
> crw------- 134217728 ram0
> crw------- 268435456 nand0
> cr-------- 8388608 nand_oob0
> crw------- 32 phy0
> crw------- 262144 self_raw
> crw------- 262144 self0
> crw------- 131072 env_raw
> crw------- 131072 env0
> crw------- 262144 nand0.barebox
> crw------- 131072 nand0.bareboxenv
> crw------- 2097152 nand0.kernel
> crw------- 265945088 nand0.root
> barebox:/
>
> I think this looks OK.
> However, I expected this to work (I took this from descriptions on the
> Internet...) :
>
> 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 ?)
'bb' means "Bad Block", and defines a layer that is bad block aware, and can
handle it in a correct manner.
Add "CONFIG_GLOB=y" to make a script work, that add the *.bb names to all
existing nand partitions.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-8766-939 228 |
Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-02-28 9:00 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 ` partitions Vanalme Filip
2011-02-28 15:05 ` partitions Vanalme Filip
2011-02-28 8:57 ` Juergen Beisert [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=201102280957.57164.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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