From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Enable ubi and ubifs support
Date: Fri, 11 Dec 2015 17:25:59 +0800 [thread overview]
Message-ID: <1449825959.2199.2.camel@altera.com> (raw)
In-Reply-To: <1449825590-2735-1-git-send-email-clsee@altera.com>
Hi Marek,
On Fri, 2015-12-11 at 17:19 +0800, Chin Liang See wrote:
> When QSPI and NAND is enabled, the ubi and ubifs support
> will be enabled too.
>
> Signed-off-by: Chin Liang See <clsee@altera.com>
> Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> Cc: Dinh Nguyen <dinh.linux@gmail.com>
> Cc: Pavel Machek <pavel@denx.de>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Stefan Roese <sr@denx.de>
> ---
> include/configs/socfpga_common.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/configs/socfpga_common.h
> b/include/configs/socfpga_common.h
> index b3f65b6..a07017b 100644
> --- a/include/configs/socfpga_common.h
> +++ b/include/configs/socfpga_common.h
> @@ -274,6 +274,14 @@ unsigned int
> cm_get_qspi_controller_clk_hz(void);
> #define CONFIG_SYS_CONSOLE_ENV_OVERWRITE
> #define CONFIG_ENV_SIZE 4096
>
> +/* UBIFS support */
> +#if defined(CONFIG_CMD_SF) || defined(CONFIG_CMD_NAND)
> +#define CONFIG_CMD_UBI
> +#define CONFIG_CMD_UBIFS
> +#define CONFIG_RBTREE
> +#define CONFIG_LZO
> +#endif
> +
I have issue on ubifsmount my ubinized image. I suspect it might
created wrongly. The code is ok based on previous patches and the one
you sent to me. Wonder you might able to validate with your working
ubinized image?
Thanks in advance!
Chin Liang
> /*
> * SPL
> *
> --
> 1.9.2.468.g3f0c02a
>
next prev parent reply other threads:[~2015-12-11 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 9:19 [U-Boot] [PATCH] arm: socfpga: Enable ubi and ubifs support Chin Liang See
2015-12-11 9:25 ` Chin Liang See [this message]
2015-12-11 14:26 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2015-12-21 15:22 Chin Liang See
2015-12-21 23:12 ` Marek Vasut
2015-12-22 0:20 ` Chin Liang See
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=1449825959.2199.2.camel@altera.com \
--to=clsee@altera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox