($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: JH <jupiter.hce@gmail.com>
Cc: Gabriele Zampieri <gabbla.malist@gmail.com>,
	Meta Freescale <meta-freescale@yoctoproject.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [yocto] Support UBI u-boot
Date: Mon, 17 Feb 2020 10:51:15 +0100	[thread overview]
Message-ID: <20200217095115.uyhdpgk6x2homrxs@qschulz> (raw)
In-Reply-To: <CAA=hcWSuVzWcGyMeOQY=tVPLiKMt4B83JhHwem1Jgp7bzkuPVg@mail.gmail.com>

Hi JH,

On Sun, Feb 09, 2020 at 08:01:15PM +1100, JH wrote:
> Changed to https://source.codeaurora.org/external/imx/uboot-imx.git
> branch imx_v2018.03_4.14.98_2.0.0_ga, it can now support
> CONFIG_CMD_MTDPARTS ind defconfg, all MTDPARTS error gone, but then
> 2018.03-r0/git/cmd/ubi.c missed dependencies of del_mtd_partitions,
> add_mtd_partitions, mtd_get_device_size all in mtdpart.c which can
> only be enabled by CONFIG_MTD_PARTITIONS:
> 
> obj-$(CONFIG_MTD_PARTITIONS) += mtdpart.o
> 
> But that CONFIG_MTD_PARTITIONS is not supported in defconfig.
> 
> Could anyone advise which branch works for UBI?
> 

FYI, U-boot was still slowly migrating to Kconfig only back then (maybe
still is). There was for a long time a mix between Kconfig options and
options in what I call board header files (include/configs/<board>.h).

Most likely CONFIG_MTD_PARTITIONS had to be defined there.

Biased recommendation: https://www.youtube.com/watch?v=5E0sdYkvq-Q

BR,
Quentin

  parent reply	other threads:[~2020-02-17  9:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  6:34 Support UBI u-boot JH
2020-02-06  7:02 ` [yocto] " 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               ` Quentin Schulz [this message]
     [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=20200217095115.uyhdpgk6x2homrxs@qschulz \
    --to=quentin.schulz@streamunlimited.com \
    --cc=gabbla.malist@gmail.com \
    --cc=jupiter.hce@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).