From: "Loc Ho" <locnho@sbcglobal.net>
To: "'Sebastian Siewior'" <linux-crypto@ml.breakpoint.cc>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
<linux-crypto@vger.kernel.org>
Subject: RE: New Crypto Hardware
Date: Mon, 21 Jan 2008 17:29:13 -0800 [thread overview]
Message-ID: <002301c85c96$32a67a40$5c05420a@amcc.com> (raw)
In-Reply-To: <20080118230721.GA30470@Chamillionaire.breakpoint.cc>
Hi,
If that is the case, then in order to fully support async hashing, I would
need an async version of HASH interface and an async version of digest. Am I
correct? Do you think it will be inconsistent if it is assumed that if the
functional setkey is not called, then it is digest. If it is called, then it
is hash.
-Loc
-----Original Message-----
From: linux-crypto-owner@vger.kernel.org
[mailto:linux-crypto-owner@vger.kernel.org] On Behalf Of Sebastian Siewior
Sent: Friday, January 18, 2008 3:07 PM
To: Loc Ho
Cc: Herbert Xu; linux-crypto@vger.kernel.org
Subject: Re: New Crypto Hardware
* Loc Ho | 2008-01-17 13:25:38 [-0800]:
>>Questions:
>>2. What is the difference between digest and hash type besides one
>>operation on transformation structure (tfm) and the other on
>>descriptor
>(desc)?
>They are used for different things.
>Digest is something like sha1 or md5. You just feed your algoritm with
>data and get a single result. A hash on the other hand has a key which
>is used as a salt, a random initialization string.
>
>[LH]
>Are you referring hash as HMAC mode of MD5/SHA? For normal MD5, use
>digest algorthm. For HMAC mode of MD5, use HASH. Is this correct?
Yes. You request them as hmac(sha1) resp. hmac(md5).
>>3. Currently, cryptodev-2.6 git doesn't work under PPC4xx development
>>board but Denx linux latest works. Have anyone tested on PPC4xx board?
>
>Please define doesn't work.
>
>[LH]
>When I compile and load Denx Linux for my sequoia board, the Kernel
>comes up and I get kernel message. When I compile and load
>cryptodev-2.6.git HEAD with the same config from Denx branch, nothing.
>It seems like cryptodev-2.6 doesn't support the sequoia board. What I
>have to do is patch only crypto file into Denx linux and that seems to
>work for me.
cryptodev-2.6 is almost v2.6.24-rc8 tree + cryptodev patches. If you can
boot v2.6.24-rc8 than you should have no problems with cryptodev. I don't
know the diff between denx-linux & linus-linux.
>Thanks,
>Loc
Sebastian
-
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-01-22 1:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0CA0A16855646F4FA96D25A158E299D603B5A5EB@SDCEXCHANGE01.ad.amcc.com>
2007-11-12 18:19 ` New Crypto Hardware Loc Ho
2007-11-13 1:41 ` Herbert Xu
[not found] ` <0CA0A16855646F4FA96D25A158E299D603EB866F@SDCEXCHANGE01.ad.amcc.com>
2007-12-25 7:32 ` Herbert Xu
[not found] ` <0CA0A16855646F4FA96D25A158E299D603FCC15D@SDCEXCHANGE01.ad.amcc.com>
2008-01-17 11:23 ` Herbert Xu
2008-01-17 18:37 ` Loc Ho
2008-01-17 20:27 ` Sebastian Siewior
[not found] ` <0CA0A16855646F4FA96D25A158E299D603FCC4D7@SDCEXCHANGE01.ad.amcc.com>
2008-01-18 23:07 ` Sebastian Siewior
2008-01-22 1:29 ` Loc Ho [this message]
2008-01-22 23:18 ` Sebastian Siewior
2008-01-23 2:17 ` Loc Ho
2008-01-24 21:07 ` RFC: Async Hash Support Loc Ho
2008-01-24 23:09 ` Sebastian Siewior
2008-01-25 2:45 ` [PATCH 1/1] CryptoAPI: Add " Loc Ho
2008-03-13 11:42 ` Herbert Xu
2008-03-13 17:39 ` Loc Ho
2008-04-10 2:03 ` Loc Ho
2008-04-10 2:29 ` Herbert Xu
2008-04-22 11:16 ` Herbert Xu
2008-04-22 17:23 ` Loc Ho
2008-05-07 13:00 ` Herbert Xu
2008-05-07 13:09 ` Patrick McHardy
2008-05-07 13:15 ` Herbert Xu
2008-05-13 20:27 ` [PATCH 1/3] [CRYPTO] hash: " Loc Ho
2008-05-14 12:40 ` Herbert Xu
2008-05-14 12:44 ` Herbert Xu
2008-05-14 13:26 ` Herbert Xu
2008-05-13 20:29 ` [PATCH 2/3] [CRYPTO] cryptd: " Loc Ho
2008-05-13 20:30 ` [PATCH 3/3] [CRYPTO] tcrypt: " Loc Ho
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='002301c85c96$32a67a40$5c05420a@amcc.com' \
--to=locnho@sbcglobal.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.