From: Marcel Holtmann <marcel@holtmann.org>
To: Jeff Sutherland <jeffs@fairwayacademy.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Timeout message from kernel
Date: Sat, 14 Feb 2004 09:53:13 +0100 [thread overview]
Message-ID: <1076748792.18588.152.camel@pegasus> (raw)
In-Reply-To: <200402132310.53881.jeffs@fairwayacademy.org>
Hi Jeff,
> > the endian stuff looks fine in the l2test.c source. What endian do the
> > Coldfire processor use?
>
> Big Endian.
maybe we really have some endian problems here and also in hcitool. The
pkt_type for create_connection is for example uint16 and this explains
why "hcitool info ..." fails. I don't have access to a machine with big
endian, so most of the userspace tools are not fully tested.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-14 8:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 21:36 [Bluez-users] Timeout message from kernel Jeff Sutherland
2004-02-13 0:14 ` Marcel Holtmann
2004-02-13 14:17 ` Jeff Sutherland
2004-02-13 14:22 ` Marcel Holtmann
2004-02-13 15:23 ` Jeff Sutherland
2004-02-13 15:28 ` Marcel Holtmann
2004-02-13 23:19 ` Jeff Sutherland
2004-02-13 23:40 ` Marcel Holtmann
2004-02-13 23:58 ` Jeff Sutherland
2004-02-14 0:06 ` Marcel Holtmann
2004-02-14 4:10 ` Jeff Sutherland
2004-02-14 8:53 ` Marcel Holtmann [this message]
2004-02-14 13:59 ` Jeff Sutherland
2004-02-14 15:02 ` Marcel Holtmann
2004-02-15 22:43 ` Jeff Sutherland
2004-02-15 23:36 ` Marcel Holtmann
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=1076748792.18588.152.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=jeffs@fairwayacademy.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