From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1TfVV2-0002YK-0i for barebox@lists.infradead.org; Mon, 03 Dec 2012 12:51:52 +0000 Date: Mon, 3 Dec 2012 07:51:50 -0500 (EST) From: "Robert P. J. Day" In-Reply-To: <20121203092701.GI10369@pengutronix.de> Message-ID: References: <20121203092701.GI10369@pengutronix.de> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: should i expect trying to mount a cramfs fs to give me a segmentation fault? To: Sascha Hauer Cc: "U-Boot Version 2 (barebox)" On Mon, 3 Dec 2012, Sascha Hauer wrote: > cramfs was present in barebox very early. I think in some places the > implementation still assumes that the filesystem image is directly > memory mapped. Probably we should investigate and either add a big > warning somewhere or fix it. ok, good to know ... i deleted my wiki page regarding barebox and cramfs since it's clear i didn't understand it. only suggestion would be to update this page: http://wiki.barebox.org/doku.php?id=user:first_steps so users don't trip over the same thing i did. onward ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox