From: "JH" <jupiter.hce@gmail.com>
To: Meta Freescale <meta-freescale@yoctoproject.org>,
Yocto discussion list <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Support UBI u-boot
Date: Thu, 6 Feb 2020 17:34:55 +1100 [thread overview]
Message-ID: <CAA=hcWSCZROrpDBWV5ZAA+LV6j0cjRSKxyjonOfWS4mCZAtdHg@mail.gmail.com> (raw)
Hi,
Sorry for cross-posting, I have been asking for helping solving the
issue many days ago, but could not get those work.
(1) UBI support
I added NAND and UBIFS support to my Yocto layer machine config file:
UBOOT_CONFIG = "nand"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
UBOOT_CONFIG[nand] += "ubi"
UBOOT_CONFIG[nand] += "ubifs"
But my u-boot.imx-nand still could not support ubi:
=> ubi part rootfs
Unknown command 'ubi' - try 'help'
What I could be missing here?
(2) Patch u-boot parameters
I am not clear how you do to change u-boot parameters, it seems to me
I have to create my own u-boot-imx_2017.03.bbappend and patch files to
mx6ullevk.h, to change u-boot parameters of mtdparts, NAND_ROOT_UBI,
bootcmd, etc based on my configuration.
But Yocto won't allow the patch running unless that the patch is
committed to the git repository in
https://source.codeaurora.org/external/imx/uboot-imx.git.
Ideally, I thought all u-boot parameters can be changed in a bbappend
file, could you advise if it is possible to do that way or not? If so,
how to do it?
If not, what is the policy for making parches and commit to the git
repository https://source.codeaurora.org/external/imx/uboot-imx.git?
Thank you.
Kind regards,
- jh
next reply other threads:[~2020-02-06 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 6:34 JH [this message]
2020-02-06 7:02 ` [yocto] Support UBI u-boot Gabriele
2020-02-06 10:07 ` JH
2020-02-06 10:39 ` JH
2020-02-06 11:11 ` Gabriele
2020-02-07 1:55 ` JH
2020-02-07 14:13 ` Gabriele
2020-02-09 6:23 ` JH
2020-02-09 9:01 ` JH
2020-02-09 11:13 ` JH
2020-02-17 9:51 ` [OE-core] " Quentin Schulz
[not found] ` <em86bbcd60-f004-4acb-b508-4471dac5c7c1@andys-imac.leeshillfarm.local>
2020-02-07 4:32 ` JH
[not found] ` <c159fe1d7cc14f5c80878fe81a957bb4@tagmaster.com>
2020-02-07 8:52 ` [yocto] " JH
2020-02-07 11:55 ` [OE-core] " Quentin Schulz
2020-02-07 13:01 ` JH
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='CAA=hcWSCZROrpDBWV5ZAA+LV6j0cjRSKxyjonOfWS4mCZAtdHg@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=u-boot@lists.denx.de \
--cc=yocto@yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).