First, allow me to thank you for your participation in these issues. I have been trying to subscribe to the cups mailing lists; but, I have NOT received any response. Is it just due to the weekend?
* Roger Leigh <[EMAIL PROTECTED]> [2006:07:09:19:16:29+0100] scribed: <snip /> > FWIW, the ieee1394 backend is broken. You can try the scsi or ipp > backends which both support firewire: I am always very confused by these "backends". When parport, or samba, it just works. I have tried "ipp", and it does not work for me. Since I do NOT understand how these work; and I have not found any documentation, it may well be that this is pilot error (?) I do NOT even see "scsi" as an option. What am I missing? > From: Michael Sweet <[EMAIL PROTECTED]> > Newsgroups: cups.general > Subject: Re: IEEE1394 backend > > Roger Leigh wrote: > > Is there any reason why the IEEE1394 backend is not built automatically > > if libraw1394 is present? It is not ever a TARGET in backend/Makefile. > > Because it doesn't work. At the time I started working on it to > support the Epson implementation of the PWG print channel stuff, > libraw1394 and the underlying kernel driver didn't support the modes > required by their interface, and the Type B Firewire card Epson sells > supports SCSI-over-Firewire which is supported by the existing SCSI > backend. FWIW, Canon and HP support both SBP2 (SCSI) and IP modes. -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
signature.asc
Description: Digital signature
