| 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: <f5ebf0d6-2f0b-45cc-b99a-b786e5df9edc@linaro.org> Date: Wed, 2 Jul 2025 13:06:17 +0100 From: Bryan O'Donoghue <bryan.odonoghue@...aro.org> To: Vikash Garodia <quic_vgarodia@...cinc.com>, Krzysztof Kozlowski <krzk@...nel.org>, Dikshita Agarwal <quic_dikshita@...cinc.com>, Abhinav Kumar <abhinav.kumar@...ux.dev>, Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org> Cc: linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 0/5] Introduce "non-pixel" sub node within iris video node On 02/07/2025 13:01, Vikash Garodia wrote: >> Anyway, in other messages I explained what is missing. You are changing >> existing hardware and you clearly must explain how existing hardware is >> affected, how can we reproduce it, how users are affected. > Exactly all of these i have explained in the commit message. The limitation with > existing hardware binding usage and how my new approach mitigates that limition. > > Coming to usecase, i made a generic comment saying usecases which needs higher > IOVA, i can add the explicit detail about usecase like 8k or higher > concurrencies like 32 or higher concurrent sessions. Why not make this change for a new SoC, instead of an existing ? That way you don't have to make the argument for retrospective ABI changes. --- bod
Powered by blists - more mailing lists