* How much flash space should I reserve for device tree blobs?
@ 2014-12-15 20:33 Brian Hutchinson
2014-12-16 12:22 ` Jason Cooper
2014-12-16 19:19 ` Robert Schwebel
0 siblings, 2 replies; 4+ messages in thread
From: Brian Hutchinson @ 2014-12-15 20:33 UTC (permalink / raw)
To: linux-arm-kernel
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.
Regards,
Brian
^ permalink raw reply [flat|nested] 4+ messages in thread
* How much flash space should I reserve for device tree blobs?
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
2014-12-16 19:19 ` Robert Schwebel
1 sibling, 1 reply; 4+ messages in thread
From: Jason Cooper @ 2014-12-16 12:22 UTC (permalink / raw)
To: linux-arm-kernel
Hey Brian,
+Arnd, Olof.
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.
The biggest unknown is the addition of binary blobs. If those are a
consideration for your board(s), then you need to reserve quite a bit
more space.
For example, a binding update could start including the firmware for an
SD wifi card. However, in the interest of retaining backwards
compatibility, Linux would still be able to load from /lib/firmware.
So, if you couldn't update your dtb, you'd still have a working wifi
card.
If you aren't concerned about binary blobs, then I'd say you're fine
with 128k or so.
Most of the scenarios I had were with 2MB NOR flash. barebox is usually
in the range of 200k, and there isn't enough room left for the kernel,
so I had plenty for the environment and the dtb.
hth,
Jason.
^ permalink raw reply [flat|nested] 4+ messages in thread
* How much flash space should I reserve for device tree blobs?
2014-12-16 12:22 ` Jason Cooper
@ 2014-12-16 12:44 ` Arnd Bergmann
0 siblings, 0 replies; 4+ messages in thread
From: Arnd Bergmann @ 2014-12-16 12:44 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* How much flash space should I reserve for device tree blobs?
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 19:19 ` Robert Schwebel
1 sibling, 0 replies; 4+ messages in thread
From: Robert Schwebel @ 2014-12-16 19:19 UTC (permalink / raw)
To: linux-arm-kernel
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.
With barebox, we put the devicetree into the root filesystem and search
it via an freedesktop.org bootspec entry these days.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-12-16 19:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-12-16 19:19 ` Robert Schwebel
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 NNTP newsgroup(s).