From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp104.biz.mail.re2.yahoo.com (smtp104.biz.mail.re2.yahoo.com [206.190.52.173]) by ozlabs.org (Postfix) with SMTP id DC33667B75 for ; Tue, 4 Jul 2006 00:19:47 +1000 (EST) Subject: Re: JFFS2 FS is read-only (not what I want) From: Ben Warren To: Mathieu Deschamps In-Reply-To: <200607031241.27979.mathieu.deschamps@com2gether.net> References: <44A6E57A.3080302@qstreams.com> <200607031241.27979.mathieu.deschamps@com2gether.net> Content-Type: multipart/alternative; boundary="=-SOEuVoAMtFQbOz+Tj3a9" Date: Mon, 03 Jul 2006 10:19:44 -0400 Message-Id: <1151936384.12449.12.camel@saruman.qstreams.net> Mime-Version: 1.0 Cc: linuxppc-embedded@ozlabs.org Reply-To: bwarren@qstreams.com List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --=-SOEuVoAMtFQbOz+Tj3a9 Content-Type: text/plain Content-Transfer-Encoding: 7bit Mathieu, Thanks for responding! On Mon, 2006-07-03 at 12:42 +0200, Mathieu Deschamps wrote: > > > Do you mean that you can't even created a void file on / as root ? Else > can you then put for instance text in it ? My point is can or can't you > first create a new fs node and then can you write to file your > changes, that's two possible causes. # pwd / # touch newfile touch: newfile: No space left on device # > Yes indeed what about drivers/mtd/maps/physmap.c ? your parts are > mask_flags: MTD_WRITEB_WRITEABLE and not MTD_CAP_ROM, > aren't they ? > My chip is pretty standard NOR type Flash, and gets recognized by CFI as using command set 0001. It gets these flags: #define MTD_CAP_NORFLASH (MTD_CLEAR_BITS|MTD_ERASEABLE) > > *** > > # Memory Technology Devices (MTD) > > # > > CONFIG_MTD=y > > # CONFIG_MTD_DEBUG is not set > > # CONFIG_MTD_CONCAT is not set > > CONFIG_MTD_PARTITIONS=y > > # CONFIG_MTD_REDBOOT_PARTS is not set > > # CONFIG_MTD_CMDLINE_PARTS is not set > > > [...] > > # CONFIG_JFFS_FS is not set > > CONFIG_JFFS2_FS=y > > Better avoid redundacy but this is not a clue, I guess > make won't be fooled by this. > Sorry, what's redundant here? I just used 'make menuconfig', and hopefully it notices incorrect options. > > IMHO, it's not a generation-time issue > > > Good. I'll keep plugging away with my BDI thanks again, Ben --=-SOEuVoAMtFQbOz+Tj3a9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Mathieu,

Thanks for responding!

On Mon, 2006-07-03 at 12:42 +0200, Mathieu Deschamps wrote:

>
Do you mean that you can't even created a void file on / as root ? Else
can you then put for instance text in it ? My point is can or can't you
first create a new fs node and then can you write to file your
changes, that's two possible causes.

# pwd
/
# touch newfile
touch: newfile: No space left on device
#

Yes indeed what about drivers/mtd/maps/physmap.c ? your parts are
mask_flags:  MTD_WRITEB_WRITEABLE and not  MTD_CAP_ROM,
aren't they ?

My chip is pretty standard NOR type Flash, and gets recognized by CFI as using command set 0001. It gets these flags:
#define MTD_CAP_NORFLASH (MTD_CLEAR_BITS|MTD_ERASEABLE)

> ***
> # Memory Technology Devices (MTD)
> #
> CONFIG_MTD=y
> # CONFIG_MTD_DEBUG is not set
> # CONFIG_MTD_CONCAT is not set
> CONFIG_MTD_PARTITIONS=y
> # CONFIG_MTD_REDBOOT_PARTS is not set
> # CONFIG_MTD_CMDLINE_PARTS is not set
>
[...]
> # CONFIG_JFFS_FS is not set
> CONFIG_JFFS2_FS=y

Better avoid redundacy but this is not a clue, I guess
make won't be fooled by this.

Sorry, what's redundant here? I just used 'make menuconfig', and hopefully it notices incorrect options.


IMHO, it's not a generation-time issue

>

Good. I'll keep plugging away with my BDI

thanks again,
Ben --=-SOEuVoAMtFQbOz+Tj3a9--