On Monday, March 24, 2014 9:05:35 AM Oliver Neukum wrote:
> On Sun, 2013-11-17 at 02:40 +, Luke-Jr wrote:
> > I *thought* 3.12 fixed this, but it seems it just gives EOF instead of
> > EIO...
>
> As a response to open()?
IIRC, this was in response to read(). Since I was unable to make any pro
On Sun, 2013-11-17 at 02:40 +, Luke-Jr wrote:
Hi,
> I *thought* 3.12 fixed this, but it seems it just gives EOF instead of EIO...
As a response to open()?
> It seems Linux is trying an interrupt in and a control out, and getting
> ENOENT
> and EPIPE respectively.
>
> Windows (where this w
I *thought* 3.12 fixed this, but it seems it just gives EOF instead of EIO...
It seems Linux is trying an interrupt in and a control out, and getting ENOENT
and EPIPE respectively.
Windows (where this works), on the other hand, is doing a whole bunch of other
things...
Here are USB captures of
On 11/07/2013 02:41 AM, Oliver Neukum wrote:
On Tue, 2013-11-05 at 21:16 +, Luke-Jr wrote:
I am trying to interface with the "HEX" devices sold by http://technobit.eu/
which appear as CDC-ACM devices, but give an I/O error whenever I try to open
them, with some rather unclear error descripti
On Tue, 2013-11-05 at 21:16 +, Luke-Jr wrote:
> I am trying to interface with the "HEX" devices sold by http://technobit.eu/
> which appear as CDC-ACM devices, but give an I/O error whenever I try to open
> them, with some rather unclear error description in dmesg:
>
> [10526714.860052] usb
I am trying to interface with the "HEX" devices sold by http://technobit.eu/
which appear as CDC-ACM devices, but give an I/O error whenever I try to open
them, with some rather unclear error description in dmesg:
[10526714.860052] usb 5-2: new full-speed USB device number 4 using uhci_hcd
[1052
