How can I get the source code of
kernel 2.6.15
bluez-libs 2.25
bluez-utils 2.25
bluez-hcidump 1.29
btsco 0.41
.....
I cann't find them on bluez.org website.
Thank you.
-----邮件原件-----
发件人: bluez-devel-admin lists.sourceforge.net
[mailto:bluez-devel-adminlists.sourceforge.net] 代表
bluez-devel-requestlists.sourceforge.net
发送时间: 2006年3月24日 12:04
收件人: bluez-devellists.sourceforge.net
主题: Bluez-devel digest, Vol 1 #1963 - 6 msgs
Send Bluez-devel mailing list submissions to
bluez-devellists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/bluez-devel
or, via email, send a message with subject or body 'help'
to
bluez-devel-requestlists.sourceforge.net
You can reach the person managing the list at
bluez-devel-adminlists.sourceforge.net
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of Bluez-devel digest..."
Today's Topics:
1. btsco not working with 3Com 3CREB96 and SE HBH-602
(Tom K)
2. EVT_EXTENDED_INQUIRY_RESULT (Andreas Faerber)
3. Re: EVT_EXTENDED_INQUIRY_RESULT (Marcel Holtmann)
4. Re: btsco not working with 3Com 3CREB96 and SE HBH-602
(Mitja Pufic)
5. Re: EVT_EXTENDED_INQUIRY_RESULT (Andreas Faerber)
6. Re: btsco not working with 3Com 3CREB96 and SE HBH-602
(Tom K)
--__--__--
Message: 1
Date: Thu, 23 Mar 2006 11:23:08 +0000
From: Tom K <tomkrunbox.com>
To: bluez-devellists.sourceforge.net
Subject: [Bluez-devel] btsco not working with 3Com 3CREB96
and SE HBH-602
Reply-To: bluez-devellists.sourceforge.net
First post here, not a developer, but I'm posting here as
advised on the
bluetooth-alsa site.
I have a 3Com 3CREB96 USB dongle and a SonyEricsson HBH-602
headset. I
have the following installed on the laptop:
kernel 2.6.15
bluez-libs 2.25
bluez-utils 2.25
bluez-hcidump 1.29
btsco 0.41
Bluetooth daemons are running, snd-bt-sco is loaded, hci0 is
up, with
the voice 0x0060 setting. The devices are paired
successfully. I now run
btsco -v A1:B2:C3 4:E5:F6,
and get the following response:
btsco v0.41
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
recieved AT*ECBP=?
recieved AT+CLIP=1
recieved AT+CSCS="UTF-8"
recieved AT+CLAN?
In another terminal, I try aplay -B 1000000 -D
plughw:Headset test.wav,
and the following is added in the btsco terminal:
i/o needed: connecting sco...
Can't connect SCO audio channel
: Connection refused
I shut down btsco, and after nearly 30 seconds, I hear a
single beep in
the headset. I run btsco again as above, with the same
initial response,
and run aplay again. This time, the sound file plays through
the
headset, and btsco shows the following:
i/o needed: connecting sco...
connected SCO channel
Done setting sco fd
recieved AT+VGS=12
Sending up speaker change 12
speaker volume: 12 mic volume: 11
driver is not in use
disconnected SCO channel
RFCOMM channel lost
btsco then shuts itself down.
All the above is consistently reproducable. Also, the same
responses are
seen if arecord is used instead of aplay, except of course
that a file
is recorded instead of played on the second attempt.
About a year ago, I had the same headset working correctly
with btsco
and a 3Com BT PCMCIA card, which I unfortunately can no
longer use.
If more info is required - hcidump, logs, etc - let me know.
I am aware
that this is a dev list, so I will understand completely if
nobody is
interested.
All the best
Tom K.
--__--__--
Message: 2
Date: Thu, 23 Mar 2006 14:05:14 +0100
From: Andreas Faerber <afaerberrumms.uni-mannheim.de>
To: bluez-devellists.sourceforge.net
Subject: [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT
Reply-To: bluez-devellists.sourceforge.net
Hello,
We've just received an HCI 2.0 dongle (Belkin/Broadcom) and
I've
recompiled my periodic scan code (on SuSE 10.1b8 w/BlueZ
2.24) to enable
support for EVT_EXTENDED_INQUIRY_RESULT. Unfortunately I
still get the
"old" EVT_INQUIRY_RESULT only; I could not find
an
OCF_EXTENDED_PERIODIC_INQUIRY command or the like so my
expectation was
to simply get back EVT_EXTENDED_INQUIRY_RESULT from
OCF_PERIODIC_INQUIRY
now that our hardware supports it (and I include it in the
filter).
Am I missing anything? Do I need to enable this feature
somewhere?
We want either EVT_INQUIRY_RESULT_WITH_RSSI or
EVT_EXTENDED_INQUIRY_RESULT because we need to read the RSSI
without
connecting.
Regards,
Andreas
--__--__--
Message: 3
Subject: Re: [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT
From: Marcel Holtmann <marcelholtmann.org>
To: bluez-devellists.sourceforge.net
Date: Thu, 23 Mar 2006 14:54:20 +0100
Reply-To: bluez-devellists.sourceforge.net
Hi Andreas,
> We've just received an HCI 2.0 dongle
(Belkin/Broadcom) and I've
> recompiled my periodic scan code (on SuSE 10.1b8
w/BlueZ 2.24) to enable
> support for EVT_EXTENDED_INQUIRY_RESULT. Unfortunately
I still get the
> "old" EVT_INQUIRY_RESULT only; I could not
find an
> OCF_EXTENDED_PERIODIC_INQUIRY command or the like so my
expectation was
> to simply get back EVT_EXTENDED_INQUIRY_RESULT from
OCF_PERIODIC_INQUIRY
> now that our hardware supports it (and I include it in
the filter).
>
> Am I missing anything? Do I need to enable this feature
somewhere?
>
> We want either EVT_INQUIRY_RESULT_WITH_RSSI or
> EVT_EXTENDED_INQUIRY_RESULT because we need to read the
RSSI without
> connecting.
call "hciconfig hci0 inqmode 1" first to switch
the device into the
correct inquiry mode. However the extended inquiry will be
only
supported by Bluetooth 2.1 (aka Lisbon) devices.
You can also check the features with "hciconfig hci0
features" if it
tells you it supports inquiry with RSSI. However in case of
some
Broadcom chips, this doesn't mean anything, because they
support it
anyway even if the features bit is not set.
Regards
Marcel
--__--__--
Message: 4
Date: Thu, 23 Mar 2006 16:22:56 +0100 (CET)
From: Mitja Pufic <msection-one.org>
To: bluez-devellists.sourceforge.net
Subject: Re: [Bluez-devel] btsco not working with 3Com
3CREB96 and SE
HBH-602
Reply-To: bluez-devellists.sourceforge.net
Hello,
This is a very old dongle, with bluecore01 and confirms with
bluetooth
1.0b specification. And as far as I know it has SCO mapped
to PCM and not
HCI, so this is the reason, why your setup is not working.
Check mail
list archive how to change this, or if it is even possible
on this old
chip. PCMCIA version does not have this problem.
br, Mitja
On Thu, 23 Mar 2006, Tom K wrote:
> First post here, not a developer, but I'm posting here
as advised on the
> bluetooth-alsa site.
>
> I have a 3Com 3CREB96 USB dongle and a SonyEricsson
HBH-602 headset. I
have
> the following installed on the laptop:
>
> kernel 2.6.15
> bluez-libs 2.25
> bluez-utils 2.25
> bluez-hcidump 1.29
> btsco 0.41
>
> Bluetooth daemons are running, snd-bt-sco is loaded,
hci0 is up, with the
> voice 0x0060 setting. The devices are paired
successfully. I now run btsco
-v
> A1:B2:C34:E5:F6,
and get the following response:
>
> btsco v0.41
> Device is 1:0
> Voice setting: 0x0060
> RFCOMM channel 1 connected
> recieved AT*ECBP=?
> recieved AT+CLIP=1
> recieved AT+CSCS="UTF-8"
> recieved AT+CLAN?
>
> In another terminal, I try aplay -B 1000000 -D
plughw:Headset test.wav,
and
> the following is added in the btsco terminal:
>
> i/o needed: connecting sco...
> Can't connect SCO audio channel
> : Connection refused
>
> I shut down btsco, and after nearly 30 seconds, I hear
a single beep in
the
> headset. I run btsco again as above, with the same
initial response, and
run
> aplay again. This time, the sound file plays through
the headset, and
btsco
> shows the following:
>
> i/o needed: connecting sco...
> connected SCO channel
> Done setting sco fd
> recieved AT+VGS=12
> Sending up speaker change 12
> speaker volume: 12 mic volume: 11
> driver is not in use
> disconnected SCO channel
> RFCOMM channel lost
>
> btsco then shuts itself down.
>
> All the above is consistently reproducable. Also, the
same responses are
seen
> if arecord is used instead of aplay, except of course
that a file is
recorded
> instead of played on the second attempt.
>
> About a year ago, I had the same headset working
correctly with btsco and
a
> 3Com BT PCMCIA card, which I unfortunately can no
longer use.
>
> If more info is required - hcidump, logs, etc - let me
know. I am aware
that
> this is a dev list, so I will understand completely if
nobody is
interested.
>
> All the best
> Tom K.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
groundbreaking scripting
language
> that extends applications into web and mobile media.
Attend the live
webcast
> and join the prime developer group breaking into this
new coding
territory!
> http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devellists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
--__--__--
Message: 5
Date: Thu, 23 Mar 2006 16:54:04 +0100
From: Andreas Faerber <afaerberrumms.uni-mannheim.de>
To: bluez-devellists.sourceforge.net
Subject: Re: [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT
Reply-To: bluez-devellists.sourceforge.net
Hi Marcel,
>call "hciconfig hci0 inqmode 1" first to
switch the device into the
>correct inquiry mode.
>
Thanks a lot, that worked!
>You can also check the features with "hciconfig
hci0 features" if it
>tells you it supports inquiry with RSSI. However in case
of some
>Broadcom chips, this doesn't mean anything, because
they support it
>anyway even if the features bit is not set.
>
>
The feature is actually listed. The only weird thing I'm
still tracking
down is that I only get inquiry results every five minutes
while it did
work as expected with the previous dongles...
Thanks again,
Andreas
--__--__--
Message: 6
Date: Thu, 23 Mar 2006 17:25:50 +0000
From: Tom K <tomkrunbox.com>
To: bluez-devellists.sourceforge.net
Subject: Re: [Bluez-devel] btsco not working with 3Com
3CREB96 and SE
HBH-602
Reply-To: bluez-devellists.sourceforge.net
Mitja Pufic wrote:
> Hello,
>
> This is a very old dongle, with bluecore01 and confirms
with bluetooth
> 1.0b specification. And as far as I know it has SCO
mapped to PCM and not
> HCI, so this is the reason, why your setup is not
working. Check mail
> list archive how to change this, or if it is even
possible on this old
> chip. PCMCIA version does not have this problem.
>
>
Many thanks for your response.
It's pretty old alright, but hciconfig hci0 revision gives
me
hci0: Type: USB
BD Address: 00:04:76:AD:12:E3 ACL MTU: 128:8 SCO
MTU: 64:8
HCI 10.3
Chip version: BlueCore01b (ES)
SCO mapping: HCI
which looked promising to me. Still, if it's not the right
stuff, I'll
hunt around for another one.
--__--__--
_______________________________________________
Bluez-devel mailing list
Bluez-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
End of Bluez-devel Digest
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http:
//sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$
1720&dat1642
_______________________________________________
Bluez-devel mailing list
Bluez-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
|