All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Clarke <eclarke@aminocom.com>
To: John Hall <John.Hall@optionexist.co.uk>
Cc: "Linux MTD list (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Writing JFFS2 image to Nand flash
Date: Mon, 15 Apr 2002 16:18:54 +0100	[thread overview]
Message-ID: <3CBAEF5E.A537C893@aminocom.com> (raw)
In-Reply-To: 541025071C7AC24C84E9F82296BB9B9508051A@OPTEX1.optex.local

John Hall wrote:

> > You should find a grep has them in wbuf.c. Are you setting
> > CONFIG_JFFS2_FS_NAND?
> Yes, CONFIG_JFFS2_FS_NAND is set. wbuf.c doesn't contain these
> functions. I had grepped fs/jffs2/*.[ch] for them.

Doh, helps if I read whats actually there. jffs2_flash_read_oob is a
define in 
os-linux.h. 

> This is the version of wbuf.c that I have:
> [john@morgan jffs2]$ cvs stat wbuf.c
> ===================================================================
> File: wbuf.c            Status: Up-to-date
> 
>    Working revision:    1.1.2.2
>    Repository revision: 1.1.2.2 /home/cvs/mtd/fs/jffs2/wbuf.c,v
>    Sticky Tag:          jffs2-nand-branch (branch: 1.1.2)

Interesting. Mine says revision 1.10. hmmm puzzled. 
I think I'd prompt dwmw2 for some words of wisdom....
Beth

  reply	other threads:[~2002-04-15 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 14:37 Writing JFFS2 image to Nand flash John Hall
2002-04-15 15:18 ` Elizabeth Clarke [this message]
2002-04-15 16:02   ` David Woodhouse
2002-04-15 16:05     ` Elizabeth Clarke
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 14:23 John Hall
2002-04-15 13:42 John Hall
2002-04-15 14:06 ` Elizabeth Clarke
2002-04-15 14:18 ` Tino Keitel
2002-04-12 13:09 John Hall
2002-04-12 13:20 ` Elizabeth Clarke
2002-04-12 10:02 John Hall
2002-04-12 12:47 ` Elizabeth Clarke

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=3CBAEF5E.A537C893@aminocom.com \
    --to=eclarke@aminocom.com \
    --cc=John.Hall@optionexist.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.