Tim,
Unfortunately, not all Ricoh printers supports 1284DeviceID in MIB. Newer laser models, do through private MIB, older laser models and Ink based printers do not expose it through MIB. Different product families (printers using different controllers) may use different MIB also. Ricoh has made quite a few acquisitions in the past...
I'd like to suggest making s-c-p more or less aligned with CUPS mechanism of matching drivers. If user can find a matching driver using CUPS web interface, he/she might expect S-C-P only to do better.
I'd like to propose the following:
1. I'll see whether I can put in Ricoh DeviceIdOID in CUPS. Currently, in cups.1.4.x, only Lexmark is having a special deviceIdOID. 2. Do you think it's possible to build a fall-back mechanism in s-c-p if CUPS cannot find "device-id"? (It's much easier to change PPD file or software than requiring printer firmware change)
Are you planning to go to Red Hat Summit in Boston this June?
Thanks George
-----Original Message----- From: Tim Waugh [mailto:twaugh@redhat.com] Sent: Wednesday, May 05, 2010 4:39 AM To: George Liu Cc: Till Kamppeter; system-config-printer-devel@lists.fedorahosted.org; Bin Li Subject: RE: Tagging PPD package with DeviceID.
On Tue, 2010-05-04 at 18:02 -0700, George Liu wrote:
If printer does not support 1284DeviceID mib, do you think you can flex s-c-p a bit so it could "generate" deviceID based on make-and-model IPP attribute?
As I've mentioned before, I would like to investigate first whether it really is not possible to obtain the real IEEE 1284 Device ID from the device. Printers have been given IEEE 1284 Device IDs for much, much longer than the Printer MIB standard has been around.
Are you saying that Ricoh network printers don't expose their Device IDs at all, via any interface?
Tim. */