devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Hector Palacios <hector.palacios-i7dp0qKlBMg@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Options to store device tree blob on NAND Flash
Date: Mon, 15 Apr 2013 14:28:41 +0100	[thread overview]
Message-ID: <20130415132841.1F8FD3E0AA8@localhost> (raw)
In-Reply-To: <5148812D.4090305-i7dp0qKlBMg@public.gmane.org>

On Tue, 19 Mar 2013 16:15:57 +0100, Hector Palacios <hector.palacios-i7dp0qKlBMg@public.gmane.org> wrote:
> Hello,
> 
> For embedded devices where NAND flash is the only storage media, I was wondering what 
> are the existing approaches on how to store the device tree blob in flash.
> Searching on the Internet I have found only two approaches:
>   1. Have a dedicated MTD partition for the device tree blob (raw).
>   2. Have a UBI volume on a partition and store the device tree blob as a file in a 
> UBIFS partition (this approach also stores the kernel image as a file in the same or 
> different volume).
> 
> Is anybody using other approach for storing the DTB in flash?
> What method is more widely used in embedded devices?

Either if fine providing U-Boot (or whatever) is able to read it. Having
the data in a filesystem is probably more convenient.

g.

      parent reply	other threads:[~2013-04-15 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 15:15 Options to store device tree blob on NAND Flash Hector Palacios
     [not found] ` <5148812D.4090305-i7dp0qKlBMg@public.gmane.org>
2013-04-15 13:28   ` Grant Likely [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=20130415132841.1F8FD3E0AA8@localhost \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=hector.palacios-i7dp0qKlBMg@public.gmane.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;
as well as URLs for NNTP newsgroup(s).