mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v7 0/7] upstream hwrng framework
Date: Wed, 22 Mar 2017 09:42:59 +0100	[thread overview]
Message-ID: <20170322084306.16726-1-o.rempel@pengutronix.de> (raw)

changes v1:
 - initial version

changes v2:
 - drop Freescale RNGC for now. It need more testing
 - add caamrng port
 - fix hwrng_init()
 - fix hwrng_get_first check in get_random_bytes

changes v3:
 - check if hwrng_get_data returns error
 - provide /dev/randomdd random device

changes v4:
 - provide get_crypto_bytes() interface.
 - add CONFIG_ALLOW_PRNG_FALLBACK
 - make cmd_password use get_crypto_bytes
 - add cmd_seed

changes v5:
 - make cmd_seed fail if no VALUE is set

changes v6:
 - reword second patch and remove useless if (bytes > lenght) check.

changes v7:
 - use numbered names: /dev/hwrngN
 - allow to use aliases for device name.

Oleksij Rempel (6):
  lib: random: add get_crypto_bytes interface and use HWRNG if posssible
  caamrng: port to hwrng framework
  fs: add prng device
  crypto: caam - fix RNG buffer cache alignment
  common: password: make use of get_crypto_bytes
  add seed command

Steffen Trumtrar (1):
  drivers: add simple hw_random implementation

 commands/Kconfig              |   6 ++
 commands/Makefile             |   1 +
 commands/seed.c               |  44 +++++++++++++++
 commands/stddev.c             |  29 ++++++++++
 common/password.c             |   6 +-
 drivers/Kconfig               |   1 +
 drivers/Makefile              |   1 +
 drivers/crypto/caam/Kconfig   |   1 +
 drivers/crypto/caam/caamrng.c |  44 +++++----------
 drivers/hw_random/Kconfig     |   6 ++
 drivers/hw_random/Makefile    |   1 +
 drivers/hw_random/core.c      | 125 ++++++++++++++++++++++++++++++++++++++++++
 include/linux/hw_random.h     |  43 +++++++++++++++
 include/stdlib.h              |   1 +
 lib/Kconfig                   |   9 +++
 lib/random.c                  |  56 +++++++++++++++++++
 16 files changed, 344 insertions(+), 30 deletions(-)
 create mode 100644 commands/seed.c
 create mode 100644 drivers/hw_random/Kconfig
 create mode 100644 drivers/hw_random/Makefile
 create mode 100644 drivers/hw_random/core.c
 create mode 100644 include/linux/hw_random.h

-- 
2.11.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2017-03-22  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22  8:42 Oleksij Rempel [this message]
2017-03-22  8:43 ` [PATCH v7 1/7] drivers: add simple hw_random implementation Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 2/7] lib: random: add get_crypto_bytes interface and use HWRNG if posssible Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 3/7] caamrng: port to hwrng framework Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 4/7] fs: add prng device Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 5/7] crypto: caam - fix RNG buffer cache alignment Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 6/7] common: password: make use of get_crypto_bytes Oleksij Rempel
2017-03-22  8:43 ` [PATCH v7 7/7] add seed command Oleksij Rempel

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=20170322084306.16726-1-o.rempel@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=barebox@lists.infradead.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