From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from web43137.mail.sp1.yahoo.com ([216.252.121.67]) by bombadil.infradead.org with smtp (Exim 4.66 #1 (Red Hat Linux)) id 1IqaaE-0007Sw-3w for linux-mtd@lists.infradead.org; Fri, 09 Nov 2007 15:36:13 -0500 Date: Fri, 9 Nov 2007 12:36:03 -0800 (PST) From: Justin Treon Subject: Re: [PATCH 1/1] MTD: Unlocking all Intel flash that is locked on power up To: Nicolas Pitre In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <162938.6418.qm@web43137.mail.sp1.yahoo.com> Cc: linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > > > > Adding the ability to unlock a partition on mount is not a bad idea, but it > > > should > > > > not be the only way. I often write to an mtd block device without mounting > it > > > and I > > > > do not always use jffs2 as my writable filing system. > > > > > > Never heard of the MTD flash-unlock user space utility? > > > > > > > That does not help me on boot up. I already have filing sytems that run that > > through scripts on startup for some of my test images. > > What about a new partition flag then? When set the unlock method would > be called on the corresponding partition if the partition is not already > marked read-only. > Then what is the point of the read only flag? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com