Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Feb 2011 09:50:09 +0000 (GMT)
From:      Iain Hibbert <plunky@rya-online.net>
To:        c.kworr@gmail.com
Cc:        freebsd-bluetooth@freebsd.org
Subject:   Re: ES 388 (Broadcom based)
Message-ID:  <alpine.NEB.2.00.1102240939190.1619@galant.ukfsn.org>
In-Reply-To: <4D662147.9050101@gmail.com>
References:  <ijvivo$ad4$1@dough.gmane.org> <alpine.NEB.2.00.1102220920130.1133@galant.ukfsn.org> <4D6385E5.4030807@gmail.com> <alpine.NEB.2.00.1102221027380.868@galant.ukfsn.org> <4D653192.4070401@gmail.com> <alpine.NEB.2.00.1102231710570.731@galant.ukfsn.org> <4D662147.9050101@gmail.com>

index | next in thread | previous in thread | raw e-mail

> > > 1298477222.959524>  HCI Event: Number of Completed Packets(0x13) plen 5
> > > 1298477222.973727>  ACL data: handle 0x0006 flags 0x02 dlen 44
> > >      L2CAP(d): cid 0x43 len 40 [psm 1]
> > >          SDP SSA Req: tid 0x1 len 0x23
> > >            pat uuid-128 0x0001 (SDP)
> > >            max 0x5dc
> > >            aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0100
> > > (SrvName)
> > >            cont 00
> > > 1298477222.973799<  ACL data: handle 0x0006 flags 0x02 dlen 15
> > >      L2CAP(d): cid 0x40 len 11 [psm 1]
> > >          SDP SSA Rsp: tid 0x1 len 0x6
> > >            cnt 0x3
> > >            cont 00
> >
> > they ask about SDP records, we have none - that is because even though we
> > do have it, they asked using a 128-bit UUID which IIRC sdpd on FreeBSD
> > does not support (I rewrote sdpd for NetBSD, it does)
>
> Does 5.1 have the code? I'll try to retest it.

actually, I'm wrong - this is because the request is for a 'protocol UUID'
and the FreeBSD sdpd does only check for a single 'service UUID' per
service provider..  I did fix that on NetBSD and the code for 5.1 does
have it but I see that the SDP protocol UUID is not contained in the
"Service Discovery Server" record anyway.. The NetBSD-current code is
completely different though and that would work, eg:

galant: {1} sdpquery -l search sdp
ServiceRecordHandle: 0x00000000
ServiceClassIDList:
    Service Discovery Server
ProtocolDescriptorList:
    L2CAP (PSM 0x0001)
    SDP
BrowseGroupList:
    Public Browse Root
LanguageBaseAttributeIDList:
    en.UTF-8 base 0x0100
ServiceName: "Bluetooth service discovery"
ProviderName: "NetBSD"
VersionNumberList: v1.0

I doubt, however, that this lack is significant..

> > and NAP, which we do tell them all about
>
> Strange. The phone doesn't show anything. I have tried PANU and GN but nothing
> changes.

What phone is it?  I guess that the phone is not set up to access an
external network in this way even though somebody set the probes up to
check it..

iain


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.NEB.2.00.1102240939190.1619>