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: Fri, 13 Feb 2004 15:22:02 +0100 [thread overview]
Message-ID: <1076682121.2671.53.camel@pegasus> (raw)
In-Reply-To: <200402130917.46561.jeffs@fairwayacademy.org>
Hi Jeff,
> l2ping from either end works. I didn't cross-compile hcidump for the ColdFire
> board, need to do some makefile wizardry in the parser subdir first. l2test
> on both ends just sits there waiting for something, no doubt I'm not invoking
> it properly. hcidump on the pc end shows the ping packets arriving from
> ColdFire. I guess my connection is basically working. On the ColdFire
> board:
> /bin> hciconfig
> hci0: Type: UART
> BD Address: 00:0A:4F:00:13:5F ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:289 acl:0 sco:0 events:14 errors:0
> TX bytes:554 acl:0 sco:0 commands:14 errors:0
>
> But invoking hcitool still yields:
> /bin> hcitool info 00:0A:4F:00:09:5E
> Requesting information ...
> bcsp_timed_event: Timeout, retransmitting 1 pkts
> Can't create connection: Input/output error
> pid 54: failed 256
>
> bcsp_timed_event: is a kernel error msg. I should probably try to set up an
> l2test session properly next. Any advice?
with the next update of the BCSP driver I will turn this into a debug
message.
Using l2test is easy and with -h you see all the options ;)
One side: l2test -r /* listen and receive */
Other side: l2test -s /* connect and send */
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-13 14:22 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 [this message]
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
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=1076682121.2671.53.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 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.