On Wed, Sep 4, 2019 at 5:09 AM Nicolas Dechesne <nicolas.dechesne@xxxxxxxxxx> wrote: > > hi Fabio, > > On Wed, Sep 4, 2019 at 1:27 PM Fabio Estevam <festevam@xxxxxxxxx> wrote: > > > > Add firmware files for Adreno A200. > > > > These firmware files are needed for running the adreno kernel > > driver on i.MX51 and i.MX53 SoCs. > > > > Signed-off-by: Fabio Estevam <festevam@xxxxxxxxx> > > --- > > WHENCE | 2 ++ > > qcom/yamato_pfp.fw | Bin 0 -> 1156 bytes > > qcom/yamato_pm4.fw | Bin 0 -> 9220 bytes > > 3 files changed, 2 insertions(+) > > create mode 100644 qcom/yamato_pfp.fw > > create mode 100644 qcom/yamato_pm4.fw > > > > diff --git a/WHENCE b/WHENCE > > index a8ec628..5e46d33 100644 > > --- a/WHENCE > > +++ b/WHENCE > > @@ -4418,6 +4418,8 @@ File: qcom/a530_zap.b00 > > File: qcom/a530_zap.b01 > > File: qcom/a530_zap.b02 > > File: qcom/a530_zap.mdt > > +File: qcom/yamato_pfp.fw > > +File: qcom/yamato_pm4.fw > > Where did you get these files from in the first place? On which > devices do you expect these firmware files to work? We were recently > discussing how to structure /lib/firmware/qcom more carefully. And the > general consensus that we reached with Rob C. and Bjorn is that if a > firmware is expected to work on a specific device (maybe it is signed) > it should be placed in /lib/firmware/qcom/<device> and if it's > unsigned and can be used on several devices based on the same SoC (dev > boards, ..) then it should be /lib/firmware/qcom/<SOC>. fwiw, the pfp/pm4 fw (later replaced by sqe) are not signed, so /lib/firmware/qcom/ location is fine for these BR, -R
