On Monday, March 24, 2014 9:05:35 AM Oliver Neukum wrote:
> On Sun, 2013-11-17 at 02:40 +0000, 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 w
> If the flag is cleared (e.g. using setserial) the latency can be
> increased through sysfs (defaults to 16ms).
Thanks, this should help.
(perhaps-waste-of-time-to-read detailed reply to Greg below..)
On Sunday, February 23, 2014 4:14:18 PM Greg KH wrote:
> On Sun, Feb 23, 2014 at 0
If I understand the USB Serial code correctly, at least open devices are
constantly polled by 2 active URBs replaced immediately upon completion,
except when the tty layer throttles them.
With many of these devices, this creates significant USB bandwidth usage. At
least one report found that it
On Monday, November 18, 2013 9:25:49 PM Greg KH wrote:
> Ok, this is making no sense. As you really aren't saying exactly what
> you are trying to do, I'm going to just give up and say you can't do it.
As I said before, I want to use devices only if they aren't already in use.
With hidapi's hidra
On Monday, November 18, 2013 8:29:24 PM Greg KH wrote:
> On Mon, Nov 18, 2013 at 08:19:38PM +0000, Luke-Jr wrote:
> > My software does not interface with keyboards under any condition.
> >
> > Some specific devices I'm working with include:
> > FTDI: Avalon, Butte
On Monday, November 18, 2013 1:37:23 PM Greg KH wrote:
> On Mon, Nov 18, 2013 at 07:10:45AM +0000, Luke-Jr wrote:
> > On Monday, November 18, 2013 6:07:37 AM Greg KH wrote:
> > > > I want my software to ignore devices that are already in use by other
> > > > softwa
On Monday, November 18, 2013 6:07:37 AM Greg KH wrote:
> > I want my software to ignore devices that are already in use by other
> > software. The "other software" might be accessing it via the kernel
> > drivers, or perhaps libusb. My software (in this case) would be using
> > libusb, and need to
On Monday, November 18, 2013 4:40:55 AM Greg KH wrote:
> On Mon, Nov 18, 2013 at 01:44:19AM +0000, Luke-Jr wrote:
> > Is there a way to tell if a USB device is in use or not before requesting
> > the kernel detach drivers?
>
> Not really, sorry.
>
> > I'd def
Is there a way to tell if a USB device is in use or not before requesting the
kernel detach drivers?
I'd define "in use" as either an interface claimed on usbfs or tty/etc
provided by a kernel driver being opened. And "not in use" including "kernel
driver attached, but not interfacing device to
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
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
On Monday, November 04, 2013 4:22:04 PM Alan Stern wrote:
> On Mon, 4 Nov 2013, Luke-Jr wrote:
> > Perhaps I phrased that wrong: I suspect this is a hardware issue or
> > firmware bug, triggering bad error handling in Linux. After upgrading to
> > 3.12, Linux indeed survives
On Monday, November 04, 2013 3:07:18 PM Alan Stern wrote:
> On Mon, 4 Nov 2013, Luke-Jr wrote:
> > On Tuesday, October 29, 2013 2:39:14 PM Alan Stern wrote:
> > > On Mon, 28 Oct 2013, Luke-Jr wrote:
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=63961
> >
On Tuesday, October 29, 2013 2:39:14 PM Alan Stern wrote:
> On Mon, 28 Oct 2013, Luke-Jr wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=63961
> >
> > Kernel version 3.10.15
> >
> > [1774470.503558] hub 2-1.3:1.0: hub_port_status failed (err = -71)
&
https://bugzilla.kernel.org/show_bug.cgi?id=63961
Kernel version 3.10.15
[1774469.764676] usb 2-1: new SuperSpeed USB device number 73 using xhci_hcd
[1774469.777435] usb 2-1: Parent hub missing LPM exit latency info. Power
management will be impacted.
[1774469.779805] usb 2-1: New USB device f
I rather suddenly got a NULL pointer dereference yesterday, running 3.10.9.
Curiously, the same re-occurred on my next boot (shutdown, cold poweron),
around when udev was loading modules. After this, I shutdown again, and turned
the PSU switch off for a few seconds - at the next boot, the proble
On Wednesday, August 29, 2012 6:09:59 PM Greg KH wrote:
> On Sun, Aug 19, 2012 at 02:31:12PM +0000, Luke-Jr wrote:
> > Also worth mentioning: the RMA replacement unit I have also exhibits this
> > same problem, but neither of them do if I connect the same devices to an
> &g
https://bugzilla.kernel.org/show_bug.cgi?id=46201
I have a device that uses a FTDI USB-to-serial chip identified by lsusb as:
Bus 001 Device 051: ID 0403:6014 Future Technology Devices International, Ltd
Only recently, within 24 hours, it will error like this, at which point the
FTDI driver beco
18 matches
Mail list logo
