Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750783AbVLOQBh (ORCPT ); Thu, 15 Dec 2005 11:01:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750785AbVLOQBh (ORCPT ); Thu, 15 Dec 2005 11:01:37 -0500 Received: from [85.8.13.51] ([85.8.13.51]:64435 "EHLO smtp.drzeus.cx") by vger.kernel.org with ESMTP id S1750783AbVLOQBg (ORCPT ); Thu, 15 Dec 2005 11:01:36 -0500 Message-ID: <43A1935A.4020902@drzeus.cx> Date: Thu, 15 Dec 2005 17:01:30 +0100 From: Pierre Ossman User-Agent: Mail/News 1.5 (X11/20051129) MIME-Version: 1.0 To: Pierre Ossman , Anderson Lizardo , Anderson Briglia , Anderson Lizardo , linux-omap-open-source@linux.omap.com, linux-kernel@vger.kernel.org, Carlos Eduardo Aguiar , Russell King - ARM Linux , Tony Lindgren , David Brownell Subject: Re: [patch 0/5] Add MMC password protection (lock/unlock) support References: <20051213213208.303580000@localhost.localdomain> <439F4AD6.9090203@indt.org.br> <439FC4A6.4010900@drzeus.cx> <5b5833aa0512141551l638b2c05xcd4588a9370bfa51@mail.gmail.com> <43A11204.2070403@drzeus.cx> <20051215091220.GA29620@flint.arm.linux.org.uk> <43A136F1.3040700@drzeus.cx> <20051215100657.GC32490@flint.arm.linux.org.uk> <20051215134436.GB6211@flint.arm.linux.org.uk> In-Reply-To: <20051215134436.GB6211@flint.arm.linux.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1134 Lines: 30 Russell King wrote: > Reading through the specs I have here, block sizes seem to be all over > the place. The MMC card specs seem to imply that any block size can > be set, from 0 bytes to 2^32-1 bytes. > > The PXA MMC interface specification allows the block size to be anything > from 1 to 1023 bytes, excluding CRC. It is unclear whether a value of 0 > means 1024. > > The MMCI specification allows the block size to be specified as a power > of two, from 1 to 2048 bytes, excluding CRC. > > Pierre - can you comment on wbsd's capabilities please? > > wbsd can do 1 to 4087 (it wants CRC bytes in the size so it goes to 4095 including those). Which means I probably set incorrect sg limits... I guess I should fix that. sdhci, which I'm currently developing, can do up to 0x7FFF. The register is 16-bits, but the upper bit never sticks so I assume it cannot be used. Rgds Pierre - 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/