All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] lib: uuid: Improve randomness of uuid values on RANDOM_UUID=y
Date: Thu, 16 May 2019 17:54:12 +0200	[thread overview]
Message-ID: <CAH3KO=3EcNM=p5DwtFRNctNSBWN_r6drywEx6VbaQy9Q6JYMEA@mail.gmail.com> (raw)
In-Reply-To: <abed0a93-1fa0-da30-20bf-ee4d7d89e649@suse.com>

On Thu, May 16, 2019 at 5:14 PM Matthias Brugger <mbrugger@suse.com> wrote:
> On 30/04/2019 21:07, Heinrich Schuchardt wrote:
> >
> > I think we should have a u-class for hardware RNGs as one source of entropy.
>
> Anyone working on this already?

Not me.

> If not I can have a look.

green_light_on(); // :)

> It could be used for
> RPi3 as well (drivers/char/hw_random/bcm2835-rng.c in the Linux kernel). :)
>
> Regards,
> Matthias

-- 
Regards,
Eugeniu.

      reply	other threads:[~2019-05-16 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30  2:53 [U-Boot] [PATCH 0/4] Misc EFI/GPT/UUID fixes Eugeniu Rosca
2019-04-30  2:53 ` [U-Boot] [PATCH 1/4] disk: efi: Fix memory leak on 'gpt guid' Eugeniu Rosca
2019-04-30 17:56   ` Heinrich Schuchardt
2019-04-30  2:53 ` [U-Boot] [PATCH 2/4] disk: efi: Fix memory leak on 'gpt verify' Eugeniu Rosca
2019-04-30 18:01   ` Heinrich Schuchardt
2019-04-30  2:53 ` [U-Boot] [PATCH 3/4] cmd: gpt: fix and tidy up help message Eugeniu Rosca
2019-04-30 18:10   ` Heinrich Schuchardt
2019-04-30  2:53 ` [U-Boot] [PATCH 4/4] lib: uuid: Improve randomness of uuid values on RANDOM_UUID=y Eugeniu Rosca
2019-04-30 19:07   ` Heinrich Schuchardt
2019-05-01 19:08     ` Eugeniu Rosca
2019-05-01 19:51       ` Tom Rini
2019-05-01 22:32         ` Eugeniu Rosca
2019-05-03 16:09           ` Eugeniu Rosca
2019-05-07 12:25             ` Eugeniu Rosca
2019-05-16 15:13     ` Matthias Brugger
2019-05-16 15:54       ` Eugeniu Rosca [this message]

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='CAH3KO=3EcNM=p5DwtFRNctNSBWN_r6drywEx6VbaQy9Q6JYMEA@mail.gmail.com' \
    --to=roscaeugeniu@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.