From: christian.buettner@rafi.de
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Antwort: Re: barebox image size
Date: Mon, 16 Jul 2012 11:15:24 +0200 [thread overview]
Message-ID: <OFCC857403.C150E96B-ONC1257A3D.003283FD-C1257A3D.0032D943@o0802.rafi.inhouse> (raw)
In-Reply-To: <20120716085418.GG30009@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2267 bytes --]
i am using:
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@pengutronix.de>
An: christian.buettner@rafi.de,
Kopie: barebox@lists.infradead.org
Datum: 16.07.2012 10:54
Betreff: Re: barebox image size
On Mon, Jul 16, 2012 at 10:37:41AM +0200, christian.buettner@rafi.de
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 |
[-- Attachment #1.2: Type: text/html, Size: 7797 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-07-16 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 8:37 christian.buettner
2012-07-16 8:54 ` Sascha Hauer
2012-07-16 9:15 ` christian.buettner [this message]
2012-07-16 9:20 ` Eric Bénard
2012-07-16 9:21 ` Antwort: " Sascha Hauer
2012-07-16 9:37 ` Antwort: " christian.buettner
2012-07-16 10:30 ` Sascha Hauer
2012-07-16 12:17 ` Antwort: " christian.buettner
2012-07-16 13:47 ` Christian Kapeller
2012-07-16 13:52 ` Antwort: " christian.buettner
2012-07-16 14:25 ` Christian Kapeller
2012-07-16 14:30 ` Antwort: " christian.buettner
2012-07-16 14:32 ` Eric Bénard
2012-07-16 22:29 ` Antwort: Re: Antwort: Re: Antwort: " Marc Reilly
2012-07-17 9:58 ` Antwort: " christian.buettner
2012-07-17 10:44 ` Marc Reilly
2012-07-17 10:49 ` Antwort: " christian.buettner
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=OFCC857403.C150E96B-ONC1257A3D.003283FD-C1257A3D.0032D943@o0802.rafi.inhouse \
--to=christian.buettner@rafi.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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