Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933690AbWKQQJ7 (ORCPT ); Fri, 17 Nov 2006 11:09:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933692AbWKQQJ7 (ORCPT ); Fri, 17 Nov 2006 11:09:59 -0500 Received: from caramon.arm.linux.org.uk ([217.147.92.249]:64272 "EHLO caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP id S933690AbWKQQJ6 (ORCPT ); Fri, 17 Nov 2006 11:09:58 -0500 Date: Fri, 17 Nov 2006 16:09:51 +0000 From: Russell King To: Anderson Briglia Cc: "Linux-omap-open-source@linux.omap.com" , linux-kernel@vger.kernel.org, Pierre Ossman , ext David Brownell , Tony Lindgren , "Aguiar Carlos (EXT-INdT/Manaus)" , "Biris Ilias (EXT-INdT/Manaus)" Subject: Re: [patch 1/6] [RFC] Add MMC Password Protection (lock/unlock) support V6 Message-ID: <20061117160951.GD28514@flint.arm.linux.org.uk> Mail-Followup-To: Anderson Briglia , "Linux-omap-open-source@linux.omap.com" , linux-kernel@vger.kernel.org, Pierre Ossman , ext David Brownell , Tony Lindgren , "Aguiar Carlos (EXT-INdT/Manaus)" , "Biris Ilias (EXT-INdT/Manaus)" References: <455DB297.1040009@indt.org.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <455DB297.1040009@indt.org.br> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 696 Lines: 18 On Fri, Nov 17, 2006 at 09:01:11AM -0400, Anderson Briglia wrote: > #define MMC_CAP_BYTEBLOCK (1 << 2) /* Can do non-log2 block > sizes */ > +#define MMC_CAP_LOCK_UNLOCK (1 << 3) /* Host password support > capability */ What's the point of this capability. If the host can do BYTEBLOCK transfers it can send the password commands. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core - 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/