From: "Jan Lübbe" <jlu@pengutronix.de>
To: Xavier Douville <barebox@douville.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Re: [PATCH 1/1] commands/ubi.c: Add support for VID header offset in ubiattach
Date: Fri, 15 Feb 2013 17:06:46 +0100 [thread overview]
Message-ID: <1360944406.3865.29.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <20130215155443.JPQP15122.toroondcbmts07-srv.bellnexxia.net@toip52-bus.srvr.bell.ca>
On Fri, 2013-02-15 at 10:54 -0500, Xavier Douville wrote:
> On 02/14/2013 11:23, Jan Lübbe wrote:
> >
> > Which kernel & barebox are you using?
> >
>
> I am using kernel 3.2.0 and barebox 2012.11.0.
> Both with patches from Phytec (phyCORE-AM335x-PD12.1.1).
I'm not sure if that barebox is different to the latest one regarding
the GPMC NAND support...
Does it actually fail on your board without this patch?
I have here:
...
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit), page size: 2048, OOB size: 64
...
barebox:/ devinfo nand0
resources:
driver: none
bus: none
Parameters:
size = 268435456
erasesize = 131072
writesize = 2048
oobsize = 64
barebox:/ ubiattach /dev/nand0.root
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
registering /dev/ubi0
registering root as /dev/ubi0.root
UBI: attached mtd0 to ubi0
UBI: MTD device name: "nand0.root"
UBI: MTD device size: 96 MiB
UBI: number of good PEBs: 768
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 33
UBI: total number of reserved PEBs: 735
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 15/8
barebox:/
So it figures out the VID offset correctly from the writesize of 2048.
Regards,
Jan
--
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
next prev parent reply other threads:[~2013-02-15 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 20:01 Xavier Douville
2013-02-11 9:19 ` Sascha Hauer
2013-02-11 15:14 ` Xavier Douville
2013-02-11 15:21 ` Sascha Hauer
2013-02-14 16:23 ` Jan Lübbe
2013-02-15 15:54 ` Xavier Douville
2013-02-15 16:06 ` Jan Lübbe [this message]
2013-02-15 16:58 ` Xavier Douville
2013-02-12 22:49 ` Marc Kleine-Budde
2013-02-12 22:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-02-13 9:00 ` Marc Kleine-Budde
2013-02-12 15:31 ` [PATCH] Do not print error message when successfully attaching more than one UBI device Xavier Douville
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=1360944406.3865.29.camel@coredoba.hi.pengutronix.de \
--to=jlu@pengutronix.de \
--cc=barebox@douville.org \
--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