From: Justin Wojdacki <justin.wojdacki@analog.com>
To: Daniel Belz <danielb@cyclades.com.br>
Cc: MTD <linux-mtd@lists.infradead.org>
Subject: Re: Mounting JFFS2, Bootloader
Date: Thu, 11 Jul 2002 10:08:19 -0700 [thread overview]
Message-ID: <3D2DBB83.ED181F2C@analog.com> (raw)
In-Reply-To: 3D2D79FE.5C54CC78@cyclades.com.br
Having recently done the same kind of thing (on a different board), I
think I can help.
Exactly what you need depends a bit on how you want to handle this. If
you are happy with a bootstrap that can only handle one kernel, then
it's really easy: You hardcode the path/filename of the kernel into
the bootloader, and then walk the filesystem looking for this file. If
you want more flexibility than that, you may instead need to look for
a configuration file and then process the configuration file.
JFFS2 has a really easy to work with on-device layout, so it shouldn't
take much effort to locate the files you're interested in.
The files you'll need to work with are in fs/jffs2 and include/linux.
Figure out exactly what capabilities you want first though. That'll
make it much easier to plan out. And remember, if it's being done in
the bootloader, you're not in the kernel, so you may have to
reimplement some things.
--
-------------------------------------------------
Justin Wojdacki
justin.wojdacki@analog.com (408) 350-5032
Communications Processors Group -- Analog Devices
next prev parent reply other threads:[~2002-07-11 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 12:28 Mounting JFFS2, Bootloader Daniel Belz
2002-07-11 17:08 ` Justin Wojdacki [this message]
2002-07-11 17:42 ` Daniel Belz
2002-07-11 18:49 ` Justin Wojdacki
2002-07-12 15:43 ` Marius Groeger
2002-07-11 17:50 ` Daniel Belz
2002-07-11 17:45 ` 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=3D2DBB83.ED181F2C@analog.com \
--to=justin.wojdacki@analog.com \
--cc=danielb@cyclades.com.br \
--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