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 7cK8TWbxmChy for ; Fri, 11 May 2012 06:30:48 +0200 (CEST) Received: from mail-yw0-f50.google.com (mail-yw0-f50.google.com [209.85.213.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 11 May 2012 06:30:48 +0200 (CEST) Received: by yhjj63 with SMTP id j63so2839552yhj.37 for ; Thu, 10 May 2012 21:30:46 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 11 May 2012 12:30:46 +0800 Message-ID: From: Rodel Miguel Content-Type: multipart/alternative; boundary=14dae9340f2740972b04bfbb330e Subject: [dm-crypt] Writing Asynchronous Block Ciphers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de --14dae9340f2740972b04bfbb330e Content-Type: text/plain; charset=ISO-8859-1 Hello, 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. Thanks in advance for your help! Kind Regards, Rodel --14dae9340f2740972b04bfbb330e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I would like to know if anyone has a tutorial/document link i= n writing a CRYPTO_ALG_TYPE_ABLKCIPHER crypto device driver?=A0 I am lookin= g at drivers/cipher/mv_cesa.c but there are lots of things going on which a= re hardware context related.=A0 I would like to know what the minimum requi= rements for an asynchronous block cipher drivers are before I hand over (DM= A) the collected data to my encryption hardware.

Thanks in advance for your help!

Kind Regards,
Rodel
=
--14dae9340f2740972b04bfbb330e-- 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 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 IrouUUlcWxPv for ; Fri, 11 May 2012 17:21:54 +0200 (CEST) Received: from mail-yw0-f50.google.com (mail-yw0-f50.google.com [209.85.213.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 11 May 2012 17:21:53 +0200 (CEST) Received: by yhjj63 with SMTP id j63so3447146yhj.37 for ; Fri, 11 May 2012 08:21:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4FACBA2B.1090402@redhat.com> References: <4FACBA2B.1090402@redhat.com> Date: Fri, 11 May 2012 11:21:52 -0400 Message-ID: From: Rodel Miguel Content-Type: multipart/alternative; boundary=14dae9340f27c12ddc04bfc44be3 Subject: Re: [dm-crypt] Writing Asynchronous Block Ciphers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz Cc: dm-crypt@saout.de --14dae9340f27c12ddc04bfc44be3 Content-Type: text/plain; charset=ISO-8859-1 Thanks Milan! I will ask around that mailing list. On Fri, May 11, 2012 at 3:05 AM, Milan Broz wrote: > 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 > --14dae9340f27c12ddc04bfc44be3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Milan!=A0 I will ask around that mailing list.

On Fri, May 11, 2012 at 3:05 AM, Milan Broz = <mbroz@redhat.com<= /a>> wrote:
On 05/11/2012 06:30 AM, Ro= del Miguel wrote:
> I would like to know if anyone has a tutorial/document link in
> writing a CRYPTO_ALG_TYPE_ABLKCIPHER crypto device driver? =A0I am
> looking at drivers/cipher/mv_cesa.c but there are lots of things
> going on which are hardware context related. =A0I 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

--14dae9340f27c12ddc04bfc44be3--