| 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: Fri, 12 Jan 2024 11:16:37 +0100 From: Köry Maincent <kory.maincent@...tlin.com> To: Manivannan Sadhasivam <mani@...nel.org> Cc: Serge Semin <fancer.lancer@...il.com>, Gustavo Pimentel <gustavo.pimentel@...opsys.com>, Vinod Koul <vkoul@...nel.org>, Cai Huoqing <cai.huoqing@...ux.dev>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org, Herve Codina <herve.codina@...tlin.com> Subject: Re: [PATCH v6 0/6] Fix support of dw-edma HDMA NATIVE IP in remote setup On Wed, 22 Nov 2023 22:42:42 +0530 Manivannan Sadhasivam <mani@...nel.org> wrote: > > For all of that you'll need to fix the > > dw_pcie_edma_find_chip()/dw_pcie_edma_detect() method somehow. > > > > Alternatively, to keep things simple you can convert the > > dw_pcie_edma_find_chip()/dw_pcie_edma_detect() methods to just relying > > on the HDMA settings being fully specified by the low-level drivers. > > > > This looks like the best possible solution at the moment. Thanks for the > insight! > > I will post the patches together with the HDMA enablement ones. Hello Manivannan, What is the status of this series? Do you want to wait for designware-ep.c to be HDMA compatible before merging the fixes? Do you expect us to do something? We can't work on the designware-ep.c driver as we do not have such hardware. Shouldn't fixes be merged as soon as possible? Regards, -- Köry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com
Powered by blists - more mailing lists