public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Robert Schwebel <robert@schwebel.de>
To: rkaiser@sysgo.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: 2.4.18-howto?
Date: Tue, 7 May 2002 19:34:30 +0200	[thread overview]
Message-ID: <20020507193430.D15258@schwebel.de> (raw)
In-Reply-To: <200205071614.g47GElw06345@dagobert.svc.sysgo.de>; from rob@sysgo.de on Tue, May 07, 2002 at 06:16:10PM +0200

Hi Robert, 

On Tue, May 07, 2002 at 06:16:10PM +0200, Robert Kaiser wrote:
> > I need the ADNP concaternation layer stuff...
> 
> Does this part cause any specific trouble ? (if so, which ?)

Yes, it doesn't work yet :-) 

# cat /proc/mtd
dev:    size   erasesize  name
# 

This is also interesting, during boot: 
DIL/Net ADNP flash: 0x400000 at 0x2000000
FLASH virtual address: 0xc180d000
CFI: Found no ADNP Flash Bank device at location zero

> > Yes, but it is nearly one year old.
> 
> .. which doesn't necessarily mean it's outdated...

<quote>
This document will attempt to describe setting up the MTD (Memory
Technology Devices), DOC, CFI and the JFFS (Journaling Flash File System)
under Linux versions 2.2.x and 2.4.x
</quote>

According to what I've read on the list it looks like it is currently more
like for 2.4 and 2.5? I've found a hint somewhere in the list archive that
ther exists an 2_4-branch, but trying to check it out results in nearly all
files being removed from my working copy. 

Is there any possibility to find out for a cvs repository which branches do
exist? However, a hint in the howto would be great how things are meant to
work for 2.4 and for 2.5. If you send me the infos I'll send a patch :-)

This: http://www.linux-mtd.infradead.org/ is also terribly outdated (latest
changelog from 2000). And there's no pointer on this page to David's page
at Red Hat, which contains a nice paper about MTD/JFFS. 

> I read in an earlier mail that your problem is with compiling the utils
> (all of them or is it just mkfs.jffs ?). Note that you don't necessarily
> need this program, even if you plan on using jffs2. The only utils you
> really need are erase and eraseall.

Don't ask - some dark magic has blown most of the problems away today, I
can compile the tools now. 

Robert
-- 
 +--------------------------------------------------------+
 | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de |
 | Pengutronix - Linux Solutions for Science and Industry |
 |   Braunschweiger Str. 79,  31134 Hildesheim, Germany   |
 |    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4    |
 +--------------------------------------------------------+

  reply	other threads:[~2002-05-07 17:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <81D0D3538E3CD411AE3C00D0B7474C31C8EE37@jadran.hermes.si>
2002-05-07 13:00 ` 2.4.18-howto? Robert Schwebel
2002-05-07 16:16   ` 2.4.18-howto? Robert Kaiser
2002-05-07 17:34     ` Robert Schwebel [this message]
2002-05-08 10:33       ` 2.4.18-howto? Robert Kaiser
2002-05-03 19:47 2.4.18-howto? Robert Schwebel
2002-05-04 13:11 ` 2.4.18-howto? Robert Schwebel
2002-05-04 19:32   ` 2.4.18-howto? Robert Schwebel
2002-05-07  5:42 ` 2.4.18-howto? Robert Schwebel
2002-05-07 11:19   ` 2.4.18-howto? Thomas Gleixner

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=20020507193430.D15258@schwebel.de \
    --to=robert@schwebel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rkaiser@sysgo.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