public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Frederick Lefebvre <flefebvre@irg.ca>
To: Pieter Grimmerink <mailinglists@grimmerink.nl>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Current status JFFS2 on DOC
Date: 08 May 2002 14:08:39 -0400	[thread overview]
Message-ID: <1020881319.14408.52.camel@zeus> (raw)
In-Reply-To: <MPBBIIEFELAEABNCNHMMGELBDAAA.mailinglists@grimmerink.nl>

I am working, among many, many other things on getting JFFS2 on a DOC
2000.  I do not know when it will be ready since I've got so much work
right now.

-- 
Frederick Lefebvre
flefebvre@irg.ca
Software Developer,
(418)523-4474 #242
Infomedia Research Group (IRG)
Quebec, Canada

On Wed, 2002-05-08 at 12:37, Pieter Grimmerink wrote:
> I was quite happy to read about the recent efforts to support
> JFFS2 on NAND devices.
> 
> Currently I'm about to make a decision on which flash device
> to use for a new embedded device. 
> Looking at prices NAND flash looks like the best option, 
> especially if we can use JFFS2 on it.
> 
> >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.
> 
> 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.
> But as far as I understand, there should be no physical limitation
> on a DOC to eventually host a JFFS2 filesystem.
> 
> Is this all true, and has someone managed to get a working 
> JFFS2 filesystem on a DOC? 
> 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)
> 
> This would eventually all have to run on a non-x86 processor.
> 
> Is this a workable solution already, or would I have to go for
> more 'conventional' hardware to be safe?
> 
> Best regards,
> 
> Pieter Grimmerink
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

  reply	other threads:[~2002-05-08 18:05 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 [this message]
2002-05-08 21:46   ` Thomas Gleixner
2002-05-08 18:22 ` Thomas Gleixner
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=1020881319.14408.52.camel@zeus \
    --to=flefebvre@irg.ca \
    --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