Hello Olaf, On Oct 11 09:30 Olaf Meeuwissen wrote (shortened): > There are two new plugins, for the Perfection V10/V100 and > the V350, making for a total of 9 plugins. ... > The new plugins should be at: > http://lx1.avasys.jp/iscan/2.3.0/iscan-plugin-gt-f700-2.0.0-0.c2.i386.rpm > http://lx1.avasys.jp/iscan/2.3.0/iscan-plugin-gt-s650-2.0.0-1.c2.i386.rpm
For your information: With your very useful comments in epkowa.desc about which plugin is needed by which scanner (many thanks for it!), it was much easier for me to check on the Avasys web pages all plugins again and now I have those plugins in our newest iscan-proprietary-drivers package: http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-7200-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-7300-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-f500-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-9400-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-f600-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/v1180/iscan-plugin-gt-x750-1.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/2.3.0/iscan-plugin-gt-s600-2.0.0-1.c2.i386.rpm http://lx1.avasys.jp/iscan/2.3.0/iscan-plugin-gt-f700-2.0.0-0.c2.i386.rpm In our newest iscan-firmware package I have this firmware files (with one typical model name which matches to the model shortcut in the associated plugin name): esfw41.bin: GT-F500 esfw32.bin: GT-9400 esfw52.bin: GT-F520 esfw43.bin: GT-F600 esfw54.bin: GT-X750 esfw66.bin: GT-S600 esfw68.bin: GT-F700 An easy to read information which model needs which firmware file would also be of interest (at least for Iscan maintainers of Linux distributors). Currently I did for each firmware file strings firmware-file | grep ^EPSON to get a model name out of the firmware file. I have the plugins and the firmware files in seperated RPMs because this way we can have the firmware file RPM available on all architectures (actually it is even a "noarch" RPM) while the plugins RPM is available only on i386. Feel free to forward this information to other Iscan maintainers of other Linux distributors. Dreaming: If we got a sufficiently free seperated license for the firmware files, I could add full support in YaST for all architectures for those scanners which need firmware and which are supported by a free backend (e.g. snapscan) because only with a sufficiently free license I can simply install the iscan-firmware RPM in YaST (i.e. without the need that I or our legal department or the user must care about license issues). All I need is to have the plugin and its license seperated from the firmware file and its license in your plugin RPMs so that it is 100% clear which license belongs to which part of your "non-free" software (e.g. seperated license text files). "sufficiently free" is e.g. the right to distribute and redistribute your firmware files as verbatim copies together with their license. At the moment it is not 100% clear for us in your license files because your license texts apply both for the plugins and the firmware files. Feel very free to forward my request for a sufficiently free seperated license for the firmware files to your management ;-) > BTW, I'll be attending the OpenPrinting Summit in Lexington in two > weeks. I saw your name mentioned in the wiki, will you be attending? I am afraid, I did not get the approval for the travel from our management. I was told that it should be possible next year. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix at suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/ ######################################################################
