From: "SHIKUILIANG" <klshi_163@163.net>
To: linux-mtd@lists.infradead.org
Cc: dwmw2@infradead.org;, gareth@microm-electronics.com
Subject: DoC beginer
Date: Wed, 14 Nov 2001 20:24:02 +0800 (CST) [thread overview]
Message-ID: <3BF26262.15239@bjapp6.163.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
hi,
I have a problem with my doc2000 device.
my target is x86 PC.and I get a linux kernel of v2.4.6.
then I compiled MTD modules with this kernel:
CONFIG_MTD=m
CONFIG_NFTL=m
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADDRESS=0
and used the new kernel image to reboot my box,
when rebooting up, I do modprobe:
#modprobe doc2000 --> OK
#modprobe nftl --> OK
then I can find 4 modules inserted into kernel :
nftl ,doc2000, mtdcore and docecc
then I run fdisk:
#fdisk /dev/nftla
.
.
.
DiskOnChip 2000 found at address 0xDC000
Sorry, we don't support UnitSizeFactor of != 1 yet
Sorry, we don't support UnitSizeFactor of != 1 yet
Could not find valid boot record
Could not mount NFTL device
Unable to open /dev/nftla
.
.
.
before do these I already run "dformat" command in dos system.
A:>dformat /win:dc00 /s:doc50.exb /y
where did wrong I do ? and what means of
"UnitSizeFactor " ?
I heard some mtd tools,like nftl_format,
where r i can get it?
any hints will be very appreciated!
stars
¼Óн£¬ÉýÖ°ÃÜóÅ
http://www.englishtown.com/master/home/courseoverview.asp?etag=TOCN&ctr=cn
===============================================
ÊÖ»úºÅÂëÊǵçÓÊ£¬´Ó´Ë½»·Ñ²»ÓóһºÅÔÚÊÖ¡°ËæÉíÓÊ¡±
¡ª¡ª 163¡°ËæÉíÓÊ¡±ÊÖ»úÓÊÏä ¡ª¡ª
¡ò ÊÖ»úºÅÂë¾ÍÊǵç×ÓÓÊÏ䵨ַ£¬·½±ã¼ÇÒä
¡ò ²»ÓÃÉÏÍø£¬Í¸¹ýÊÖ»ú¶ÌÐÅ£¬ËæÊ±ÕÆÎÕÓʼþµÄ½ÓÊÕÇé¿ö
¡ò ¾ö²»´í¹ýÈκÎÉÌÒµÁ¼»ú
¡ò ·½±ãµÄ°´ÔÂÊÕ·Ñ·½Ê½£¬×îµÍÿÔÂÖ»Ðè5Ôª
ÏêÇéÇëä¯ÀÀ
http://vip.163.net/mobile/mobile.htm
===============================================
reply other threads:[~2001-11-14 12:14 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=3BF26262.15239@bjapp6.163.net \
--to=klshi_163@163.net \
--cc=dwmw2@infradead.org \
--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