public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Schmidt <schmidt@nue.et-inf.uni-siegen.de>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave
Date: Mon, 06 Sep 2004 11:17:55 +0200	[thread overview]
Message-ID: <1094462275.5145.22.camel@notepaq> (raw)
In-Reply-To: <413C24C6.1030102@nue.et-inf.uni-siegen.de>

Hi Michael,

> > this sounds like a chip limitation. What does "hciconfig -a" say?
> 
> Here goes:
> 
> BL-554:
> 
> hci0:	Type: USB
> 	BD Address: 02:00:F4:18:51:74 ACL MTU: 192:8  SCO MTU: 64:8
> 	UP RUNNING PSCAN ISCAN
> 	RX bytes:1787 acl:1 sco:0 events:92 errors:0
> 	TX bytes:543 acl:1 sco:0 commands:44 errors:0
> 	Features: 0xff 0xff 0x0f 0x00
> 	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> 	Link policy: RSWITCH HOLD SNIFF PARK
> 	Link mode: SLAVE ACCEPT
> 	Name: 'BlueZ (0)'
> 	Class: 0x000100
> 	Service Classes: Unspecified
> 	Device Class: Computer, Uncategorized
> 	HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1)
> 	LMP Subver: 0x175
> 	Manufacturer: Cambridge Silicon Radio (10)
> 
> 
> BL-500:
> 
> hci0:	Type: UART
> 	BD Address: 02:00:80:EC:7C:4A ACL MTU: 192:8  SCO MTU: 64:8
> 	UP RUNNING PSCAN ISCAN
> 	RX bytes:897 acl:0 sco:0 events:19 errors:0
> 	TX bytes:634 acl:0 sco:0 commands:20 errors:0
> 	Features: 0xff 0xff 0x0f 0x00
> 	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> 	Link policy: RSWITCH HOLD SNIFF PARK
> 	Link mode: SLAVE ACCEPT
> 	Name: 'BlueZ (0)'
> 	Class: 0x000100
> 	Service Classes: Unspecified
> 	Device Class: Computer, Uncategorized
> 	HCI Ver: 1.1 (0x1) HCI Rev: 0x135 LMP Ver: 1.1 (0x1)
> 	LMP Subver: 0x135
> 	Manufacturer: Cambridge Silicon Radio (10)
> 
> 
> Don't get confused by the apparently weird device addresses; this is 
> part of my project.

you need at least a HCI 16.4 firmware to get it working. Check my pages
and the "hciconfig hci0 revision" command for more information.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-09-06  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 13:47 [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-05 17:53 ` Collin R. Mulliner
2004-09-06  8:30 ` Marcel Holtmann
2004-09-06  8:50   ` Michael Schmidt
2004-09-06  9:17     ` Marcel Holtmann [this message]
2004-09-06 10:38       ` [Bluez-users] general question on the procedure of BlueZ Johannes
2004-09-06 11:21         ` Johannes
2004-09-07  7:56           ` Johannes
2004-09-06 11:43       ` [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-06  8:37 ` Xavier Garreau

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=1094462275.5145.22.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=schmidt@nue.et-inf.uni-siegen.de \
    /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