commit | 4992fb40e0cadb0c663f55bc62340132b87e1f83 | [log] [tgz] |
---|---|---|
author | Bryan Cain <bryancain@chromium.org> | Thu Nov 09 17:33:59 2023 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 15 23:27:18 2023 |
tree | 8039d1210d3bc9c95425a3370b326542ab72cb90 | |
parent | 40a88480cce4e9de01e7469c9b6f8cf909d406d9 [diff] |
Add media-col-database and media-type-supported to printer attributes These advertise support for media type and borderless printing, features newly supported in ChromeOS. BUG=b:309805840 TEST=use Chromium with the enable-borderless-printing feature flag and verify that the borderless checkbox and media type dropdown appear Change-Id: If8ff1a6f2d2224cd2111500f790c8b6176ede3dd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/virtual-usb-printer/+/5018016 Reviewed-by: Benjamin Gordon <bmgordon@chromium.org> Tested-by: Bryan Cain <bryancain@chromium.org> Commit-Queue: Bryan Cain <bryancain@chromium.org>
Virtual USB Printer provides a server which can be used with USBIP in order to emulate a USB printing device and bind it to the system as if it were physically connected to a USB port.
Virtual USB Printer supports both regular USB printers as well as IPP-over-USB devices.
This project was created in order to make on-device tests which check for any regressions in the native USB printing system.
As of https://crrev.com/c/3093381, virtual-usb-printer
is built and installed by default on all test images that support it.
If for some reason you need to build it yourself, you can USE=usbip
when building packages for your board - i.e.
USE="usbip" ./build_packages --board=$BOARD
virtual-usb-printer
relies on usbip
to manifest as a virtual USB device. Most test images seem to come with this built-in by default. If you need to build your own kernel with usbip
support, make sure to build with CONFIG_USBIP_CORE
and CONFIG_USBIP_VHCI_HCD
.virtual-usb-printer
can behave like
For ease of human operation, start virtual-usb-printer
via its Upstart unit. Pass the appropriate arguments to the invocation as needed.
For example, to start and connect the virtual-usb-printer
as an IPP-over-USB printer, issue
start virtual-usb-printer USB_DESCRIPTORS=ippusb_printer.json IPP_ATTRIBUTES=ipp_attributes.json
Consult the Upstart config file to see the arguments understood in this context.
virtual-usb-printer
sends its output to the system log.The printer's USB descriptors and defined IPP attributes can be configured using a JSON file and are loaded at run-time using command line flags. Example configurations can be found in the config/
directory.
The configuration files can be loaded with the following flags:
--descriptors_path
- full path to the JSON file which defines the USB descriptors--attributes_path
- full path to the JSON file which defines the supported IPP attributes--record_doc_path
- full path to the file used to record documents received from print jobs--output_log_dir
- directory path specifying where scan settings will be loggedRefer to these existing tast tests for examples of how to use the virtual-usb-printer
to test the Chromium OS printing stack.