Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Sunnan <sunnan@handgranat.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bthid on ppc
Date: Tue, 16 Mar 2004 08:48:32 +0100	[thread overview]
Message-ID: <1079423312.3307.51.camel@pegasus> (raw)
In-Reply-To: <4056493B.5040000@handgranat.org>

Hi Sunnan,

> Thanks for correcting my misinformation.
> Could you please tell me where this suspected non-big-endian safe code 
> is? (Which files and functions, etc?)

I think the problems are in libs2/lib/sdp.c or libs2/lib/sdp_data.c.

> As I said, I've gotten the other bthid to work for repeating intervals a 
> few seconds long. I guess it could still be a big endian problem, but it 
> doesn't crash, it's just unable to read SDP (I don't even know what SDP 
> is! Embarassing, I'm going to read up on that) sometimes.

There is a sdptest program under libs2/test and you can play with.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-03-16  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 22:13 [Bluez-users] bthid on ppc Ben Wilson
2004-03-08  0:13 ` Marcel Holtmann
2004-03-08  5:40   ` Ben Wilson
2004-03-15 23:14     ` Sunnan
2004-03-15 23:35       ` Marcel Holtmann
2004-03-16  0:24         ` Sunnan
2004-03-16  7:48           ` Marcel Holtmann [this message]

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=1079423312.3307.51.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=sunnan@handgranat.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