From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Simmonds Subject: Re: [PATCH 06/14] Pramfs: Include files Date: Mon, 22 Jun 2009 20:31:10 +0100 Message-ID: <4A3FDBFE.8050509@2net.co.uk> References: <4A33A7EC.6070008@gmail.com> <200906221317.04166.arnd@arndb.de> <4A3FC7F1.5050108@gmail.com> <200906222033.20883.arnd@arndb.de> Reply-To: chris@2net.co.uk Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200906222033.20883.arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Arnd Bergmann Cc: Marco , Sam Ravnborg , Linux FS Devel , Linux Embedded , Linux Kernel Arnd Bergmann wrote: > On Monday 22 June 2009, Marco wrote: >> Sorry, I meant it's not currently possible. At the moment the only way >> to use it as rootfs it's to copy all the data in an already mounted >> (empty) ram partition and reboot. However it's not my first item on my >> todo list because I think that it's possible to use it as rootfs but it >> isn't the standard use for this fs. > > Well, it doesn't have to work right away. What I'm asking to > define the data structures in a way that keeps the layout stable > across kernel updates. Since a future version of the file system > might support cross-endian image creation, it would be good to > define the data structures in a fixed endian mode already, so > you don't have to change it in the future. > > Arnd <>< > -- > To unsubscribe from this list: send the line "unsubscribe linux-embedded" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > I disagree: that adds an unnecessary overhead for those architectures where the cpu byte order does not match the data structure ordering. I think the data structures should be native endian and when mkpramfs is written it can take a flag (e.g. -r) in the same way mkcramfs does. Chris Simmonds