All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Côté" <scote1@Matrox.COM>
To: Alexander Larsson <alex@cendio.se>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Bjorn Wesen <bjorn.wesen@axis.com>,
	jffs-dev@axis.com, mtd@infradead.org
Subject: Re: jffs_erasable_size: offset = 0x0034b000
Date: Fri, 07 Jul 2000 10:17:20 -0400	[thread overview]
Message-ID: <3965E670.79F93BEB@matrox.com> (raw)
In-Reply-To: Pine.LNX.3.96.1000706153526.15928A-100000@biffen.cendio.se

Alexander Larsson wrote:
> 
> On Thu, 6 Jul 2000, David Woodhouse wrote:
> 
> >
> > bjorn.wesen@axis.com said:
> > >  We'll probably leave the 2.0 as it is, and when we switch to 2.4
> > > we'll either use mtd or just keep going with our own little flash.c
> > > (which works fine :)
> >
> > It looks like 2.4 will have the MTD code in it already - Linus included
> > Tuesday's snapshot in 2.4.0-test3-pre4.
> 
> Ouch, it's got jffs too. The invalidate_inode_pages(inode) patch should
> really be applied to it. I haven't had time to test it, but it's almost
> certainly correct, and it is broken without it.
> 

I don't think JFFS is ready to be included in the kernel.  It hasn't
been tested a lot (the 2.2 and 2.4 ports) and I'm sure we'll find many
bugs (the invalidate_inode_pages bug is a good example of a huge bug
that we almost missed).  Just today, I untarred the source code of a
program on a JFFS partition, tried to compile it and got a read error
from jffs_readpage().  

I'm not sure if Linus plans on releasing 2.4 soon but I wouldn't want
JFFS to be released in the kernel is it's full of bugs.

-- 
Sébastien Côté


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-07-07 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1000706132924.20701C-100000@fafner.axis.se>
2000-07-06 13:13 ` jffs_erasable_size: offset = 0x0034b000 David Woodhouse
2000-07-06 13:36   ` Alexander Larsson
2000-07-07 14:17     ` Sébastien Côté [this message]
2000-07-07 14:33       ` Simon Kagstrom
2000-07-09 17:11       ` David Woodhouse
2000-07-10  7:38         ` Simon Kagstrom
     [not found] <39637696.8FD02579@matrox.com>
2000-07-05 21:45 ` 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=3965E670.79F93BEB@matrox.com \
    --to=scote1@matrox.com \
    --cc=alex@cendio.se \
    --cc=bjorn.wesen@axis.com \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=mtd@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.