From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Larsson <alex@cendio.se>
Cc: Bjorn Wesen <bjorn.wesen@axis.com>,
Finn Hakansson <finn.hakansson@axis.com>,
mtd@infradead.org, alan@redhat.com
Subject: Re: JFFS - ready for submission into 2.[34]?
Date: Fri, 02 Jun 2000 09:33:45 +0100 [thread overview]
Message-ID: <28185.959934825@devel2.axiom.internal> (raw)
In-Reply-To: <Pine.LNX.4.10.10006021024210.11605-100000@tammy.signum.se>
alex@cendio.se said:
> Possibly. But i suppose the real reason is that the current way would
> be the way you normally use it in embedded systems (like those axis
> are doing). You generate your root fs on the build machine, create a
> jffs image and download it into the flash memory of the target system.
Yeah, but it's still not imperative to create the image in one go from mkfs.
We create our Linux (and even NT) workstations by just taking a dump of the
filesystem after installation, and dd'ing that onto the target. That would
work just as well for JFFS.
Either way - once we get it working on NAND flash, and having to map round
bad blocks, we're going to have difficulties with just dumping an image on
to the flash anyway.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-06-02 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 16:25 JFFS - ready for submission into 2.[34]? David Woodhouse
2000-06-01 17:13 ` Alexander Larsson
2000-06-02 8:21 ` David Woodhouse
2000-06-02 8:26 ` Alexander Larsson
2000-06-02 8:33 ` David Woodhouse [this message]
2000-06-02 8:04 ` Alexander Larsson
2000-06-02 9:00 ` Finn Hakansson
2000-06-02 9:34 ` David Woodhouse
2000-06-02 8:39 ` Alexander Larsson
2000-06-05 23:10 ` Bjorn Wesen
2000-06-09 5:42 ` Jason Gunthorpe
2000-06-02 9:07 ` Alexander Larsson
2000-06-04 18:35 ` Stephen Tweedie
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=28185.959934825@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=alan@redhat.com \
--cc=alex@cendio.se \
--cc=bjorn.wesen@axis.com \
--cc=finn.hakansson@axis.com \
--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