All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: linux-crypto@vger.kernel.org
Subject: Crypto Hardware Drivers?
Date: Wed, 08 Dec 2010 16:13:48 -0500	[thread overview]
Message-ID: <4CFFF50C.4000406@borg.org> (raw)

Is this the right place to ask questions about writing a Linux device 
driver to make some crypto hardware on an ARM SoC work under the Linux 
crypto API?

I have some hardware documentation that I don't yet know whether I can 
talk about (I know, if I can't then the driver will have difficulty 
being be GPL, and if it isn't an open license, it won't work...).

I have some sample code for the hardware that is an incomplete and 
obsolete Linux module.
I can see source code examples for things like the Padlock, IXP4xx 
hardware, etc.
I have never touched any Linux kernel crypto code before this project.  
(I have done some stuff in userland, so the fact of crypto doesn't scare 
me.)

At the moment I am trying to understand things like the parameter to 
crypto_register_alg(), how that is different from crypto_register_ahash()...

And for a DMA case how data moves and who owns the memory. 

Stuff like that...

Yes, the sources and Google are my friends, and 
Documentation/crypto/api-intro.txt has a very promising title but 
doesn't say terribly much inside.

Are there any obvious key resources I should know about?  (Any general 
pointers would be appreciated, too.)


Thanks,

-kb

             reply	other threads:[~2010-12-08 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 21:13 Kent Borg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-13 17:43 Crypto Hardware Drivers? Tobias Karnat
2010-12-13 17:53 ` Kent Borg

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=4CFFF50C.4000406@borg.org \
    --to=kentborg@borg.org \
    --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.