lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 2 Nov 2017 12:06:24 -0700
From:   Florian Fainelli <>
To:     Stefan Wahren <>,
        Florian Fainelli <>
Cc:     Krzysztof Kozlowski <>, Ray Jui <>,
        Eric Anholt <>,
        Rob Herring <>,
        Steffen Trumtrar <>,
        Harald Freudenberger <>,
        Russell King <>,
        "moderated list:BROADCOM BCM2835 ARM ARCHITECTURE" 
        PrasannaKumar Muralidharan <>,
        Scott Branden <>,
        <>, Martin Kaiser <>,
        Herbert Xu <>,
        "maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..." 
        Matt Mackall <>,
        Mark Rutland <>,
        "moderated list:BROADCOM BCM2835 ARM ARCHITECTURE" 
        <>, Sean Wang <>
Subject: Re: [PATCH 00/12] bcm63xx-rng conversion to bcm2835-rng

Hi Stefan,

On 11/02/2017 12:01 PM, Stefan Wahren wrote:
> Hi Florian,
>> Florian Fainelli <> hat am 2. November 2017 um 02:03 geschrieben:
>> Hi,
>> As it usually happens when there is a fair amount of HW IP block re-use,
>> competing implementations show up. In that case the BCM2835 HWRNG driver and
>> the BCM63xx RNG driver have exactly the same register offsets and this is
>> indeed the same piece of HW.
>> This patch series first prepares the bcm2835-rng to be more future proof and
>> support newer platforms, and the last part brings in what is necessary to
>> migrate the bcm63xx-rng over to bcm2835-rng. Finally we delete bcm63xx-rng
>> completely.
>> The reason why BCM2835 RNG was kept over BCM63xx RNG is because the former
>> deals correctly with a warm up count and the number of words available in the
>> FIFO size.
> are these the same patches as in this branch [1]?

Yes, this branch contains these 12 patches.

Powered by blists - more mailing lists