From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about dfu flash rootfs image
Date: Mon, 14 Oct 2013 15:08:02 +0800 [thread overview]
Message-ID: <525B9852.1050604@atmel.com> (raw)
In-Reply-To: <525B849F.3050805@denx.de>
Hi Heiko,
On 10/14/2013 13:43, Heiko Schocher wrote:
> Hello Bo,
>
> Am 12.10.2013 09:18, schrieb Bo Shen:
>> Hi All,
>> Now I am implementing DFU support on Atmel sama5d3xek board, when try
>> to download rootfs image to NAND flash through DFU, we need to drop
>> ffs from rootfs image.
>
> Do you use ubi or jffs2?
I tested with both ubi and jffs2 in raw mode.
>> In dfu_nand.c when it call nand_write_skip_bad() with flags as 0.
>> However, I need to call nand_write_skip_bad() with flags at least with
>> WITH_DROP_FFS set.
>>
>> Till now, I don't find any good solution to pass the parameter, except
>> hard code it or through "#ifdef CONFIG_CMD_NAND_TRIMFFS" to set it.
>> Any suggestions for it and any other solution?
>
> There was a discussion, how to reorganize the dfu_alt_info var, see:
>
> http://lists.denx.de/pipermail/u-boot/2013-July/158920.html
>
> I think, your question fits into this thread ...
>
> Currently, I think, you should add in
> drivers/dfu/dfu_nand.c:dfu_fill_entity_nand()
>
> a new "partdropffs" ? string, and set a marker like for "partubi"
> the dfu->data.nand.ubi var, and use this marker, where you need it ...
OK, I will wait the final decision.
Maybe for raw and ubi both need this option.
> bye,
> Heiko
Best Regards,
Bo Shen
prev parent reply other threads:[~2013-10-14 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 7:18 [U-Boot] Question about dfu flash rootfs image Bo Shen
2013-10-14 5:43 ` Heiko Schocher
2013-10-14 6:46 ` Lukasz Majewski
2013-10-14 7:08 ` Bo Shen [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=525B9852.1050604@atmel.com \
--to=voice.shen@atmel.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.