From: Artem Bityutskiy <dedekind@infradead.org>
To: "Musch, Edwin" <musche@dataio.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: AW: UBI - NAND Flash Programming
Date: Wed, 13 May 2009 11:24:10 +0300 [thread overview]
Message-ID: <1242203050.27996.173.camel@localhost.localdomain> (raw)
In-Reply-To: <B538B21A486F9E4CBBE577217764F37701662A61@email2.dataio.internal>
Hi, no offence, just a kind suggestion: we do not appreciate
top-posting here. Well, any technical mailing list does not
appreciate that.
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: The lost context.
Q: What makes top-posted replies harder to read than bottom-posted?
A: Yes.
Q: Should I trim down the quoted part of an email to which I'm replying?
Please, read http://david.woodhou.se/email.html
On Tue, 2009-05-05 at 14:41 -0700, Musch, Edwin wrote:
> I'm working on the device level of the chip, but I'm not using the Linux kernel. Only our customer does but we have to follow the UBI convention.
And we do not appreciate looooooooong lines, just like any technical
mailing.
> We are programming blank chips in production so there is nothing in the NAND flash. This means I do not have to change anything from the Image, right?
Right. The link I posted you last time does have the algorithm
description. It is more generic than you need, but you may easily
simplify it. In your case - you do not have to preserve erase
counters. Just skip bad blocks, that's all.
> So I don't have to make any updates within the main and the spare area, right?
UBI does not touch the spare area. Never.
> With question 2 & 3 I try to say. Do I need to update a dependency if a block will be moved?
No. In UBI all eraseblocks are independent.
> Is there something in the main / spare area of the NAND flash that needs to be updated if a block will be moved into the next good block.
No. You may even randomly re-arrange all eraseblocks, this
should not matter.
> Could you provide me the structure of the table if "NAND_USE_FLASH_BBT" is enabled?
No, sorry. Never used BBT. You should download kernel sources
and dig them, unfortunately.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-05-13 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 15:39 UBI - NAND Flash Programming Musch, Edwin
2009-05-05 5:18 ` Artem Bityutskiy
2009-05-05 21:41 ` AW: " Musch, Edwin
2009-05-13 8:24 ` Artem Bityutskiy [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=1242203050.27996.173.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=musche@dataio.com \
/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