public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Carl Przybylek <carlp@bioace.net>
To: linux-mtd@lists.infradead.org
Subject: JFFS1/2 with DiskOnChip
Date: Wed, 18 Sep 2002 15:57:03 -0400	[thread overview]
Message-ID: <3D88DA8E.212465C5@bioace.net> (raw)

Sorry I accidentally hit send....

I keep getting these ECC needs a full sector write when trying to put a
jffs1/2 image onto an m-sys disk on chip.   Seems at first the latest
mtd source did not link into the kernel correctly, Ive fixed that and I
still keep getting the errors.  If someone can answer the following
questions or has put a jffs2 filesytem on DiskOnChip I would greatly
appreciate a list of the steps you followed to get it to work.

Ive went through and ensured the following are configured in the
kernel.  I do have a question about the CONFIG_MTD_NAND_YOURBOARD=y
option.  Ive noticed the inti_doc2000 calls are defined so I assume I
dont need to follow the procedure in
http://www.linux-mtd.infradead.org/tech/nand.html to add my device.
However, I dont see an option for CONFIG_MTD_NAND_DOC2000.  Is this
enabled by the CONFIG_MTD_DOC2000 option?

CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_NAND_YOURBOARD=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_NAND=y

Also Ive notice an option CONFIG_MTD_NAND_ECC_JFFS2 in the nand.c file.
I dont see this defined in any other code, do I need to enable this
config option in the kernel as well?

Im also confused as to whether I need to worry about the nftla system
before I add the jffs2 system.  It seems from the howto that I only need
to eraseall /dev/mtd0 and then cp jffs2.image /dev/mtd0 and I should be
good to go.  Everytime I try to cp to the dev/mtd0 device i keep getting
an ECC error.

Thanks
Carl Przybylek

             reply	other threads:[~2002-09-18 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 19:57 Carl Przybylek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-18 18:57 JFFS1/2 with DiskOnChip Carl Przybylek

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=3D88DA8E.212465C5@bioace.net \
    --to=carlp@bioace.net \
    --cc=linux-mtd@lists.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