public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] cmd: mtdparts: support runtime generated mtdparts
Date: Mon, 6 Jun 2016 23:21:03 +0200	[thread overview]
Message-ID: <20160606212103.GA5686@localhost.localdomain> (raw)
In-Reply-To: <CAOMqctS79ppigcmTByCZDyue-vb_h2yJUoeXa1q9x7fGz353fA@mail.gmail.com>

On Mon, Jun 06, 2016 at 08:50:55PM +0200, Michal Suchanek wrote:
> On 6 June 2016 at 09:48, Ladislav Michl <ladis@linux-mips.org> wrote:
[snip]
> > Okay, specifing size in therms of eraseblock would solve my problem
> > and I have to admit I'm not aware such a thing exists. Any pointer to
> > the patch introducing that change?
> >
> 
> I am not aware of any. it's on the list of nice to have things I will
> probably not get to,
> 
> Anyway, It's imho the place to put this code so that Linux does not
> depend on u-boot for pre-chewing it's partition table to get the
> partitions right.

Linux already depends on U-Boot as U-Boot feeds Linux with MTD partitions.
So this patch does not introduce any change in this regard. And whenever
are paritions altered by user, saved to U-Boot environment or default
layout provided according actual eraseblock size is just not important
here. In the end both U-Boot and Linux are working with the same partition
layout. This is the only thing that matters and this patch does not change
that. It changes only this: instead of hardcoding default layout into string
provided at compile time, there is now posibility to create that string
runtime. That's all.

And now... Your recomended solution is to change both U-Boot and Linux
to understand partition layout based on indexes and sizes expressed
in eraseblocks. While size of SPL could be nicely evaluated in terms
of eraseblocks, it is a bit more complicated with kernel partition,
because 10 eraseblocks says nothing about partition size, therefore
you cannot say whenever kernel will fit that space without knowledge
of eraseblock size. So you just reverted the problem and both U-Boot
and Linux would end with more code to be maintained for compatibility.

Best regards,
	ladis

  reply	other threads:[~2016-06-06 21:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 17:34 [U-Boot] [PATCH 0/6] cmd: mtdparts: Add support for runtime generated defaults Ladislav Michl
2016-06-05 17:38 ` [U-Boot] [PATCH 1/6] cmd: mtdparts: fix mtdparts variable presence confusion in mtdparts_init Ladislav Michl
2016-06-05 17:40 ` [U-Boot] [PATCH 2/6] cmd: mtdparts: fix null pointer dereference in parse_mtdparts Ladislav Michl
2016-06-05 17:41 ` [U-Boot] [PATCH 3/6] cmd: mtdparts: consolidate mtdparts reading from env Ladislav Michl
2016-06-05 17:42 ` [U-Boot] [PATCH 4/6] cmd: mtdparts: use defaults by default Ladislav Michl
2016-06-05 17:43 ` [U-Boot] [PATCH 5/6] cmd: mtdparts: support runtime generated mtdparts Ladislav Michl
2016-06-05 17:58   ` Michal Suchanek
2016-06-05 18:23     ` Ladislav Michl
2016-06-06  7:08       ` Michal Suchanek
2016-06-06  7:48         ` Ladislav Michl
2016-06-06 18:50           ` Michal Suchanek
2016-06-06 21:21             ` Ladislav Michl [this message]
2016-06-07  7:43               ` Michal Suchanek
2016-06-07 13:08                 ` Ladislav Michl
2016-06-05 17:43 ` [U-Boot] [PATCH 6/6] igep00x0: generate default mtdparts according NAND chip used Ladislav Michl

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=20160606212103.GA5686@localhost.localdomain \
    --to=ladis@linux-mips.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