From: Nikita Kiryanov <nikita@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/4] ARM: imx: enhance support for the cm-fx6 module
Date: Thu, 14 Jul 2016 18:46:50 +0300 [thread overview]
Message-ID: <20160714154650.GA13093@arkadi-linux.compulab.local> (raw)
In-Reply-To: <f226f39a7503428f9af81c37d822a347@rwthex-s1-b.rwth-ad.de>
Hi Christopher, Stefano,
Whole series:
Acked-by: Nikita Kiryanov <nikita@compulab.co.il>
On Tue, Jul 12, 2016 at 11:37:33PM +0200, christopher.spinrath at rwth-aachen.de wrote:
> Hi,
>
> this is v2 of the series. To address the review comments of v1, v2 has an
> addtional patch (2/4) touching include/fdt_support.h (thus, I added Simon
> to the recipients).
>
> The original cover letter was (for a discussion cf. [2]):
>
> this series aims at enhancing support for the cm-fx6 module. In
> particular, with respect to the upstream linux kernel.
>
> The first patch improves the default environment. It is non-functional
> but makes it more convenient to adapt certain settings.
>
> The later two patches add mtd partition support for the on-board spi
> flash chip. They pick up the discussion about specifying a default
> partitioning in the device tree from here [1]. In short: adding the
> default partitioning to the device tree was rejected by the linux/
> device tree community during mainlining large parts of the device tree.
> It was proposed to implement the partition/mtd handling in u-boot.
> On the other hand, it was argued that the flash chip becomes some
> kind of "black-box" since there will be no partition labeling (in
> particular, with old u-boot versions).
>
> IMHO defining the mtd partitioning has the following (dis-)advantages:
>
> Advantages:
> - It is easier for the user to change the partitioning (e.g. to use
> the unsued 1MB free space).
>
> - The flash ship is used entirely for u-boot. So it is quite natural
> that u-boot manages it. Also, moving the partition table to it
> allows us to change the layout in future versions of u-boot (almost
> independently of the kernel - there are still non-device tree kernels).
>
> - U-Boot becomes the single point of definition for all device tree
> kernels. Otherwise, each kernel (vendor vs. upstream + version)
> would ship its own partitioning. Moreover, u-boot has to know
> something about the partitioning, too, because it has to know where
> the environment is saved.
>
> Disadvantages:
> - Users of the upstream linux kernel have to use a recent u-boot
> version to avoid the "black box" effect. A concrete impact is
> that the update routine (described/proposed by CompuLab) does
> not work out of the box with older u-boot versions.
>
> - Updating u-boot is something users might not want or miss to do.
>
> However, I think nowadays it is ok to demand a recent u-boot in
> combination with the upstream kernel. The cm-fx6 wouldn't be
> the first board doing so. Hence, I propose these patches here.
>
> Cheers,
> Christopher
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-June/434562.html
> [2] http://lists.denx.de/pipermail/u-boot/2016-June/258546.html
>
prev parent reply other threads:[~2016-07-14 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:37 [U-Boot] [PATCH v2 0/4] ARM: imx: enhance support for the cm-fx6 module christopher.spinrath at rwth-aachen.de
2016-07-14 15:46 ` Nikita Kiryanov [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=20160714154650.GA13093@arkadi-linux.compulab.local \
--to=nikita@compulab.co.il \
--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