public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Jack Lu <jlu@rdmcorp.com>, linux-mtd@lists.infradead.org
Subject: Re: the procedure setting up jffs2
Date: Thu, 12 Sep 2002 20:15:27 -0400	[thread overview]
Message-ID: <3D812E1F.FC5AC8E5@opersys.com> (raw)
In-Reply-To: 20020912231417.0ED47FA8D@denx.denx.de

Wolfgang Denk wrote:
> in message <3D811741.FB5178A@opersys.com> you wrote:
> >
> > The chip you mention is bottom-boot, so the above will very likely wipe-out
> > the bootloader. You probably want to partition your MTD device by modifying
> > the mapping driver and then write the JFFS2 image to another partition then
> > /dev/mtd0. Check drivers/mtd/tqm8xxl.c for an example.
> 
> We (more  or  less)  consider  this  method  of  static  partitioning
> obsolete.  

So do I. Unfortunately, drivers/mtd/cmdline.c is only available in the MTD
CVS for the time being (and Denx's kernel sources ;). Neither 2.5.34 nor
2.4.19 include this code. Instead, they currently include drivers/mtd/bootldr.c
which is only for ARM. Do you have any idea when cmdline.c will be part of the
mainline kernel?

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

  reply	other threads:[~2002-09-13  0:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  8:37 the procedure setting up jffs2 Jack Lu
2002-09-12 22:37 ` Karim Yaghmour
2002-09-12 23:14   ` Wolfgang Denk
2002-09-13  0:15     ` Karim Yaghmour [this message]
2002-09-13  8:35       ` Marius Groeger
2002-09-13  9:07         ` 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=3D812E1F.FC5AC8E5@opersys.com \
    --to=karim@opersys.com \
    --cc=jlu@rdmcorp.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wd@denx.de \
    /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