From: "Nikolai Vladychevski" <niko@isl.net.mx>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: duplicate DoC millenium with dd
Date: Tue, 11 Sep 2001 20:13:45 GMT [thread overview]
Message-ID: <20010911201345.19481.qmail@qis> (raw)
In-Reply-To: <8583.1000239450@redhat.com>
David Woodhouse writes:
>
> niko@isl.net.mx said:
>> for some reason I can not duplicate Disc on chip Millenium (8MB) with
>> dd command. I can build it using dd, fdisk, nftla_format, erase....
>> etc, but not only dd.
>
> The DiskOnChip uses NAND flash, which has 'out of band' data areas. A
> simple dd won't read or write them. Neither would it be sensible to use the
> nanddump and nandwrite utilities for doing so, although they can - you want
> to reformat each device individually, with its own bad block map, not the
> bad block map of your master.
ohh, so bad.... I will have to nftl_format every time I update my flash....
>
> nftl_format, mkfs and tar or dump/restore are sensible.
>
> What are you partitioning it for, btw?
It's a firewall. I place linuxbios & kernel first, then I nftl_format
/dev/mtd0 0xFIRST_FREE_BLOCK and place a minimal filesystem (cramfs) on the
rest of the chip..... since you say nftl_format removes original badblocks
table M-Systems put on the chip at fabrication time, I kinda dislike this
util.....
is there any way to avoid nftl_format and boot my cramfs from /dev/mtdblockX
or /dev/mtd0 with an 0xXXXX offset or something like this?
Nikolai
next prev parent reply other threads:[~2001-09-11 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 18:26 duplicate DoC millenium with dd Nikolai Vladychevski
2001-09-11 20:17 ` David Woodhouse
2001-09-11 20:13 ` Nikolai Vladychevski [this message]
2001-09-11 21:23 ` David Woodhouse
2001-09-11 20:58 ` Nikolai Vladychevski
2001-09-11 22:00 ` David Woodhouse
2001-09-11 22:20 ` Nikolai Vladychevski
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=20010911201345.19481.qmail@qis \
--to=niko@isl.net.mx \
--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 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.