public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 16:28:40 +0100	[thread overview]
Message-ID: <1076686120.2671.83.camel@pegasus> (raw)
In-Reply-To: <200402131023.03974.jeffs@fairwayacademy.org>

Hi Jeff,

> > 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 */
> 
> Hmmm...
> [root@Arwen test]# ./l2test -w
> l2test[29184]: Waiting for connection on psm 10 ...
> 
> /bin> l2test -r
> l2test[79]: Waiting for connection on psm 10 ...

why don't you try what I have written? And read what "l2test -h" says.

	l2test -r	/* listen and receive */
	l2test -w	/* listen and send */

Two connections that are listening. How should they connect to each
other?

> Note that from ColdFire, this fails:
> /bin> hcitool cc --role=s 00:0A:4F:00:09:5E
> bcsp_timed_event: Timeout, retransmitting 1 pkts
> Can't create connection: Input/output error
> 
> /bin> hcitool con
> Connections:
> 
> But from the pc, I get this:
> [root@Arwen test]# hcitool cc --role=m 00:0A:4F:00:13:5F
> Can't create connection: Connection timed out
> 
> But now running 'hcitool con' on Coldfire gives this:
> /bin> hcitool con
> Connections:
>         > ACL 00:0A:4F:00:09:5E handle 40 state 1 lm SLAVE
> 
> and from the pc:
> [root@Arwen test]# hcitool con
> Connections:
>         < ACL 00:0A:4F:00:13:5F handle 41 state 1 lm MASTER
> 
> So it seems that hcitool <> hcid, or userland <> kernel is messed up on 
> ColdFire, is that correct?  Remember I'm still a newbie at this...

Maybe this is a role switch problem. Show us both outputs from
"hciconfig -a".

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

  reply	other threads:[~2004-02-13 15:28 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 [this message]
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=1076686120.2671.83.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