| 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: <ae83acc2-534d-49de-a0ec-b2117e5bd4d1@linaro.org>
Date: Fri, 13 Dec 2024 11:31:07 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Renjiang Han <quic_renjiang@...cinc.com>,
Stanimir Varbanov <stanimir.k.varbanov@...il.com>,
Vikash Garodia <quic_vgarodia@...cinc.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>
Cc: Stanimir Varbanov <stanimir.varbanov@...aro.org>,
linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/4] arm64: dts: qcom: add venus node for the qcs615
On 13/12/2024 09:56, Renjiang Han wrote:
> + video-decoder {
> + compatible = "venus-decoder";
> + };
> +
> + video-encoder {
> + compatible = "venus-encoder";
> + };
To be honest, I'd prefer not to continue on doing this.
Adding a compat string to existing yaml might work-around the issue but,
it doesn't really _account_ for the issue.
I've posted a series to fix the problem
20241209-media-staging-24-11-25-rb3-hw-compat-string-v5-0-ef7e5f85f302@...aro.org
Either that or deeper rewrite of venus to remove the above dependencies
should go ahead.
I'm not in favour of willfully continuing to do the wrong thing,
especially when per above, there's a working solution for it.
---
bod
Powered by blists - more mailing lists