From: Jeff Sutherland <jeffs@fairwayacademy.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Timeout message from kernel
Date: Sun, 15 Feb 2004 17:43:51 -0500 [thread overview]
Message-ID: <200402151743.51707.jeffs@fairwayacademy.org> (raw)
In-Reply-To: <1076770958.14758.5.camel@pegasus>
On Saturday 14 February 2004 10:02, Marcel Holtmann wrote:
> Hi Jeff,
>
> > > 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.
> >
> > I'll have access to this machine for a little while, so if you have
> > something you'd like to try just send patches this way :-)
>
> try this one to solve the problem with "hcitool info ...".
/> hcitool info 00:0A:4F:00:09:5E
Requesting information ...
bcsp_timed_event: Timeout, retransmitting 1 pkts
BD Address: 00:0A:4F:00:09:5E
Device Name: BlueZ (0)
LMP Version: 1.1 (0x1) LMP Subversion: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link>
<HV2 packets> <HV3 packets> <u-law log> <A-law log>
<CVSD> <paging scheme> <power control> <transparent SCO>
/>
Heh, my hunch was correct for once, looks like it WAS an endian problem :-D
Thanks!
-Jeff
(now to see if I can get a ppp connection going...)
--
Secure your email with Gnu Privacy Guard and Mozilla, the open source
cross platform solution for Windows, Linux, and Mac OS X.
See http://enigmail.mozdev.org/
next prev parent reply other threads:[~2004-02-15 22:43 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
2004-02-14 13:59 ` Jeff Sutherland
2004-02-14 15:02 ` Marcel Holtmann
2004-02-15 22:43 ` Jeff Sutherland [this message]
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=200402151743.51707.jeffs@fairwayacademy.org \
--to=jeffs@fairwayacademy.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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