On 08/24/13 02:14, Hans Petter Selasky wrote: > On 08/24/13 02:44, George Mitchell wrote: >> On 08/23/13 07:11, George Mitchell wrote: >>> On 08/23/13 02:18, Hans Petter Selasky wrote: >>>> On 08/23/13 02:29, George Mitchell wrote: >>>>> On 08/22/13 07:34, Hans Petter Selasky wrote: >>>> > >> Give that the printer works fine with the same code on my amd64 >> machines, does this suggest we have a byte-ordering problem in the >> driver? -- George > > Hi, > > I looked at the code and your debug prints, and it looks like the > usbd_transfer_setup() function is to blame. To get further debugging > here, you need to enable hw.usb.debug=15 and hw.usb.dwcotg.debug=15 or > something like that. > > error = usbd_transfer_setup(uaa->device, &iface_index, > sc->sc_xfer, ulpt_config, ULPT_N_TRANSFER, > sc, &sc->sc_mtx); > > I think this should be trivial to fix one the cause is found. > > --HPS Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- GeorgeReceived on Sat Aug 24 2013 - 16:21:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:40 UTC