On 05/17/16 18:53, Karl Denninger wrote:
If this is a condition of some sort in the device or driver I've not
been able to figure out what it is, or how to force it to clear -- or to
prove whether it's in the device or the ugen driver.
Any ideas?
Hi,
The most easy way to know this for sure, i
On 5/18/2016 02:51, Hans Petter Selasky wrote:
> On 05/17/16 18:53, Karl Denninger wrote:
>> If this is a condition of some sort in the device or driver I've not
>> been able to figure out what it is, or how to force it to clear -- or to
>> prove whether it's in the device or the ugen driver.
>>
>>
On 05/18/16 17:32, Karl Denninger wrote:
If I'm reading this correctly usbdump is showing me exactly what the
device is sending; that is, there is no "driver" involved here (just bus
traffic) -- correct?
Hi,
usbdump is showing exactly what the USB controller driver is sending and
receiving. It
On 5/18/2016 10:46, Hans Petter Selasky wrote:
> On 05/18/16 17:32, Karl Denninger wrote:
>> If I'm reading this correctly usbdump is showing me exactly what the
>> device is sending; that is, there is no "driver" involved here (just bus
>> traffic) -- correct?
> Hi,
>
> usbdump is showing exactly
On 05/18/16 17:53, Karl Denninger wrote:
This is being seen on a Pi2 / 11-Current.
I'm reasonably sure that the Pi2 itself and the base USB code is ok,
however, because there is another USB device also in use by the same
software (it emulates a serial port and so attaches on the serial
driver; i
On 05/18/16 17:53, Karl Denninger wrote:
I'm reasonably sure that the Pi2 itself and the base USB code is ok,
however, because there is another USB device also in use by the same
software (it emulates a serial port and so attaches on the serial
driver;
Hi,
When you are using /dev/usb/X.Y.Z the
On 5/18/2016 11:22, Hans Petter Selasky wrote:
> On 05/18/16 17:53, Karl Denninger wrote:
>> This is being seen on a Pi2 / 11-Current.
>>
>> I'm reasonably sure that the Pi2 itself and the base USB code is ok,
>> however, because there is another USB device also in use by the same
>> software (it
On 05/18/16 18:57, Karl Denninger wrote:
~620ms
Rather consistent note that the device itself, however, is a
power-line (X10) interface and thus the actual timing of a command that
can be sent (the bits are clocked during the zero-crossing of each 60hz
cycle) is approximately this figure.
On 5/18/2016 11:57, Karl Denninger wrote:
> On 5/18/2016 11:22, Hans Petter Selasky wrote:
>> On 05/18/16 17:53, Karl Denninger wrote:
>>> This is being seen on a Pi2 / 11-Current.
>>>
>>> I'm reasonably sure that the Pi2 itself and the base USB code is ok,
>>> however, because there is another USB
On 05/18/16 19:21, Karl Denninger wrote:
One other note -- I looked at libusb but it does not appear that there
is a way to do a "select()" on the input endpoint to determine if data
is available.
LibUSB v2.0 has:
int
libusb20_dev_get_fd(struct libusb20_device *pdev);
--HPS
10 matches
Mail list logo
