From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237] helo=passion.cambridge.redhat.com) by pentafluge.infradead.org with esmtp (Exim 3.22 #1 (Red Hat Linux)) id 157Cd8-0004Nk-00 for ; Tue, 05 Jun 2001 09:56:02 +0100 From: David Woodhouse In-Reply-To: <20010605105729.A26674@crystal.2d3d.co.za> References: <20010605105729.A26674@crystal.2d3d.co.za> <20010605104201.A26328@crystal.2d3d.co.za> <25630.991730918@redhat.com> To: Abraham vd Merwe Cc: MTD for Linux Subject: Re: acceptable chip driver limitations Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 10:00:10 +0100 Message-ID: <25766.991731610@redhat.com> Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: abraham@2d3d.co.za said: > No, I'm talking about mtd->read() and mtd->write. Surely they can > return errors? If not, what about physical write/read errors? Sorry, I misunderstood. No, that is not acceptable. You must accept unaligned and odd-sized writes. You can just special-case the first and last read/write cycles, padding writes with 0xFF. See how the existing driver for Intel chips does it. -- dwmw2