public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
To: <Russ.Dill@asu.edu>
Cc: linux-mtd@lists.infradead.org
Subject: RE: File systems and Disk on Chips
Date: Sun, 6 Jul 2003 13:41:58 -0400	[thread overview]
Message-ID: <000001c343e5$e6bb1d20$239efea9@who5> (raw)
In-Reply-To: <1057473735.2659.247.camel@localhost>

(See below, to honor the hosting list's policies.)
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-
> bounces@lists.infradead.org] On Behalf Of Russ Dill
> Sent: Sunday, July 06, 2003 2:42 AM
> To: Gregg C Levine
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: File systems and Disk on Chips
> 
> On Sat, 2003-07-05 at 17:00, Gregg C Levine wrote:
> > Hello from Gregg C Levine
> > I have here a 2 Megabyte Disk on Chip device, plugged into a
carrier
> > board. It is now wearing the GRUB based firmware. How when I bring
up
> > my system, the DOC device complains about the lack of a file
system.
> > Any ideas as to how I could put a file system on this device?
> > Preferably as a native Linux format.
> 
> Basically, you put a block filesystem on top of NFTL that grub
> understands. Grub does not at this point understand YAFFS or JFFS2
on
> NAND flash, but I'm sure there a lot of people who are looking for
that
> and it wouldn't be difficult to do.
> 
> --
> Russ Dill <Russ.Dill@asu.edu>
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
Hello again from Gregg C Levine
Okay that makes more sense. But now how do I go about creating the "
block filesystem on top of NFTL", that I need to use? 

For example, I've gotten with my test image, as far as creating a
floppy disk image, and booting that, inside the Bochs emulator. It
worked, the test kernel launched, and told me that the kernel did what
it was supposed to do. 

My other problem, is that I still can not get the utilities inside
that directory to properly compile, they always break when trying to
create the ones that manage the JFFS2 stuff. I am hoping that the
snapshot from yesterday has been fixed, but I don't know.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

  reply	other threads:[~2003-07-06 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-06  0:00 File systems and Disk on Chips Gregg C Levine
2003-07-06  0:04 ` Gregg C Levine
2003-07-06  6:42 ` Russ Dill
2003-07-06 17:41   ` Gregg C Levine [this message]
2003-07-06 18:47     ` Russ Dill
2003-07-08  8:09     ` David Woodhouse
2003-07-06 22:27   ` Charles Manning
2003-07-06 22:58     ` Russ Dill

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='000001c343e5$e6bb1d20$239efea9@who5' \
    --to=hansolofalcon@worldnet.att.net \
    --cc=Russ.Dill@asu.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox