public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: aman@mistralsoftware.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: K9F2g08u0m Samsung Nand Support
Date: Mon, 20 Sep 2004 12:47:08 +0200	[thread overview]
Message-ID: <1095677227.15940.0.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <KBEHLCHPJHMPJFKMLMOPKEIJCJAA.aman@mistralsoftware.com>

On Mon, 2004-09-20 at 12:17, Amanullah Khan wrote:
> Hi All
> 
> In the K9F2g08u0m Samsung NAND, there is a restriction for programming page
> in a Block. The restriction is,
> "Within a block, the pages must be programmed consecutively from the LSB
> (least significant bit) page of the block to MSB (most significant bit)
> pages of the block. Random page address programming is prohibited".
> 
> I would like to know whether in JFFS2 these restrictions are taken care.

Yes

tglx

      reply	other threads:[~2004-09-20 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 10:17 K9F2g08u0m Samsung Nand Support Amanullah Khan
2004-09-20 10:47 ` Thomas Gleixner [this message]

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=1095677227.15940.0.camel@thomas.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=aman@mistralsoftware.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox