Merging received chunked messages and writing to document

Modifying the handling of HTTP chunked messages so that once the
terminating chunk has been received all of the chunks are merged
together and written out so that the output can be compared in tests.

BUG=chromium:885915
TEST=Tests run successfully with tast on asuka device

Change-Id: Ib6d74728e948e363fb636a7be80831539837efaa
Reviewed-on: https://chromium-review.googlesource.com/1474745
Commit-Ready: David Valleau <valleau@chromium.org>
Tested-by: David Valleau <valleau@chromium.org>
Reviewed-by: Sean Kau <skau@chromium.org>
7 files changed
tree: d78d922df339c3112250cce9b13def9763d3ee3b
  1. LICENSE
  2. README.md
  3. config/
  4. device_descriptors.cc
  5. device_descriptors.h
  6. ipp_test.cc
  7. ipp_util.cc
  8. ipp_util.h
  9. load_config.cc
  10. load_config.h
  11. load_config_test.cc
  12. op_commands.cc
  13. op_commands.h
  14. server.cc
  15. server.h
  16. smart_buffer.cc
  17. smart_buffer.h
  18. smart_buffer_test.cc
  19. tools/
  20. usb_printer.cc
  21. usb_printer.h
  22. usbip.cc
  23. usbip.h
  24. usbip_constants.h
  25. value_util.cc
  26. value_util.h
  27. virtual_usb_printer.cc
  28. virtual_usb_printer.gyp
README.md

Virtual USB Printer

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.

Motivation

This project was created in order to make on-device tests which check for any regressions in the native USB printing system.

Requirements

  • USBIP - userspace program for binding virtual device to system
  • USBIP kernel modules:
    • CONFIG_USBIP_CORE
    • CONFIG_USBIP_VHCI_HCD
  • Linux Kernel v4.14 - USBIP currently only works on this kernel version

In order to actually “connect” the virtual printer to the system the USBIP program is used.

USBIP is typically used to export real USB devices over a network so that other systems on the network can bind them and treat them as connected devices.

For the purposes of the virtual printer, only the client portion of USBIP is required so that the virtual device can be bound to the system.

How to Use

Run the virtual-usb-printer program:

virtual-usb-printer --descriptors_path=<path>

(Optional) Check the list of exported printers with USBIP:

usbip list -r localhost

Should return something like this:

Exportable USB devices
======================
 - localhost
        1-1: Canon, Inc. : unknown product (04a9:27e8)
           : /sys/devices/pci0000:00/0000:00:01.2/usb1/1-1
           : (Defined at Interface level) (00/00/00)
           : 0 - Printer / Printer Bidirectional (07/01/02)

Bind the virtual printer to the system:

usbip attach -r localhost -b 1-1

Once the device has been attached it should appear in the list of connected USB devices (lsusb), and can be used with the native printing system in Chrome OS.

Configuration

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
    • Only needed for IPP-over-USB printer configurations
  • --record_doc_path - full path to the file used to record documents received from print jobs