From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: libusb broken on 2.6.28 x86_64 ?
Date: Thu, 1 Jan 2009 23:24:36 -0800 [thread overview]
Message-ID: <20090102072436.GA3444@suse.de> (raw)
In-Reply-To: <495DBBC1.7040202@rtr.ca>
On Fri, Jan 02, 2009 at 02:01:21AM -0500, Mark Lord wrote:
> Mark Lord wrote:
>> 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 ??
> ..
>
> Mmm.. broken only for 64-bit userspace, it seems.
>
> I've recompiled the same app against 32-bit libs,
> and it works just fine on that 64-bit system,
> as well as on 32-bit systems.
>
> But not when compiled for pure 64-bit operation on a 64-bit system.
>
> Looks tricky .. must be a change somewhere that assumes
> a pointer/long is 32-bits or something.
Which version of libusb, a new one was just released a few weeks ago
that fixes a lot of problems reported in the older libusb versions, and
made things much faster to boot. You might want to check it out.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2009-01-02 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:31 libusb broken on 2.6.28 x86_64 ? Mark Lord
2009-01-02 7:01 ` Mark Lord
2009-01-02 7:24 ` Greg KH [this message]
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=20090102072436.GA3444@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkml@rtr.ca \
/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.