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
| ||
|
Date: Mon, 12 Sep 2016 11:49:07 -0500 From: Timur Tabi <timur@...i.org> To: Warner Losh <imp@...imp.com>, Sebastian Frias <sf84@...oste.net> Cc: Mark Rutland <mark.rutland@....com>, devicetree <devicetree@...r.kernel.org>, Mason <slash.tmp@...e.fr>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers Warner Losh wrote: > Do I have more examples > where FreeBSD has to deviate because the DT is actually Linux > specific and does a poor job of modeling the hardware and instead > reflects the Linux driver model? I have plenty of those... I think it would be a great idea if the FreeBSD and Linux DT maintainers collaborated on cleaning up the DT bindings so that this problem no longer occurs (or at least, not normally). I would love to see some of those examples.
Powered by blists - more mailing lists