[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e307c4aa-1dae-4d48-ae79-36923372c8e0@oss.qualcomm.com>
Date: Wed, 7 May 2025 21:05:19 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Rob Clark <robdclark@...il.com>, dri-devel@...ts.freedesktop.org
Cc: freedreno@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
Rob Clark <robdclark@...omium.org>, Sean Paul <sean@...rly.run>,
Konrad Dybcio <konradybcio@...nel.org>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Dmitry Baryshkov <lumag@...nel.org>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/msm/adreno: Remove MODULE_FIRMWARE()'s
On 5/7/25 5:47 PM, Rob Clark wrote:
> From: Rob Clark <robdclark@...omium.org>
>
> The driver handles the case where gpu fw is not in the initrd. OTOH it
> doesn't always handle the case where _some_ fw is in the initrd, but
> others are not. In particular the zap fw tends to be signed with an OEM
> specific key, so the paths/names differ across devices with the same
> SoC/GPU, so we cannot sanely list them with MODULE_FIRMWARE().
>
> So MODULE_FIRMWARE() just ends up causing problems without actually
> solving anything. Remove them!
>
> Signed-off-by: Rob Clark <robdclark@...omium.org>
> ---
it's probably the best decision to avoid all the mess..
Reviewed-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Konrad
Powered by blists - more mailing lists