From: Juan Gonzo <kayemmess@yahoo.ca>
To: MTD Mailing List <mtd@infradead.org>
Subject: Re: persistence of files using jffs
Date: Fri, 14 Jul 2000 19:09:47 -0400 (EDT) [thread overview]
Message-ID: <20000714230947.15023.qmail@web5305.mail.yahoo.com> (raw)
When umount and then remount, any new files I copied are
not there.
Our system has 4 Intel Strataflash chips that are coupled pairs
to give us 32MB at 32bits data width. In the structure 'map_info',
I set the 'buswidth' field to 4.
The startup code uses the write32 functions, but when I mount
I noticed that write16 functions are being used. As well, in
the file cfi_cmdset_0001.c, only write16 functions are called.
Is this causing a problem for our system?
Thanks,
-- kelly
--- David Woodhouse <dwmw2@infradead.org> wrote:
>
> kayemmess@yahoo.ca said:
> > (1) mknod /dev/mtd3 b 31 3 (mtd3 is where the fs 'partition'
> is,
> > using examples from nora.c)
>
> The block devices should be /dev/mtdblock<n>. /dev/mtd3 should be a
> character device. But the names don't really matter.
>
>
> kayemmess@yahoo.ca said:
> > And I can 'umount /mnt' successfully as well.
> > However, when I cycle power on the system, any *new* files I create
> or
> > copy into this space are lost.
>
> Hmmm. Are they there when you unmount and remount? Can you make sure
> you're
> using the latest version from CVS, and enable CONFIG_JFFS_FS_VERBOSE?
>
>
>
> --
> dwmw2
>
>
>
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-07-14 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 23:09 Juan Gonzo [this message]
2000-07-15 13:26 ` persistence of files using jffs David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2000-07-13 20:09 Juan Gonzo
2000-07-14 7:37 ` David Woodhouse
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=20000714230947.15023.qmail@web5305.mail.yahoo.com \
--to=kayemmess@yahoo.ca \
--cc=mtd@infradead.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