public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: How much flash space should I reserve for device tree blobs?
Date: Tue, 16 Dec 2014 13:44:58 +0100	[thread overview]
Message-ID: <94604137.TN9zLIKKd4@wuerfel> (raw)
In-Reply-To: <20141216122224.GG967@titan.lakedaemon.net>

On Tuesday 16 December 2014 07:22:24 Jason Cooper wrote:
> 
> On Mon, Dec 15, 2014 at 03:33:50PM -0500, Brian Hutchinson wrote:
> > Reflecting back on the famous quote of "Nobody needs more than 640K",
> > how much space should I reserve in flash to 'future proof' my MTD map
> > in regards to dtb's?
> > 
> > Looking at the current flavors of dtb's built in a recent mainline
> > kernel, the biggest one I see is 66K.
> > 
> > How big do you all see these getting?  I know, it's probably a loaded
> > question.  Would just like to bounce this off the list as a sanity
> > check ... measure twice cut once kind of thing.
> 
> There's probably better folks to answer this than me (former powerpc
> folks, eg Arnd, Olof), but since I've had to consider it as well, I'll
> tell you my thoughts.

I thought that these days a lot of boot loaders can just access file
systems. If you use a FAT or ext4 file system (on block based storage)
or something like UBI (on raw flash) to store both the kernel and DT,
you should be able to avoid hardcoding sizes.

It also depends on how much space you have total. On an eMMC, I would
just round up to whole megabytes, but if you have only 4MB of NOR flash
available, you have to be more conservative.

	Arnd

  reply	other threads:[~2014-12-16 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 20:33 How much flash space should I reserve for device tree blobs? Brian Hutchinson
2014-12-16 12:22 ` Jason Cooper
2014-12-16 12:44   ` Arnd Bergmann [this message]
2014-12-16 19:19 ` Robert Schwebel

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=94604137.TN9zLIKKd4@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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