From: Al Viro <viro@ZenIV.linux.org.uk>
To: Daniel Walker <danielwa@cisco.com>
Cc: Nikunj Kela <nkela@cisco.com>,
David Woodhouse <dwmw2@infradead.org>,
xe-linux-external@cisco.com, Rod Whitby <rod@whitby.id.au>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make JFFS2 endianness configurable
Date: Fri, 2 Nov 2018 00:34:34 +0000 [thread overview]
Message-ID: <20181102003434.GW32577@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20181102000236.rqho7txtb7gv543t@zorba>
On Thu, Nov 01, 2018 at 05:02:36PM -0700, Daniel Walker wrote:
>
>
>
> On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote:
> > This patch allows the endianness of the JFSS2 filesystem to be
> > specified by config options.
> >
> > It defaults to native-endian (the previously hard-coded option).
> >
> > Some architectures benefit from having a single known endianness
> > of JFFS2 filesystem (for data, not executables) independent of the
> > endianness of the processor (ARM processors can be switched to either
> > endianness at run-time).
> >
>
>
> The description is pretty sad .. We have a product which we released that uses
> JFFS2, and that product was release with a kernel in one endianness. Then later
> on we decided to change the endianness and now we're stuck with a JFFS2
> partition that has the wrong endiannes, in a released product. This patch allows
> us to set the endianness to something different from the architecture setting.
>
> So there a significant use case for the change, at least for Cisco.
FWIW, can't we detect it at mount time, as e.g. UFS does?
next prev parent reply other threads:[~2018-11-02 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 22:56 [PATCH] Make JFFS2 endianness configurable Nikunj Kela
2018-11-02 0:02 ` Daniel Walker
2018-11-02 0:34 ` Al Viro [this message]
2018-11-02 14:04 ` Daniel Walker
2018-11-02 20:15 ` Richard Weinberger
2018-11-02 21:14 ` Daniel Walker
2018-11-02 21:22 ` Richard Weinberger
2018-11-07 1:09 ` Nikunj Kela (nkela)
2018-11-02 8:45 ` Joakim Tjernlund
2018-11-02 9:28 ` Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 20:18 [PATCH]: " Rod Whitby
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=20181102003434.GW32577@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=danielwa@cisco.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nkela@cisco.com \
--cc=rod@whitby.id.au \
--cc=xe-linux-external@cisco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.