From: Greg KH <greg@kroah.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: ark3116_driver@auctionant.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] ark3116: receive returns negative
Date: Thu, 17 May 2007 05:45:25 -0700 [thread overview]
Message-ID: <20070517124525.GC20055@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705161743250.9570@yvahk01.tjqt.qr>
On Wed, May 16, 2007 at 06:04:45PM +0200, Jan Engelhardt wrote:
> Hello,
>
>
> I seem to have problems with the ark3116 driver from 2.6.18.8. This is a
> USB-RS232 cable. Just opening the /dev/ttyUSB0 device
> gives (this is the
> debug output enabled by `modprobe ark3116 debug=1`).
>
> The lines that look suspicious are
> /serial/ark3116.c: 124 < 1 bytes [0xFFFFFFB0]
> and
> /serial/ark3116.c: ark3116_ioctl cmd 0x5401 not supported
Why is this suspicious? We don't support all ioctls for all usb-serial
drivers, perhaps this one is just not really needed?
> I have also seen things like "id here < -62 [0x10]", which would
> indicate that usb_control_msg() returned something very negative
> (-ETIME!?).
But does the driver seem to work properly?
> Issuing a write() on an open fd to ttyUSB does not generate any further
> debug output. Is the driver even complete/functional?
Do you get data through the device properly?
thanks,
greg k-h
next prev parent reply other threads:[~2007-05-17 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 16:04 ark3116: receive returns negative Jan Engelhardt
2007-05-17 12:45 ` Greg KH [this message]
2007-05-17 14:10 ` [linux-usb-devel] " Jan Engelhardt
2007-05-17 14:51 ` Jan Engelhardt
2007-05-17 14:58 ` Greg KH
2007-05-17 14:58 ` [linux-usb-devel] " Greg KH
2007-05-17 15:16 ` [PATCH] " Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070517124525.GC20055@kroah.com \
--to=greg@kroah.com \
--cc=ark3116_driver@auctionant.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.