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@xxxxxxxxxxxxxxx [mailto:linux-crypto-owner@xxxxxxxxxxxxxxx] On Behalf Of Sebastian Siewior Sent: Friday, January 18, 2008 3:07 PM To: Loc Ho Cc: Herbert Xu; linux-crypto@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
