From: Brent Roberts <randd@globalopensource.net>
To: MTD list <linux-mtd@lists.infradead.org>
Subject: kernel for DOC 2000 192 MB with 5.1.2 firmware
Date: Fri, 5 Aug 2005 16:37:33 -0700 [thread overview]
Message-ID: <200508051637.33177.randd@globalopensource.net> (raw)
Hello all.
Which kernel version will support the DiskOnChip 2000 size 192 MB with 5.1.2
firmware? I have not had success doing the following:
Using kernel 2.6.3 with the following relevant configuration:
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOCPROBE=y
CONFIG_MTD_DOCPROBE_ADDRESS=0
#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND_IDS=y
and kernel 2.6.8 with the following relevant configuration:
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOCECC=y
#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_IDS=y
CONFIG_MTD_NAND_DISKONCHIP=y
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
In each case I boot to DOS and issue the following commands using version 5.x
of DOC tools:
To save the BBT:
dformat /win:d000 /noformat /log:docbbt.txt
To install GRUB and format with NFTL (where GRUB_F~1 is grub_firmware, I
intend to boot from this DOC):
dformat /win:d000 /bdfk0:GRUB_F~1
Then I boot to linux:
fdisk /dev/nftla
This command fails: "fdisk cannot open /dev/nftla".
The above commands and grub_firmware worked fine with a 32 MB DOC 2000 having
4.2 firmware on the 2.6.3 kernel i described above.
I have read that linux prefers the 4.2 firmware, however, attempts to change
from 5.1.2 to 4.2 have been unsuccessful using M-Systems DOC tools under DOS.
Thanks in advance!
-Brent Roberts
reply other threads:[~2005-08-06 0:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200508051637.33177.randd@globalopensource.net \
--to=randd@globalopensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.