From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linux-crypto@vger.kernel.org
Subject: Freescale SEC1 and HMAC
Date: Thu, 24 Apr 2014 15:22:28 +0200 [thread overview]
Message-ID: <53591014.4060408@c-s.fr> (raw)
In the Talitos driver, there is a TALITOS_FTR_HMAC_OK flag which is set
only for SEC2.1
Is there any reason for that ?
According to the doc, SEC2 and SEC1 all seems to support HMAC.
However I have tried it on SEC1 and it seems that it doesn't work
properly when wanting to perform a continuation with several descriptors
(which is the case for the last test vector).
And when reading the doc I get confused: the MPC885 Reference Manual
describes a CONT bit in MDEU Mode Register to be used for implementing
continuation mode. The bits seems to be properly set by the driver, but
the result is not the one expected.
Then when I looks into the addendum document AN2912 "SEC Lite Descriptor
Programmer's Guide", the CONT bit is not included in the mode register,
and for the INT bit (which is supposed to be used to initialize for the
first packet of a continuation) it is said it must be set to 1 at all time.
Do you know anything about that ?
Christophe
reply other threads:[~2014-04-24 13:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53591014.4060408@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).