From: Martin Karger <martin@evilgenius.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] flexible bt-dongle and bccmd
Date: Mon, 28 Aug 2006 22:36:57 +0200 [thread overview]
Message-ID: <44F353E9.7080406@evilgenius.de> (raw)
In-Reply-To: <1156799873.5613.51.camel@aeonflux.holtmann.net>
Marcel Holtmann wrote:
> Hi Martin,
>
>> i just realised that the problem is not changing the value of remver.
>> the output of hcidump looks good. i can store differnt values in psi or
>> psram.
>>
>> the problem seems to be somewhere else:
>>
>> PSKEY_LMP_REMOTE_VERSION has the value 0x0003 which is for LMP Version
>> 2.0 i guess. but the output of hcitool info shows the wrong value (0x2)
>>
>> # bccmd -i hci1 psget remver
>> The LMP version reported remotely: 0x0003 (3)
>> # hcitool info 00:0A:94:02:12:34
>> Requesting information ...
>> BD Address: 00:0A:94:02:12:34
>> Device Name: BlueZ (1)
>> LMP Version: 1.2 (0x2) LMP Subversion: 0x5dc
>> Manufacturer: Cambridge Silicon Radio (10)
>
> the remote version is the version that the other side will see. However
> what is the reason for playing around with this. You better use psclr to
> remove this key and let the firmware set the default value.
>
first reason to play around with it: the remote version is wrong for
this bt-dongle. i think it should be 0x3 not 0x2.
second reason is, i want to find out, if its possible to "clone" a
bt-device. not only the address but also things like lmp-version or
features of a device.
when i am able to delete/clear a pskey, can also wonder if i can create
a new pskey entry.
bye
martin
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-08-28 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 23:13 [Bluez-devel] flexible bt-dongle and bccmd Martin Karger
2006-08-28 13:38 ` Marcel Holtmann
2006-08-28 17:34 ` Martin Karger
2006-08-28 17:38 ` Brand, Chris
2006-08-28 17:43 ` Martin Karger
2006-08-28 17:46 ` Brand, Chris
2006-08-28 17:52 ` Peter Wippich
2006-08-28 21:17 ` Marcel Holtmann
2006-08-28 20:36 ` Martin Karger [this message]
2006-08-28 23:57 ` Marcel Holtmann
2006-08-29 13:01 ` Martin Karger
2006-08-29 18:00 ` Marcel Holtmann
2006-08-29 16:43 ` Peter Wippich
2006-09-04 16:03 ` Martin Karger
2006-09-04 18:06 ` Marcel Holtmann
2006-09-04 15:57 ` Martin Karger
2006-09-04 18:08 ` 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=44F353E9.7080406@evilgenius.de \
--to=martin@evilgenius.de \
--cc=bluez-devel@lists.sourceforge.net \
/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