From: Thomas Gleixner <gleixner@autronix.de>
To: "Pieter Grimmerink" <mailinglists@grimmerink.nl>,
<linux-mtd@lists.infradead.org>
Subject: Re: Current status JFFS2 on DOC
Date: Wed, 8 May 2002 20:22:38 +0200 [thread overview]
Message-ID: <200205081822.g48IMck11634@thomas.tec.autronix.de> (raw)
In-Reply-To: <MPBBIIEFELAEABNCNHMMGELBDAAA.mailinglists@grimmerink.nl>
On Wednesday, 8. May 2002 18:37, Pieter Grimmerink wrote:
> From a design point of view, DiscOnChip looks nice with
> it's feature to boot from it.
> SmartMedia looks a bit cheaper, but that would require
> a separate NOR device, large enough to hold a compressed
> kernel, total price going up above the DOC prices again.
The minimum requirement is 1MB for a compressed kernel image
and a bootloader. That's affordable and working :)
> However, all that I have found so far in mailinglists and
> howto's, indicates that JFFS2 on smartmedia has been further
> investigated then JFFS2 on DOC.
JFFS2 on SmartMedia and NAND can be considered as stable.
There are some small TODO's
> But as far as I understand, there should be no physical limitation
> on a DOC to eventually host a JFFS2 filesystem.
No, DOC is NAND with some glue logic around
> Is this all true, and has someone managed to get a working
> JFFS2 filesystem on a DOC?
Thats true, but AFAIK there's no DOC / JFFS2 at the moment.
> and finaly, what are the chances of acutally booting into a
> JFFS2 root filesystem directly from a DOC?
> (I heard something about a modified GNU GRUB to replace the DOC
> firmware)
Yep, grub replaces the bootloader.
> This would eventually all have to run on a non-x86 processor.
Should work
> Is this a workable solution already, or would I have to go for
> more 'conventional' hardware to be safe?
The DOC solution is not workable, because it's not available, but you are
heartly invited to join the club and hack the neccecary drivers. There are
some more people around, who are interrested.
The NAND / Smartmedia solution is working reliable.
See also http://www.linux-mtd.infradead.org/tech/nand.html
--
Thomas
___________________________________
autronix automation GmbH
http://www.autronix.de gleixner@autronix.de
next prev parent reply other threads:[~2002-05-08 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 16:37 Current status JFFS2 on DOC Pieter Grimmerink
2002-05-08 18:08 ` Frederick Lefebvre
2002-05-08 21:46 ` Thomas Gleixner
2002-05-08 18:22 ` Thomas Gleixner [this message]
2002-05-08 22:52 ` Pieter Grimmerink
2002-05-09 7:11 ` David Woodhouse
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=200205081822.g48IMck11634@thomas.tec.autronix.de \
--to=gleixner@autronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mailinglists@grimmerink.nl \
/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