[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1415353480.958.301.camel@sauron.fi.intel.com>
Date: Fri, 07 Nov 2014 11:44:40 +0200
From: Artem Bityutskiy <dedekind1@...il.com>
To: Rodrigo Freire <rfreire@...hat.com>
Cc: Jörn Engel <joern@...fs.org>,
linux-mtd@...ts.infradead.org, Felix Fietkau <nbd@...nwrt.org>,
dwmw2@...radead.org, linux-kernel@...r.kernel.org,
Herton Krzesinski <hkrzesin@...hat.com>
Subject: Re: [RESEND PATCH V2] mtd: block2mtd: Present block2mtd timely on
boot time
On Sat, 2014-11-01 at 09:33 -0400, Rodrigo Freire wrote:
> From: Felix Fietkau <nbd@...nwrt.org>
>
> mtd: block2mtd: Ensure that block2mtd is presented timely on boot time
>
> Currently, a block MTD device is not presented to the system on time, in
> order to start mounting the filesystems. This patch ensures that block2mtd
> is presented at the right time, so filesystems can be mounted on boot time.
> This issue is seen on BCM2835 (Raspberry Pi) systems when mounting JFFS2
> over block2mtd devices as the root filesystem.
> This patchset also adds a MTD device name and a timeout option to the driver.
> Original patchset:
> https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.12/440-block2mtd_init.patch?rev=40444
> https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.12/441-block2mtd_probe.patch?rev=40444
I think you can mount jffs2 using /dev/mtdX, you do not need the block
driver.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists