public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Stephen Herzog" <mtd@sdesign.com>
To: <linux-mtd@lists.infradead.org>
Subject: DoC, NFTL, partitions
Date: Wed, 2 May 2001 15:01:48 -0700	[thread overview]
Message-ID: <000f01c0d353$7c5d27c0$160aa8c0@gumby> (raw)

Greetings,

I am currently working on a project using a single DoC Millennium 8M 
for boot, os, and data collection.  I currently have a system configured
with a single nftl filesystem, and then devided it into a 6M (OS) and 2M
(log file) partitions nftla1 and nftla2.  Both have ext2 file systems on
it.  Boot is achived by using the msystems bios and modified lilo. 

My problem is this: the 2M log file partition gets corrupted with 
unscheduled power down. 

I have read a large amount of information and source code and one of 
the best solution I have seen was suggested by dwmw2 at  
http://mhonarc.axis.se/jffs-dev/msg00411.html  where I would place
two nftl filesystems on the DOC, and then use ext2 on the first, 
and jffs on the second. 

I have made a few attempts at this, however I am not succeeding 
at it and decided to ask for some help. I am using kernel 2.4.3 
with mtd-snapshot-20010430.tar.bz2 

here are the steps I have taken thus far:

eraseall /dev/mtd0
  Erased 8192 Kibyte @ 0 -- 100% complete.

nftl_format /dev/mtd0 0 4194303
  Phase 1. Checking and erasing Erase Zones from 0x00000000 to 0x003fffff
          Erasing Zone #510 @ 0x3fc000
  Phase 2.a Writing NFTL Media Header and Bad Unit Table
  Phase 2.b Writing Spare NFTL Media Header and Spare Bad Unit Table
  Phase 3. Writing Unit Control Information to each Erase Unit

nftl_format /dev/mtd0 4194304 4194303
  Phase 1. Checking and erasing Erase Zones from 0x00400000 to 0x007fffff
          Erasing Zone #1022 @ 0x7fc000
  Phase 2.a Writing NFTL Media Header and Bad Unit Table
  Phase 2.b Writing Spare NFTL Media Header and Spare Bad Unit Table
  Phase 3. Writing Unit Control Information to each Erase Unit

I reboot now as I am not using modules.
On boot, I get the following:

  M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
  ...
  DiskOnChip Millennium found at address 0xD0000
  Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
  1 flash chips found. Total DiskOnChip size: 8 Mbytes
  mtd: Giving out device 0 to DiskOnChip Millennium
  ...
  M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
  $Id: nftlcore.c,v 1.68 2001/03/26 15:44:47 dwmw2 Exp $
  NFTL_notify_add for DiskOnChip Millennium
  NFTL_setup
   nftla: unknown partition table
  Linux PCMCIA Card Services 3.1.22    

I was really wanting to see nftla AND nftlb here.   As an aside, 
I can fdisk /dev/nftla and get a single 4M partition on /dev/nftla1
however I can't seem to find the other 4M of the chip.  From reading 
the nftl kernel code, it sounds like it should scan then entire DoC 
and find the two partitions, however that is not happening. 

Can someone offer advice as to what I am doing wrong?

Also, any tips for getting jffs onto the nftl partition, I don't
seem to be having much luck there either. 

Thanks in advance,

Steve Herzog

             reply	other threads:[~2001-05-02 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 22:01 Stephen Herzog [this message]
2001-05-03  0:59 ` DoC, NFTL, partitions Ollie Lho

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='000f01c0d353$7c5d27c0$160aa8c0@gumby' \
    --to=mtd@sdesign.com \
    --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