From: Juerg Haefliger <juergh@protonmail.com>
To: Antoine Tenart <atenart@kernel.org>
Cc: Juerg Haefliger <juerg.haefliger@canonical.com>,
davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: inside-secure - Add MODULE_FIRMWARE macros
Date: Wed, 27 Apr 2022 07:33:53 +0000 [thread overview]
Message-ID: <20220427093252.00d013c9@smeagol> (raw)
In-Reply-To: <165104455443.3327.8052402101857118285@kwain>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Wed, 27 Apr 2022 09:29:14 +0200
"Antoine Tenart" <atenart@kernel.org> wrote:
> Hello Juerg,
>
> Quoting Juerg Haefliger (2022-04-27 09:03:49)
> > +
> > +MODULE_FIRMWARE("inside-secure/eip197b/ifpp.bin");
> > +MODULE_FIRMWARE("inside-secure/eip197b/ipue.bin");
> > +MODULE_FIRMWARE("inside-secure/eip197d/ifpp.bin");
> > +MODULE_FIRMWARE("inside-secure/eip197d/ipue.bin");
> > +MODULE_FIRMWARE("inside-secure/eip197_minifw/ifpp.bin");
> > +MODULE_FIRMWARE("inside-secure/eip197_minifw/ipue.bin");
>
> There's also the old location when the EIP197b firmwares were at the
> root of the linux-firmware repo. The driver still supports it, so I
> guess those two should have a MODULE_FIRMWARE entry too.
Hi Antoine,
Yeah, I was wondering about that myself but wasn't sure if it should be added.
Will add it then and send a v2.
...Juerg
> Thanks,
> Antoine
[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
prev parent reply other threads:[~2022-04-27 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:03 [PATCH] crypto: inside-secure - Add MODULE_FIRMWARE macros Juerg Haefliger
2022-04-27 7:29 ` Antoine Tenart
2022-04-27 7:33 ` Juerg Haefliger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220427093252.00d013c9@smeagol \
--to=juergh@protonmail.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=juerg.haefliger@canonical.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox