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
| ||
|
Message-ID: <08e60e79-8ae3-06ac-779e-d4d99e0ed846@metux.net> Date: Mon, 15 Apr 2019 13:55:49 +0200 From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net> To: Alan Tull <atull@...nel.org>, Federico Vaga <federico.vaga@...n.ch> Cc: Eric Schwarz <eas@...optimization.com>, linux-kernel <linux-kernel@...r.kernel.org>, linux-fpga@...r.kernel.org, linux-pci@...r.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>, linux-x86_64@...r.kernel.org, linux-fpga-owner@...r.kernel.org Subject: Re: Device Description for FPGA Components on x86 system On 10.04.19 16:21, Alan Tull wrote: > I wish I could point you to a complete solution, but there is a lot of> work to be done in this area. Most of what is in the kernel is a low> level in-kernel API [4]. As you correctly state, the hardest part of> this is doing the enumerating if you are on x86 and aren't using> devicetree. ACK. I believe, introducing oftree the right way to go. I've got that on my 2do list, too, but yet too busy w/ other things. So, if you'd like to work on that, I'd highly appreciate that. I'd like to also use oftree overlays for some platform drivers that essentially just initialize/wire up generic drivers to perform some board specific function (eg. drivers/platform/x86/pcengines-apuv2.c). --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists