From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alex Dubov <oakad@yahoo.com>, Vitaly Wool <vitalywool@gmail.com>,
joern <joern@logfs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stanley.miao@windriver.com,
linux-mtd <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 13/15] MTD: add few workarounds to nand system for SmartMedia/xD chips.
Date: Tue, 23 Feb 2010 00:12:29 +0200 [thread overview]
Message-ID: <1266876749.4971.15.camel@maxim-laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.1002222235560.4136@localhost.localdomain>
On Mon, 2010-02-22 at 22:53 +0100, Thomas Gleixner wrote:
> On Mon, 22 Feb 2010, Maxim Levitsky wrote:
>
> > On Mon, 2010-02-22 at 22:25 +0100, Thomas Gleixner wrote:
> > > On Mon, 22 Feb 2010, Maxim Levitsky wrote:
> > >
> > > > * Add an option NAND_SMARTMEDIA that can be set by nand driver
> > > > If set, it will cause separate ID table to be used, which includes
> > > > mask rom devices and new xD cards
> > >
> > > Why that option ? We can just extend the existing ids table and be
> > > done. No extra magic needed.
> > >
> >
> > Two reasons.
> >
> > First of all several xD chips (I belive the Type M) have exactly same
> > IDs like normal nand chips. However they don't report capabilities about
> > pagesize, blocksize, etc.
Sure, I didn't meant the #WP line. Sure it is set by the controller.
I mean WP bit in status report.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-02-22 22:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 18:39 [PATCH 0/15 V10] Work to enable SmartMedia/xD support in mtd Maxim Levitsky
2010-02-22 18:39 ` [PATCH 01/15] MTD: create unlocked versions of {get,put}_mtd_device Maxim Levitsky
2010-02-22 18:39 ` [PATCH 02/15] blktrans: remove mtd_blkcore_priv and switch to per device queue and thread Maxim Levitsky
2010-02-22 18:39 ` [PATCH 03/15] blktrans: Hotplug fixes Maxim Levitsky
2010-02-22 18:39 ` [PATCH 04/15] MTD: mtdblock: test return value of add_mtd_blktrans_dev, because if can fail Maxim Levitsky
2010-02-22 18:39 ` [PATCH 05/15] MTD: call the remove notifiers before assuming it is in use Maxim Levitsky
2010-02-22 18:39 ` [PATCH 06/15] blktrans: allow FTL drivers to export sysfs attributes Maxim Levitsky
2010-02-22 18:39 ` [PATCH 07/15] MTD: nand: make suspend work if device is accessed by kernel threads Maxim Levitsky
2010-02-22 18:39 ` [PATCH 08/15] MTD: nand: make MTD_OOB_PLACE work correctly Maxim Levitsky
2010-02-22 18:39 ` [PATCH 09/15] MTD: nand: cleanup the nand_do_write_ops Maxim Levitsky
2010-02-22 18:39 ` [PATCH 10/15] MTD: nand: make reads using MTD_OOB_RAW affect only ECC validation Maxim Levitsky
2010-02-22 21:20 ` Thomas Gleixner
2010-02-22 21:28 ` Maxim Levitsky
2010-02-22 21:29 ` Thomas Gleixner
2010-02-22 21:34 ` Maxim Levitsky
2010-02-23 7:23 ` Maxim Levitsky
2010-02-23 18:32 ` Maxim Levitsky
2010-02-22 18:39 ` [PATCH 11/15] MTD: nand: add ->badblockbits to specify the minimum number of bits in bad block byte to consider the block good Maxim Levitsky
2010-02-22 18:39 ` [PATCH 12/15] MTD: common module for smartmedia/xD support Maxim Levitsky
2010-02-22 18:39 ` [PATCH 13/15] MTD: add few workarounds to nand system for SmartMedia/xD chips Maxim Levitsky
2010-02-22 21:25 ` Thomas Gleixner
2010-02-22 21:33 ` Maxim Levitsky
2010-02-22 21:53 ` Thomas Gleixner
2010-02-22 22:12 ` Maxim Levitsky [this message]
2010-02-22 18:39 ` [PATCH 14/15] MTD: Add new SmartMedia/xD FTL Maxim Levitsky
2010-02-22 18:39 ` [PATCH 15/15] MTD: Add nand driver for Ricoh xD/SmartMedia reader Maxim Levitsky
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=1266876749.4971.15.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=oakad@yahoo.com \
--cc=stanley.miao@windriver.com \
--cc=tglx@linutronix.de \
--cc=vitalywool@gmail.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