On Fri, Dec 21, 2012 at 10:04 AM, Mark A. Greer wrote:
> From: "Mark A. Greer"
>
> Add Device Tree suport to the omap-aes crypto
> driver. Currently, only support for OMAP2 and
> OMAP3 is being added but support for OMAP4 will
> be added in a subsequent patch.
>
> CC: Dmitry Kasatkin
> Signed-o
On Tue, Sep 30, 2008 at 7:33 AM, Herbert Xu <[EMAIL PROTECTED]> wrote:
> Russ Dill <[EMAIL PROTECTED]> wrote:
>>
>> I worked with this a bit, and since the IV has to be modified, it was
>> just easier to check for nbytes less than or equal to block size in my
>
On Mon, Sep 29, 2008 at 6:50 PM, Kevin Coffman <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 29, 2008 at 6:18 PM, Russ Dill <[EMAIL PROTECTED]> wrote:
>> crypto/cts.c currently implements RFC 3962. It deviates from the basic
>> CTS algorithm in two ways. The first
crypto/cts.c currently implements RFC 3962. It deviates from the basic
CTS algorithm in two ways. The first is that it does not support
encrypting data blocks smaller than the underlying block size. Reading
and writing past the end of buffers will occur if it is attempted.
Second, when the length
