public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: Darren Martz <dmartz@shelbrook.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Boot from DoC2000
Date: Thu, 09 May 2002 08:54:07 -0700	[thread overview]
Message-ID: <1020959648.30841.3590.camel@russ> (raw)
In-Reply-To: <001e01c1f73d$8a53ad90$9702a8c0@maverick>

On Thu, 2002-05-09 at 02:40, Darren Martz wrote:
> I'm new to linux, so my questions may seem rather simplistic <g>
> 
> Sorry for the multiple questions, I have read most of the papers and
> many of the posting on this list but these are missing pieces...
> 
> It seems the m-sys driver adds logic to the bios gaining access to the
> DoC. The mtd solution everyone is working so hard on seems to do things
> differently, but I'm not sure how or what.  I am also unclear as to what
> boot loaders support this new way to boot an mtd device. I understand
> grub is designed to support that scenario but is still in development.
> Does the lilo solution rely on the m-sys patch?
> 
> I suppose a boot loader like grub is required because the bios doesn't
> support native access to the device(s).
> 
> So what filesystem options are there? I know that m-sys has their own
> "TrueFFS" fs, and it requires a kernel patch. Being new to linux, I'd
> like to stay away from that for the time being. I have read about jffs1
> and jffs2, and from what I can tell jffs1 is stable but lacking the nice
> features, while jffs2 is very much experimental but coming along nicely.
> 
> Knowing all that, the options seem to be as follows:
> 
> 1) LILO plus an m-sys patch with the TrueFFS or any other filesystem
> 2) GRUB with any filesystem including JFFS, but not TrueFFS
> 3) SYSLINUX ??? i suspect is not supported
> 
> I believe I read that to date, nobody has had a successful boot on a DoC
> with grub - yet! 
> So does that leave the only current option as LILO with the m-sys patch?

look at the mailing list archives, grub works great on a DOC. jffs2 (or
jffs) is not ready for use on a DOC, but its close, so you'd have to use
a standard filesystem on top of NFTL.

actually, syslinux works fine with the original m-sys "firmware"

  reply	other threads:[~2002-05-09 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  9:40 Boot from DoC2000 Darren Martz
2002-05-09 15:54 ` Russ Dill [this message]
2002-05-09 17:06   ` Darren Martz
2002-05-09 19:43     ` Thomas Gleixner
2002-05-09 21:26 ` David Woodhouse
2002-05-09 22:28   ` Darren Martz
2002-05-09 22:45     ` David Woodhouse
2002-05-09 22:47     ` Ilguiz Latypov
2002-05-13 12:41 ` 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=1020959648.30841.3590.camel@russ \
    --to=russ.dill@asu.edu \
    --cc=dmartz@shelbrook.com \
    --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