From: "Alok Singh" <aloks@broadcom.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] JFFS2 - readme.txt
Date: Wed, 30 May 2007 21:03:00 -0000 [thread overview]
Message-ID: <FE7FB54DCB7C6949A1D3F9FF22DA6C135AB138@lvl7in-mail01.lvl7.com> (raw)
In-Reply-To: <20070530191758.GF32489@lunn.ch>
Andrew,
I'm using v2_0 jffs2. I'm running the test fileio1.c under jffs2/tests
folder. I'm getting errors in creating the file "foo". Any pointers
here.
Device being mounted is -
cdl_component CYGDAT_IO_FLASH_BLOCK_DEVICE_NAME_1 {
# Flavor: data
user_value "\"/dev/flash1\""
# value_source user
# Default value: "\"/dev/flash1\""
};
cdl_option CYGNUM_IO_FLASH_BLOCK_OFFSET_1 {
# Flavor: data
user_value 0x000A0000 /* 0xbc0A0000*/
# value_source user
# Default value: 0x00100000
};
cdl_option CYGNUM_IO_FLASH_BLOCK_LENGTH_1 {
# Flavor: data
user_value 0x800000 /* 8 MB */
# value_source user
# Default value: 0x00100000
}
****************************************************
INFO>: reading directory /
<INFO>: entry . [mode 00016f01 ino 80184530 nlink 1 size 0]
<INFO>: entry .. [mode 00016f01 ino 80184530 nlink 1 size 0]
<INFO>: create file /foo size 202
<FAIL>: access() returned 286326803
<4>Write error in obliterating obsoleted node at 0x007c0000: 1
<5>Write of %zd bytes at 0x00000044 failed. returned 8126476, retlen %z
d
<5>Write of %zd bytes at 0x0000002b failed. returned 8126544, retlen %z
d
regards,
Alok
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Thursday, May 31, 2007 12:48 AM
To: Alok Singh
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] JFFS2 - readme.txt
On Thu, May 31, 2007 at 12:32:19AM +0530, Alok Singh wrote:
> Hi,
> I'm trying to use jffs2 on my box. Readme.txt under doc says that
> minor modifications are necessary to eCos flash drivers(flash.c and
> flash_program_buf.c for intel chip) and that these are supplied in
> "jffs2/current/src" folder.
That is an old document. Ignore it. The current Intel flash drivers
should work.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-30 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 19:11 Alok Singh
2007-05-30 20:22 ` Andrew Lunn
2007-05-30 21:03 ` Alok Singh [this message]
2007-05-30 21:12 ` Andrew Lunn
2007-05-30 21:58 ` Alok Singh
2007-05-31 0:24 ` Andrew Lunn
2007-05-31 14:34 ` [ECOS] routines to dump ARP and Route table in ecos Madan Mohan Goud
2007-05-31 14:50 ` Lars Povlsen
2007-05-31 16:11 ` Andrew Lunn
2007-06-01 5:12 ` Madan Mohan Goud
2007-06-01 10:25 ` Madan Mohan Goud
2007-06-01 19:46 ` [ECOS] routines to dump ARP and Route table in ecos - Alok Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FE7FB54DCB7C6949A1D3F9FF22DA6C135AB138@lvl7in-mail01.lvl7.com \
--to=aloks@broadcom.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).