linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Bruce_Leonard@selinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question about ubimkvol vs. mkfs.ubifs
Date: Mon, 07 Apr 2008 10:37:06 +0300	[thread overview]
Message-ID: <1207553826.8040.58.camel@sauron> (raw)
In-Reply-To: <1207553242.8040.48.camel@sauron>

On Mon, 2008-04-07 at 10:27 +0300, Artem Bityutskiy wrote:
> Hi,
> 
> On Sun, 2008-04-06 at 16:53 -0700, Bruce_Leonard@selinc.com wrote:
> > This is probably a basic question but I'll admit to being lost.  I'm 
> > relatively new to kernel coding and up till now I've been focused on the 
> > very low level stuff, i.e., making hardware work and LEDs go 
> > blinkey-blinkey.  Currently I'm working on a NAND flash driver that I need 
> > to tie into UBI/UBIFS.  I've got the driver working, I can 
> > read/write/erase my flash parts, so the low level stuff that I understand 
> > is good. 
> 
> Is it a secret what is your flash and what is its size? If it is NAND
> I'd recommend you to test it with Adrian's NAND tests:
> git://infradead.org/~ahunter/nand-tests.git

Just a note - be careful with torture test - it may harm. Although we
were unable to wear-out SLC OneNAND after even > 2 000 000 erases.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-04-07  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 23:53 Question about ubimkvol vs. mkfs.ubifs Bruce_Leonard
2008-04-07  0:23 ` Hamish Moffatt
2008-04-07  2:42   ` Bruce_Leonard
2008-04-07  7:27 ` Artem Bityutskiy
2008-04-07  7:37   ` Artem Bityutskiy [this message]
2008-04-07 20:07   ` Bruce_Leonard
2008-04-08  5:43     ` Artem Bityutskiy
2008-04-08 16:45       ` Bruce_Leonard
2008-04-08 16:51         ` Artem Bityutskiy
2008-04-08 16:54         ` Artem Bityutskiy

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=1207553826.8040.58.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=Bruce_Leonard@selinc.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;
as well as URLs for NNTP newsgroup(s).