>Number: 190204
>Category: usb
>Synopsis: Please add an empty #define LIBUSB_CALL in libusb.h (1.0+ API)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
The following reply was made to PR usb/190204; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: usb/190204: commit references a PR
Date: Sun, 25 May 2014 18:06:35 + (UTC)
Author: hselasky
Date: Sun May 25 18:06:32 2014
On 25 May 2014, at 12:36, Daniel O'Connor wrote:
> I'll take pictures of them on Monday.
http://imgur.com/a/N8Dto
The non-working one uses an EtronTech EJ188H
The working one uses a VLI VL800 (I think, my photo was pretty hard to read)
--
Daniel O'Connor software and network engineer
for Genes
On 26 May 2014, at 11:59, Daniel O'Connor wrote:
> On 25 May 2014, at 12:36, Daniel O'Connor wrote:
>> I'll take pictures of them on Monday.
>
> http://imgur.com/a/N8Dto
>
> The non-working one uses an EtronTech EJ188H
> The working one uses a VLI VL800 (I think, my photo was pretty hard to re
As a result of Warren Block's suggestion, I decided to try a number of
new and additional tests in order to try to further pin down and/or at
least document the current set of USB 3.0 problems I've been grappling
with.
I have also gathered further information about which chips, specifically
are c
On 05/26/14 05:16, Ronald F. Guilmette wrote:
2) As can be seen in the "desktop2-varlogmessages.txt' log file, on that
one system there were also a number of additional errors logged after the
Hitachi Touro Mobile drive was plugged in:
(probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 2
On 5/26/14, 2:16 PM, Hans Petter Selasky wrote:
On 05/26/14 05:16, Ronald F. Guilmette wrote:
2) As can be seen in the "desktop2-varlogmessages.txt' log file,
on that
one system there were also a number of additional errors logged
after the
Hitachi Touro Mobile drive was plugged in:
(pr
On 05/26/14 08:22, Julian Elischer wrote:
I've seen this pattern a bit too much.
user: I see error X
dev: turn on quirk Y, disabling {lock device, queuing, syncing,
block erase, etc.}
Would it be possible for part of the attach code for drives, to silently
run through a bunch of these co
