From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] cramfs: change to new site location
Date: Tue, 13 Feb 2018 21:26:50 +0100 [thread overview]
Message-ID: <20180213212650.3fe2884b@windsurf.lan> (raw)
In-Reply-To: <SG2PR06MB1165EA4292BE78ADF8D3A1678AF60@SG2PR06MB1165.apcprd06.prod.outlook.com>
Hello,
On Tue, 13 Feb 2018 20:24:21 +0000, Chris Brandt wrote:
> All I can tell you is that there is not a command line option for it.
> So, I assume it's not supported.
>
> $ output/build/host-cramfs-5aea81001ac6/mkcramfs
> usage: output/build/host-cramfs-5aea81001ac6/mkcramfs [-h] [-e edition] [-i file] [-n name] [-D file] dirname outfile
> -h print this help
> -E make all warnings errors (non-zero exit status)
> -e edition set edition number (part of fsid)
> -i file insert a file image into the filesystem (requires >= 2.4.0)
> -n name set name of cramfs filesystem
> -p pad by 512 bytes for boot code
> -s sort directory entries (old option, ignored)
> -v be more verbose
> -x use extended block pointers (requires >= 4.15)
> -X allow XIP of ELF files (imply -x)
> -z make explicit holes (requires >= 2.3.39)
> -D Use the named FILE as a device table file
> -q squash permissions (make everything owned by root)
> dirname root of the filesystem to be compressed
> outfile output file
>
> I don't have any big endian systems, so I can't test it either.
We have a number of Qemu defconfigs, including for big-endian systems
such as PowerPC. It should be doable to perform a test :)
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-13 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:54 [Buildroot] [PATCH 0/2] cramfs: new maintainer, repo and XIP feature Chris Brandt
2018-02-13 19:54 ` [Buildroot] [PATCH 1/2] cramfs: change to new site location Chris Brandt
2018-02-13 20:14 ` Thomas Petazzoni
2018-02-13 20:24 ` Chris Brandt
2018-02-13 20:26 ` Thomas Petazzoni [this message]
2018-02-13 21:08 ` Chris Brandt
2018-02-14 17:37 ` Chris Brandt
2018-04-05 19:07 ` Matthew Weber
2018-04-06 15:02 ` Chris Brandt
2018-04-06 15:13 ` Thomas Petazzoni
2018-04-06 15:19 ` Chris Brandt
2018-04-06 15:29 ` Thomas Petazzoni
2018-04-06 15:41 ` Matthew Weber
2018-04-06 15:38 ` Matthew Weber
2018-04-06 15:36 ` Matthew Weber
[not found] ` <nycvar.YSQ.7.76.1804061138320.28462@knanqh.ubzr>
2018-04-06 15:43 ` Matthew Weber
[not found] ` <nycvar.YSQ.7.76.1804061305080.28462@knanqh.ubzr>
2018-04-06 18:29 ` Matthew Weber
[not found] ` <nycvar.YSQ.7.76.1804061446470.28462@knanqh.ubzr>
2018-04-06 19:07 ` Chris Brandt
2018-02-13 19:54 ` [Buildroot] [PATCH 2/2] cramfs: add xip option Chris Brandt
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=20180213212650.3fe2884b@windsurf.lan \
--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