> -----Original Message----- > From: linux-crypto-owner@xxxxxxxxxxxxxxx <linux-crypto-owner@xxxxxxxxxxxxxxx> On Behalf Of > Josh Boyer > Sent: Thursday, August 15, 2019 1:33 PM > To: Pascal van Leeuwen <pascalvanl@xxxxxxxxx> > Cc: Linux Firmware <linux-firmware@xxxxxxxxxx>; linux-crypto@xxxxxxxxxxxxxxx > Subject: Re: [GIT PULL] inside-secure: add new GPLv2 "mini" firmware for the EIP197 driver > > On Tue, Aug 6, 2019 at 8:54 AM Pascal van Leeuwen <pascalvanl@xxxxxxxxx> wrote: > > > > The following changes since commit dff98c6c57383fe343407bcb7b6e775e0b87274f: > > > > Merge branch 'master' of git://github.com/skeggsb/linux-firmware > > (2019-07-26 07:32:37 -0400) > > > > are available in the git repository at: > > > > > > https://github.com/pvanleeuwen/linux-firmware-clean.git is_driver_fw > > > > for you to fetch changes up to fbfe41f92f941d19b840ec0e282f422379982ccb: > > > > inside-secure: add new GPLv2 "mini" firmware for the EIP197 driver > > (2019-08-06 13:19:44 +0200) > > > > ---------------------------------------------------------------- > > Pascal van Leeuwen (1): > > inside-secure: add new GPLv2 "mini" firmware for the EIP197 driver > > > > WHENCE | 10 ++++++++++ > > inside-secure/eip197_minifw/ifpp.bin | Bin 0 -> 100 bytes > > inside-secure/eip197_minifw/ipue.bin | Bin 0 -> 108 bytes > > 3 files changed, 10 insertions(+) > > create mode 100644 inside-secure/eip197_minifw/ifpp.bin > > create mode 100644 inside-secure/eip197_minifw/ipue.bin > > If this is GPLv2, where is the source code? > Ok, I am not a lawyer so I don't know anything about this license stuff. I just meant it is free to use and do whatever you want with. GPLv2 was agreed with our lawyers for the driver source code, so I just stuck that on the firmware as well (not looking forward to another time consuming pass through the legal department!). If GPLv2 implies that you have to provide source code, then what other license should I use that means freedom, but no source code? Note that: a) I actually *lost* the source code (no joke or excuse!) b) This is for a proprietary in-house micro engine, so while we don't necessarily mind providing the source code, we don't want to provide any documentation or assembler for that. As we definitely don't want to *support* any other people messing with it. Making the source code effectively useless anyway. > josh > > > > diff --git a/WHENCE b/WHENCE > > index 31edbd4..fce2ef7 100644 > > --- a/WHENCE > > +++ b/WHENCE > > @@ -4514,3 +4514,13 @@ File: meson/vdec/gxl_mpeg4_5.bin > > File: meson/vdec/gxm_h264.bin > > > > Licence: Redistributable. See LICENSE.amlogic_vdec for details. > > + > > +-------------------------------------------------------------------------- > > + > > +Driver: inside-secure -- Inside Secure EIP197 crypto driver > > + > > +File: inside-secure/eip197_minifw/ipue.bin > > +File: inside-secure/eip197_minifw/ifpp.bin > > + > > +Licence: GPLv2. See GPL-2 for details. > > + > > diff --git a/inside-secure/eip197_minifw/ifpp.bin > > b/inside-secure/eip197_minifw/ifpp.bin > > new file mode 100644 > > index 0000000..b4a8322 > > Binary files /dev/null and b/inside-secure/eip197_minifw/ifpp.bin differ > > diff --git a/inside-secure/eip197_minifw/ipue.bin > > b/inside-secure/eip197_minifw/ipue.bin > > new file mode 100644 > > index 0000000..2f54999 > > Binary files /dev/null and b/inside-secure/eip197_minifw/ipue.bin differ Regards, Pascal van Leeuwen Silicon IP Architect, Multi-Protocol Engines @ Verimatrix www.insidesecure.com
