From: "Dvir Oren" <dvir@lucidvon.com>
To: MTD <mtd@infradead.org>, David Woodhouse <dwmw2@infradead.org>
Subject: Questions about MTD
Date: Sat, 18 Mar 2000 22:05:11 +0200 [thread overview]
Message-ID: <E12WPTl-0007TN-00@infradead.org> (raw)
I'm trying to use the MTD drivers to boot off a DiskOnChip 2000,
and ran into the following problems:
1. The flash has to be formatted with nftl_format in order for the
MTD drivers to write successfully to the flash. However, when I run
nftl_format, it destroys the bios extension that allows booting from
the flash. I then try to run nftl_format /dev/mtd0 49152, to skip the
first 48K, which hold the bios extension. However, this seems to
cause some problems:
a. nftl_format in fact does not erase the first 48K, however it does
delete the partition table. As I understand it, the disk partition is in
the first 512 bytes, so how can that be?
b. When I try to create the partition, there are a lot of file system
errors, possibly because I formatted starting at 49152. It seems
like nftl_format doesn't set the start of the device from after the first
48k, which will then conflict.
2. doc_loadbios doesn't seem to do what it's supposed to do.
However, it does destroy the flash, allowing me to docpmap /e the
flash, which will lead me to the next...
3. erase seg faults. Is erase supposed to do what docpmap /e
does?
4. Some odd problems when trying to dd the first 48k. The
partition table is not saved after removing the nftl module. Only
after writing it a second time does it get saved.
5. One thing I don't understand: even though everybody talks
about the first 48k being the firmware, the firmware itself is less
than 48k. How does that work? And what about the first 512bytes
of the partition table?
Can anybody help?
Has anybody succeeded in booting off a DiskOnChip 2000 using
the MTD drivers?
BTW: The lilo I posted here a few weeks ago which was patched
to work with MTD, probably will not work correctly. I'll post here a
new one soon,. if it interests anyone.
I was partially able to load LILO off /dev/nftla, however only from the
MBR (not /dev/nftla1) - it seems like nftl_format destroys the MBR,
or something like that. I was not able to create a full boot from the
flash, since the file system keeps getting trashed.
---------
Dvir Oren <dvir@lucidvon.com>
Lucid VON Ltd. <http://www.lucidvon.com>
9 Saloniki St., Tel-Aviv Israel
Tel: +972 3 644 3038 Fax: +972 3 644 3039
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-03-18 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-18 20:05 Dvir Oren [this message]
2000-03-20 9:41 ` Questions about MTD David Woodhouse
2000-03-20 18:06 ` Bill Roman
2000-03-20 18:49 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2000-03-20 11:17 Oron Ogdan
2000-03-20 13:51 ` Kyle Harris
2000-03-20 14:11 Oron Ogdan
2000-03-20 16:17 ` Kyle Harris
2000-03-20 19:34 Dvir Oren
2000-03-21 9:01 ` David Woodhouse
2000-03-20 20:51 Oron Ogdan
2000-03-21 2:59 ` Kyle Harris
2000-03-20 20:51 Oron Ogdan
2000-03-21 12:36 Oron Ogdan
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=E12WPTl-0007TN-00@infradead.org \
--to=dvir@lucidvon.com \
--cc=dwmw2@infradead.org \
--cc=mtd@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