On 11/18/2017 05:04 AM, Stefan Wahren wrote:
> As Sylvain Garrigues pointed out the BCM2835 RNG block has an
> interrupt. Also in preparation for Florian's upcoming patch series
> add this property to the binding. While we are at it fix the
> indenting of the example.
>
> Link:
On Sat, 18 Nov 2017 14:04:13 +0100, Stefan Wahren
wrote:
> This patch adds the missing interrupt property to the RNG block
> of BCM283x.
>
> Link: https://github.com/raspberrypi/linux/issues/2195
> CC: Florian Fainelli
> Signed-off-by: Stefan
Hi Horia,
On Fri, Apr 13, 2018 at 3:18 AM, Horia Geantă wrote:
> Stripping should happen before set_rsa_pub_pdb() is called since the Protocol
> Data Block contains the input length that is used by the accelerator:
> pdb->f_len = req->src_len;
>
> It should
New Centaur CPU(Family > 6) supprt Random Number Generator, but can't
support MSR_VIA_RNG. Just like VIA Nano.
Signed-off-by: David Wang
---
drivers/char/hw_random/via-rng.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 4/13/2018 3:12 AM, Fabio Estevam wrote:
> Hi Horia,
>
> On Thu, Apr 12, 2018 at 4:12 AM, Horia Geantă wrote:
>
>> Yes, driver needs to strip off leading zeros from input data before feeding
>> it
>> to the accelerator.
>> I am working at a fix.
>
> I was able to to
On Fri, Apr 13, 2018 at 07:38:30AM +0200, Stephan Mueller wrote:
> > The crng_init variable has three states:
> >
> > 0: The CRNG is not initialized at all
> > 1: The CRNG has a small amount of entropy, hopefully good enough for
> >early-boot, non-cryptographical use cases
> > 2: The CRNG is
Am Freitag, 13. April 2018, 14:53:13 CEST schrieb Theodore Y. Ts'o:
Hi Theodore,
>
> This was always the original design intent, but I screwed up and no
> one noticed until Jann reached out to be and said, "Hey this
> doesn't seem to make much sense".
I disagree, but I guess you would have
This patch series adds a new compression algorithm to the kernel and to
the crypto api.
Changes since v6:
- Fixed git apply error due to other recently applied patches
Changes since v5:
- Fixed compile-error due to variable definitions inside #ifdef
CONFIG_ZRAM_WRITEBACK
Changes since v4:
-
The data-format of zBeWalgo, and some other algorithms is unstable. To
identify such unstable algorithms this patch adds a new flag to the
crypto-api.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/zbewalgo.c | 2 +-
include/linux/crypto.h | 6 ++
2 files
zBeWalgo is a completely new algorithm - Currently it is not published
somewhere else right now, googleing it would not show up any results. The
following section describes how the algorithm works.
zBeWalgo itself is a container compression algorithm, which can execute
multiple different
Most compression algorithms published by the crypto api are supporting
multiple different compression levels. The crypto api currently just
calls these algorithms with their default compression level.
This patch enables the caller to specify the compression level.
Signed-off-by: Benjamin Warnke
Up to Version 3 of this patch the decompressor of zbewalgo did not verify
that there is no overflow in the output buffer. Now zbewalgo includes a
safe decompressor which does check for buffer overflows and heap-error.
ZBewalgo and other Algorithms like lz4 include an unsafe decompressor version,
This patch adds zBeWalgo to the crypto api so that zBeWalgo can be used by
zram.
Signed-off-by: Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
---
crypto/Kconfig | 12
crypto/Makefile| 1 +
crypto/testmgr.c | 10 +++
crypto/testmgr.h |
13 matches
Mail list logo