Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] cramfs: add xip option
Date: Mon, 9 Apr 2018 11:42:01 +0200	[thread overview]
Message-ID: <20180409114201.77e40354@windsurf> (raw)
In-Reply-To: <20180407133543.90767-3-chris.brandt@renesas.com>

Hello,

On Sat,  7 Apr 2018 08:35:43 -0500, Chris Brandt wrote:

> +config BR2_TARGET_ROOTFS_CRAMFS_XIP
> +	bool "Support XIP of all ELF files"
> +	help
> +	  For ELF files, uncompressed and properly aligned data blocks will be
> +	  automatically be mapped directly into user space whenever possible providing
> +	  eXecute-In-Place (XIP) from ROM of read-only segments. Data segments mapped
> +	  read-write (hence they have to be copied to RAM) may still be compressed in
> +	  the cramfs image in the same file along with non compressed read-only
> +	  segments. Both MMU and no-MMU systems are supported. This is particularly
> +	  handy for tiny embedded systems with very tight memory constraints.
> +
> +	  The CRAMFS_MTD Kconfig option must also be enabled in a 4.15+ kernel.

These lines were way too long, so I rewrapped them. You can
use ./utils/check-package to verify your changes: it would have
complained on this change due to the length of the lines.

Applied with this fixed.

Thanks for this cramfs update!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-04-09  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 13:35 [Buildroot] [PATCH v3 0/2] cramfs: new maintainer, repo and XIP feature Chris Brandt
2018-04-07 13:35 ` [Buildroot] [PATCH v3 1/2] cramfs: change to new site location Chris Brandt
2018-04-09  9:41   ` Thomas Petazzoni
2018-04-07 13:35 ` [Buildroot] [PATCH v3 2/2] cramfs: add xip option Chris Brandt
2018-04-09  9:42   ` Thomas Petazzoni [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=20180409114201.77e40354@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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