On 08/25/13 04:44, Hans Petter Selasky wrote:
On 08/24/13 20:21, George Mitchell wrote:
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
On 08/25/13 19:20, George Mitchell wrote:
On 08/25/13 04:44, Hans Petter Selasky wrote:
On 08/24/13 20:21, George Mitchell wrote:
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
On 08/25/13 04:44, Hans Petter Selasky wrote:
On 08/24/13 20:21, George Mitchell wrote:
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
On 08/24/13 20:21, George Mitchell wrote:
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 ...
On 08/25/13 04:44, Hans Petter Selasky wrote:
On 08/24/13 20:21, George Mitchell wrote:
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
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
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
On 08/23/13 02:29, George Mitchell wrote:
On 08/22/13 07:34, Hans Petter Selasky wrote:
Here's the result:
root@pi:/ # usbdump -i usbus0 -f 4 -s 65536
00:26:01.592494 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
00:26:01.593117 usbus0.4
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:
Here's the result:
[...]
(at which point if I type control-c to stop usbdump, the system gets a
fatal kernel mode translation fault, but that's another
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:
Here's the result:
[...]
(at which point if I type control-c to stop usbdump, the system gets a
fatal kernel mode
As I was saying a few minutes ago ...
On 01/27/13 17:32, George Mitchell wrote:
On 01/27/13 14:07, Hans Petter Selasky wrote:
[...] I need output when hw.usb.ulpt.debug=15 to say exactly.
Could you
ask the provider of the binaries to compile having USB_DEBUG set, also
for the
modules.
--HPS
On 08/22/13 13:24, George Mitchell wrote:
As I was saying a few minutes ago ...
On 01/27/13 17:32, George Mitchell wrote:
On 01/27/13 14:07, Hans Petter Selasky wrote:
[...] I need output when hw.usb.ulpt.debug=15 to say exactly.
Could you
ask the provider of the binaries to compile having
On 08/22/13 07:34, Hans Petter Selasky wrote:
On 08/22/13 13:24, George Mitchell wrote:
As I was saying a few minutes ago ...
On 01/27/13 17:32, George Mitchell wrote:
On 01/27/13 14:07, Hans Petter Selasky wrote:
[...] I need output when hw.usb.ulpt.debug=15 to say exactly.
Could you
ask
On Sunday 27 January 2013 17:14:55 George Mitchell wrote:
System: Raspberry Pi
uname: r245840M (Alie Tan's image from 25 January)
By comparison, this Lexmark E120 printer attaches and prints with no
difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says:
ugen0.5: Lexmark International
On Sunday 27 January 2013 17:14:55 George Mitchell wrote:
System: Raspberry Pi
uname: r245840M (Alie Tan's image from 25 January)
By comparison, this Lexmark E120 printer attaches and prints with no
difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says:
ugen0.5: Lexmark International
On Sunday 27 January 2013 19:06:36 George Mitchell wrote:
On 01/27/13 11:33, Hans Petter Selasky wrote:
On Sunday 27 January 2013 17:14:55 George Mitchell wrote:
System: Raspberry Pi
uname: r245840M (Alie Tan's image from 25 January)
By comparison, this Lexmark E120 printer attaches
On 01/27/13 11:33, Hans Petter Selasky wrote:
On Sunday 27 January 2013 17:14:55 George Mitchell wrote:
System: Raspberry Pi
uname: r245840M (Alie Tan's image from 25 January)
By comparison, this Lexmark E120 printer attaches and prints with no
difficulty on FreeBSD-9.1-RELEASE, but on
On 01/27/13 13:15, Hans Petter Selasky wrote:
[...]
Hi,
I don't see any errors in the usbdump trace you sent. So we can at least rule
that out.
Hint: You can filter traffic using the -f option for usbdump.
What does:
usbconfig dump_device_desc dump_curr_config_desc
output? Can you also get
On Sunday 27 January 2013 19:24:01 George Mitchell wrote:
On 01/27/13 13:15, Hans Petter Selasky wrote:
[...]
Hi,
I don't see any errors in the usbdump trace you sent. So we can at least
rule that out.
Hint: You can filter traffic using the -f option for usbdump.
What
On 01/27/13 14:07, Hans Petter Selasky wrote:
On Sunday 27 January 2013 19:24:01 George Mitchell wrote:
On 01/27/13 13:15, Hans Petter Selasky wrote:
[...]
Hi,
I don't see any errors in the usbdump trace you sent. So we can at least
rule that out.
Hint: You can filter traffic using the -f
20 matches
Mail list logo
