lists.openwall.net   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  linux-cve-announce  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, 10 May 2022 02:41:30 +0800
From:   Zhou Yanjie <zhouyanjie@...yeetech.com>
To:     Paul Cercueil <paul@...pouillou.net>
Cc:     jringle@...dpoint.com, shc_work@...l.ru,
        Rob Herring <robh@...nel.org>,
        Paul Boddie <paul@...die.org.uk>,
        "H. Nikolaus Schaller" <hns@...delico.com>,
        Jiaxun Yang <jiaxun.yang@...goat.com>,
        linux-serial@...r.kernel.org,
        linux-mips <linux-mips@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Question about SC16IS752 device tree.

Hi Paul,

On 2022/5/10 上午2:13, Paul Cercueil wrote:
> I can't say for sure that it's your problem, but your bluetooth nodes 
> are missing "reg" properties. 


Unfortunately it doesn't seem to be the problem here, I added "reg" and
the problem persists, and I've looked at other device trees that contain
"brcm,bcm43438-bt", none of them use "reg", and "reg" is not mentioned in
neither "Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt" nor
"Documentation/devicetree/bindings/net/broadcom-bluetooth.yaml".


Best regards!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ