public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Peter Bergmann <bergmann.peter@gmx.net>
To: linux-mtd@lists.infradead.org
Subject: DiskOnChip Millennium Plus 32MB
Date: Sat, 14 May 2005 13:23:54 +0200	[thread overview]
Message-ID: <4285DFCA.8050703@gmx.net> (raw)

i have an embedded x86 device with a trueffs DiskOnChip
Millennium Plus 32MB on it.
the first thing i've tried was the semi-binary only
driver from m-systems (doc.o) with kernel 2.6.11.
the chip was only detected when specifying the fl_winh
module parameter in order to increase the default probe
window size.
but the driver does not really work. each time i run
md5sum on a file or the device itself (/dev/fla)
i get a different checksum! i've tried the same driver
with a doc2000 16MB and a millennium 8mb and it worked
without problems.

i was glad to find the following message on your project
homepage:
"The DiskOnChip 2000, Millennium and Millennium Plus
devices should be fully supported, using their native
NFTL and INFTL 'translation layers'."

but i've not been able to get it running:

the devices/doc2001plus.c recognizes the device but the
inftl.ko says:
"INFTL no longer supports the old DiskOnChip drivers
loaded via docprobe. Please use the new diskonchip
driver under the NAND subsystem"

great but this combined nand/diskonchip.c driver tells
me "DiskOnChip Millennium Plus 32MB is not supported,
ignoring."

what do i have to do in order to get a
trueffs formatted DiskOnChip Millennium Plus 32MB
running under linux ?

please cc me as i'm not subscribed to the list yet.

thanks for any hints!

cheers,
pet.

             reply	other threads:[~2005-05-14 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 11:23 Peter Bergmann [this message]
2005-05-17  7:11 ` DiskOnChip Millennium Plus 32MB Raphael Zimmerer
2005-05-17 11:43   ` Peter Bergmann
2005-05-17 12:34     ` Balint Cristian
  -- strict thread matches above, loose matches on Subject: below --
2008-06-13 14:39 Mark Salter

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=4285DFCA.8050703@gmx.net \
    --to=bergmann.peter@gmx.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