All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Gan" <cgan@iders.ca>
To: <rkaiser@sysgo.de>, <linux-mtd@lists.infradead.org>,
	"yaffs list" <yaffs@toby-churchill.org>
Subject: RE: NAND and concat
Date: Wed, 11 Dec 2002 09:57:09 -0600	[thread overview]
Message-ID: <NFBBLPGPLKFIKCCPLALEMEPJCEAA.cgan@iders.ca> (raw)
In-Reply-To: <200212111138.gBBBcYs16381@dagobert.svc.sysgo.de>

I haven't really given it much thought either, but off the top of my head:

  1.  read_ecc and write_ecc
  2.  read_oob and write_oob

But really, I think this may be OK to do.  Since I need something like this
for my project anyways I can give it a shot and test.  Everything else
should be useable as is.

If anyone can think of anything I should watch out for, advice would be
great.

> -----Original Message-----
> From: linux-mtd-admin@lists.infradead.org
> [mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Robert Kaiser
> Sent: Wednesday, December 11, 2002 6:47 AM
> To: Christian Gan; linux-mtd@lists.infradead.org; yaffs list
> Subject: Re: NAND and concat
>
>
> Am Mittwoch, 11. Dezember 2002 00:29 schrieb Christian Gan:
> > Is anyone working on concat for NAND flashes?
>
> Probably not.
>
> > I looked though and realised
> > that there is no functionality at the moment for NAND (i.e. no
> support for
> > read/write oob etc).
>
> I must admit that I knew nothing about NAND flashes when I wrote
> the concat
> stuff (and this hasn't improved much in the meantime) :-(.
>
> OTOH, all the concat stuff does is to redirect calls to the
> hardware drivers,
> so, except for the maintaining of OOB data, what NAND specific
> functionality
> would be needed ?
>
> Rob
>
> ----------------------------------------------------------------
> Robert Kaiser                         email: rkaiser@sysgo.de
> SYSGO AG
> Am Pfaffenstein 14                    phone: (49) 6136 9948-762
> D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

  reply	other threads:[~2002-12-11 15:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  6:02 Which filesystem can live on one flash sector? fred
2002-12-10  7:46 ` Jörn Engel
2002-12-10 17:28 ` Russ Dill
2002-12-10 23:29   ` NAND and concat Christian Gan
2002-12-10 23:58     ` Charles Manning
2002-12-11 15:58       ` Christian Gan
2002-12-11 12:46     ` Robert Kaiser
2002-12-11 15:57       ` Christian Gan [this message]
2003-03-05 19:21       ` [PATCH] NAND and mtdconcat Christian Gan
2003-03-06 12:10         ` Robert Kaiser
2003-03-06 23:10           ` Christian Gan

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=NFBBLPGPLKFIKCCPLALEMEPJCEAA.cgan@iders.ca \
    --to=cgan@iders.ca \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rkaiser@sysgo.de \
    --cc=yaffs@toby-churchill.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.