From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001157] New: Addition of JFFS2 flash test offset and length options to cdl
Date: Thu, 17 Feb 2011 22:04:00 -0000 [thread overview]
Message-ID: <bug-1001157-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001157
Summary: Addition of JFFS2 flash test offset and length options
to cdl
Product: eCos
Version: CVS
Platform: All
OS/Version: HostOS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: mbergandi@gmail.com
CC: ecos-patches@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=1136)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1136)
eCos ecm to enable JFFS2 and patch file
HOST: Ubuntu 10.04.1 LTS
TARGET: Linux Synthetic Target
The jffs2 tests attempt to mount JFFS2_TEST_DEV at "/". JFFS2_TEST_DEV is
defined as in fs/jffs2/current/tests/jffs2_1.c as:
# define JFFS2_TEST_DEV "/dev/flash/0/"
stringify(CYGNUM_FS_JFFS2_TEST_OFFSET) ","
stringify(CYGNUM_FS_JFFS2_TEST_LENGTH)
That define literally evaluates to:
JFFS2_TEST_DEV="/dev/flash/0/CYGNUM_FS_JFFS2_TEST_OFFSET,CYGNUM_FS_JFFS2_TEST_LENGTH"
I verified it in gdb. CYGNUM_FS_JFFS2_TEST_OFFSET and
CYGNUM_FS_JFFS2_TEST_LENGTH are not defined _anywhere_ in the ecos
tree. Since the image gets mounted successfully in the test, I assume
that the offset and length are just ignored if they aren't numbers.
A suggestion was made to add these missing defines to the jffs2.cdl. I have
attached a patch to just that. There is also a minimal config to turn on jffs2
and its requirements. They are in the attached jffs2test.tar.gz.
The default jffs2 config sets a block size of 64KB, 15 main blocks, and one
boot block. The total size of the synthv2.flash image that the tests create is
1MB. Based on these sizes, I set the default for CYGNUM_FS_JFFS2_TEST_OFFSET to
be 0x1000 (64KB: skip the boot block) and CYGNUM_FS_JFFS2_TEST_LENGTH to
0x0F0000 (1MB - 64KB). If my understanding is correct, the length is measured
from the offset. The result would be that JFFS2_TEST_DEV will be sensible:
JFFS2_TEST_DEV="/dev/flash/0/0x1000,0x0F0000"
I ran all the jffs2 tests successfully on the synthetic target with boot blocks
enabled and disabled.
Mike
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-02-17 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 22:04 bugzilla-daemon [this message]
2011-02-17 22:25 ` [Bug 1001157] " bugzilla-daemon
2011-02-17 22:26 ` bugzilla-daemon
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=bug-1001157-104@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).