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:   Tue, 15 Dec 2020 16:49:10 +0100
From:   Arnd Bergmann <>
To:     Florian Fainelli <>
Cc:     Bharat Gooty <>,
        Ray Jui <>,
        devicetree <>,
        linux-kernel <>,
        Arnd Bergmann <>,
        Scott Branden <>,
        Ray Jui <>,
        linux-arm-msm <>,
        Andy Gross <>,
        Bjorn Andersson <>,
        Rob Herring <>,
        bcm-kernel-feedback-list <>,
        Zhen Lei <>,
        linux-arm-kernel <>
Subject: Re: [PATCH v2 1/2] arm64: dts: broadcom: clear the warnings caused by
 empty dma-ranges

On Tue, Dec 15, 2020 at 4:41 PM Florian Fainelli <> wrote:
> On 12/15/2020 5:19 AM, Bharat Gooty wrote:
> > Since the IOMMU is disabled and DMA engine is on 32-bit bus, We can not
> > give the complete DDR for the USB DMA.
> > So restricting the usable DAM size to 4GB.
> Thanks, can you make this a proper patch submission along with a Fixes:
> tag that is:
> Fixes: 2013a4b684b6 ("arm64: dts: broadcom: clear the warnings caused by
> empty dma-ranges")

Yes, that would be helpful, though I would appreciate a better description
that explains what is actually going on: is it the device or the bus that
has the 32-bit limitation, and if it is indeed a bug in the device, why do
you pretend that this is a 64-bit device on a 32-bit bus instead (this
could also use a comment in the dts file)?


Powered by blists - more mailing lists