Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libusb1 endian problems
Date: Thu, 24 Jun 2010 11:28:21 +0200	[thread overview]
Message-ID: <hvv8fl$skd$2@dough.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1006240651040.4844@asterix.crazy-teaparty.dyndns.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24-06-10 06:59, Vitus Jensen wrote:
> Hej!
> 
> libusb1 is optimized for little-endian machines *g*, version 1.0.0
> (stable branch) fails on ppc machines because of endian problems. 
> Symptom: lsusb shows no devices

Aha! I've been working about that for *years* on my efika.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMIyU1MkyGM64RGpERAqBZAJ9uw0eK/nSm2Y9Y/uRuGE5t+9M7eACgr2ZQ
o+2QazAE6kgQaWBG4j/GzlE=
=+7gB
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-06-24  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24  4:59 libusb1 endian problems Vitus Jensen
2010-06-24  9:28 ` Koen Kooi [this message]
2010-06-24 12:51 ` [PATCH] libusb1_1.0.8: new recipe Vitus Jensen
2010-06-24 15:16   ` Khem Raj
2010-06-24 19:29     ` [PATCH][STABLE] " Vitus Jensen
2010-09-07 20:41       ` Vitus Jensen

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='hvv8fl$skd$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox