From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: libusb broken on 2.6.28 x86_64 ?
Date: Fri, 02 Jan 2009 01:31:08 -0500 [thread overview]
Message-ID: <495DB4AC.50602@rtr.ca> (raw)
I'm trying to use 2.6.28 for the first time on an x86_64 box here
with devices controlled by libusb. The devices work on the first
access, but then fail on all subsequent accesses. Unplugging/replugging
causes them to work again for a single subsequent access.
This is with two completely different USB gadgets:
a VFD alphanumeric display, and an FTDI serial device in bitbang mode.
Did something break in 2.6.28 for libusb devices ??
Cheers
next reply other threads:[~2009-01-02 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:31 Mark Lord [this message]
2009-01-02 7:01 ` libusb broken on 2.6.28 x86_64 ? Mark Lord
2009-01-02 7:24 ` Greg KH
2009-01-02 7:48 ` Mark Lord
2009-01-02 7:51 ` Mark Lord
2009-01-02 7:58 ` Greg KH
2009-01-02 8:15 ` Mark Lord
2009-01-02 8:25 ` Mark Lord
2009-01-02 8:28 ` Greg KH
2009-01-02 9:37 ` Mark Lord
2009-01-02 13:23 ` Alan Stern
2009-01-02 15:44 ` Mark Lord
[not found] <20090102082824.GA4212@suse.de.suse.lists.linux.kernel>
2009-01-02 11:43 ` Marcus Meissner
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=495DB4AC.50602@rtr.ca \
--to=lkml@rtr.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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.