static inline struct device_d *imx53_add_nand(struct imx_nand_platform_data *pdata)
{
struct resource res[] = {
{
.start = MX53_NFC_BASE_ADDR,
.size = SZ_4K,
.flags = IORESOURCE_MEM,
}, {
.start = MX53_NFC_AXI_BASE_ADDR,
.size = SZ_4K,
.flags = IORESOURCE_MEM,
},
};
struct device_d *dev = xzalloc(sizeof(*dev));
dev->resource = xzalloc(sizeof(struct resource) * ARRAY_SIZE(res));
memcpy(dev->resource, res, sizeof(struct resource) * ARRAY_SIZE(res));
dev->num_resources = ARRAY_SIZE(res);
strcpy(dev->name, "imx_nand");
dev->id = -1;
dev->platform_data = pdata;
register_device(dev);
return dev;
}
with imx_nand_platform_data parameter:
static struct imx_nand_platform_data tx53_nand_pdata =
{
.width = 1,
.hw_ecc = 1,
.flash_bbt = 1,
};
imx_nand_load_image() is never used in my imx53 board init code.. is this the fault?
- christian
Von: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
An: christian.buettner@xxxxxxx,
Kopie: barebox@xxxxxxxxxxxxxxxxxxx
Datum: 16.07.2012 10:54
Betreff: Re: barebox image size
On Mon, Jul 16, 2012 at 10:37:41AM +0200, christian.buettner@xxxxxxx wrote:
> hi,
>
> we need to implement a lot of features into the barebox. Finally the size
> of the image will be bigger than the standard max of 256K.
> When i flash an image, bigger than 256K to nand, barebox does not boot
> anymore - if i reduce it to 256K or smaller, everthing works fine.
>
> What do i have to do to use a bigger barebox image size?
Just a guess:
You are using imx_nand_load_image() with a fixed size of 256k. grep for
this function in the current tree and see how the correct image size is
calculated.
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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
