Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754483Ab0BVWMf (ORCPT ); Mon, 22 Feb 2010 17:12:35 -0500 Received: from mail-fx0-f219.google.com ([209.85.220.219]:37943 "EHLO mail-fx0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753146Ab0BVWMe (ORCPT ); Mon, 22 Feb 2010 17:12:34 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=BqUftV3tRdXP4ReXxxSCCarMGyKvpB0YpYvIs/2qcak+i4wXnaOe0OQJLPRU7AEvur Dd6MKLBfxb4NDgf7Nd3xl+pZbS9xNUXqJmZ6ie7SAcum5WnCvgSGFQfVsI8Kixx2Aibn 8ra0ETkNOYnpLcCs+zmuf2X8MRM3zqm/t+m+E= Subject: Re: [PATCH 13/15] MTD: add few workarounds to nand system for SmartMedia/xD chips. From: Maxim Levitsky To: Thomas Gleixner Cc: David Woodhouse , linux-mtd , linux-kernel , Alex Dubov , joern , stanley.miao@windriver.com, Vitaly Wool In-Reply-To: References: <1266863982-5258-1-git-send-email-maximlevitsky@gmail.com> <1266863982-5258-14-git-send-email-maximlevitsky@gmail.com> <1266874402.4971.9.camel@maxim-laptop> Content-Type: text/plain; charset="UTF-8" Date: Tue, 23 Feb 2010 00:12:29 +0200 Message-ID: <1266876749.4971.15.camel@maxim-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1126 Lines: 32 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/