From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: Finding flash type...
Date: Wed, 06 Dec 2006 13:58:59 +0200 [thread overview]
Message-ID: <1165406340.20337.48.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0612060929280.29536@lnxricardw.se.axis.com>
On Wed, 2006-12-06 at 09:31 +0100, Ricard Wanderlof wrote:
> For NAND flash chips I think it would also be nice to get a list of bad
> blocks. This can be most useful when debugging.
Yeah. Once sysfs support is there we could export many useful
information without need to call these syscalls.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-12-06 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 18:53 Finding flash type Siddharth Choudhuri
2006-11-30 9:53 ` Ricard Wanderlof
2006-12-01 8:22 ` Artem Bityutskiy
2006-12-06 1:44 ` Siddharth Choudhuri
2006-12-06 2:05 ` Josh Boyer
2006-12-06 8:31 ` Ricard Wanderlof
2006-12-06 11:58 ` Artem Bityutskiy [this message]
2006-12-06 11:57 ` 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=1165406340.20337.48.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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