On Tue, Mar 2, 2010 at 5:42 PM, Olaf Meeuwissen <olaf.meeuwissen at avasys.jp> wrote:
>> Yes, they have a patch for "Expression800" in addition. ?My assumption >> is it would be an issue with any SCSI-only EPSON scanner? ?Or is there >> a small subset of names all models use? > > Hadn't heard about that one, I'll add that to epkowa.desc as well then. > ?Assume it is for the Expression 800 only and not for its Japanese > cousin the GT-9600. Sorry for not including that. The report was for "Expression 800" entry. The following is bug report if interested. https://bugzilla.redhat.com/show_bug.cgi?id=456656 > To be honest, I don't know what the various EPSON scanners with a SCSI > interface report. ?Apparently, most advertise themselves as a "scanner" > device so no special handling should be required. ?Some models however > think that they are "processors" and need the :scsi entry. ?What names > these models report, I don't know, so I will have to rely on whatever > people report. > >>>> Mostly, the epson2.desc values are driven by epkowa developers from >>>> their epkowa.desc. ?Would it be possible for epkowa developers to >>>> provide a ":scsi" line for all SCSI devices? >>> Yes. ?No promises on a release time line but we could send a diff to the >>> list and ask someone with the necessary privileges to commit. >> >> My understanding is that epson2.desc updates are automated based on >> epkowa.desc updates. > > As m. allen noah also pointed out, that's living life dangerously. If epkowa.desc can include those ":scsi" that are known, it would be great. Since the epkowa.desc is used in sane-backend build process, fedora would get your ":scsi" fixes when users install sane-backends and these reports would reduce some... maybe helping isane out in the process. The epson2.desc entries may need further discussion but it sounds like my initial wish of removing a downstream patch can be addressed sometime in near future via a epkowa.desc update. Chris
