From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fAS-XXqiVjiY for ; Fri, 11 May 2012 09:05:21 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 11 May 2012 09:05:20 +0200 (CEST) Message-ID: <4FACBA2B.1090402@redhat.com> Date: Fri, 11 May 2012 09:05:15 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Writing Asynchronous Block Ciphers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rodel Miguel Cc: dm-crypt@saout.de On 05/11/2012 06:30 AM, Rodel Miguel wrote: > I would like to know if anyone has a tutorial/document link in > writing a CRYPTO_ALG_TYPE_ABLKCIPHER crypto device driver? I am > looking at drivers/cipher/mv_cesa.c but there are lots of things > going on which are hardware context related. I would like to know > what the minimum requirements for an asynchronous block cipher > drivers are before I hand over (DMA) the collected data to my > encryption hardware. This is question for linux-crypt mailing list, http://vger.kernel.org/vger-lists.html#linux-crypto actually, problems with mv_cesa are just dicsussed there... Milan