From: "Vikas Sinha" <compuvikas@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci inquiry error with name scan
Date: Mon, 4 Jun 2007 18:58:06 +0530 [thread overview]
Message-ID: <1ab01fb50706040628x9d1ac47xac985b34d8f742e6@mail.gmail.com> (raw)
In-Reply-To: <20070601163447.0c678f57@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 4110 bytes --]
Thanks Andreas,
I am waiting for ur patch. If there anything I can do please tell me. I took
other way to overcome this problem. I have allocated MAX space for array of
inquery structure (i.e. 256) and then doing inquiry and making it memset
zero after using its result. I think ur right .
On 6/1/07, Andreas Gaufer <Andreas.Gaufer@bluecellnetworks.com> wrote:
>
> Hi Avaited,
>
> i believe this is a bug in hci.c in the bluez-libs package. It returns
> wrong names if multiple hci_read_remote_name calls are done in a short
> period of time.
>
> hci_send_req which is used by hci_read_remote_name returns data of the
> first EVT_REMOTE_NAME_REQ_COMPLETE that occurs on the device even if it
> does not match the bdaddres that was requested.
>
> This problem was also already noticed by Sjoerd Simons in June 2004 and
> sent to this list with the subject "btaddr <-> name bug ?" (1)
>
> I prepared a patch that should fix that problem. I will provide that
> patch on this list as soon as I'm finished with stress-testing it.
>
> Greetings
>
> Andy
>
>
> 1) http://thread.gmane.org/gmane.linux.bluez.devel/2489/focus=2491
>
>
> On Tue, 26 Dec 2006 04:47:47 +0000 (UTC)
> Avaited <compuvikas@gmail.com> wrote:
>
> > hi all
> >
> > I am facing a big problem with hci layer process. I have developed a
> platform
> > and http wraper for bluetooth services using bluez. I am searching all
> device
> > present in vicinity by using hci.c function 'hci_scan()'. later for each
> > number(BDADDR) i am searching its name by hci_read_remote_name(). Most
> of the
> > time I am getting right name(i.e. what ever name i am giving to my
> devices ) But
> > some time name get swaped with some one. Lisk in my case my mobile name
> was
> > SHARK and my Machine name was VIKAS [0], VIKAS[1], my friends mobile was
> GOLD,
> > SILVER. but when I had done scan name it returned me my mobile,s name as
> > VIKAS[1]. I am surprise why this happened.
> >
> > Is there any problem with present bluez stack I am using
> > bluez-bluefw-1.0-6
> > bluez-pin-0.23-3
> > bluez-hcidump-1.11-1
> > bluez-libs-2.10-2
> > bluez-utils-2.10-2.1
> > on redhat 4.0 Enterprise Edition
> > with kernel 2.6.9-5.EL i386
> > int getScanName(bdaddr_t *device_bt,char * device_name,bdaddr_t
> *dongle_bt)
> > {
> > if((s = GetScanSock(dongle_bt)) < 0) // this will connect to
> local dongle
> > {
> > ERR_LOG(ERR,"Unable to open socket");
> > return -s;
> > }
> > if(hci_read_remote_name(s,
> device_bt,sizeof(device_name),device_name,0) < 0)
> > {
> > ERR_LOG(DBG,"No Name found");
> > close(s);
> > return -NOTFOUND;
> > }
> > ERR_LOG(DBG,"Name of Device hci scan [%s] DeviceBT
> > [%s]",device_name,device_bt);
> > close(s);
> > return 0;
> > }
> > this function get called for each device found in scan.
> >
> >
> > I am in deep trouble to know what is problem with this.
> >
> > Please help
> >
> >
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
--
Impossible
itself contain
I M Possible
Vikas
[-- Attachment #1.2: Type: text/html, Size: 6198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-06-04 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 4:47 [Bluez-devel] hci inquiry error with name scan Avaited
2007-06-01 14:34 ` Andreas Gaufer
2007-06-04 13:28 ` Vikas Sinha [this message]
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=1ab01fb50706040628x9d1ac47xac985b34d8f742e6@mail.gmail.com \
--to=compuvikas@gmail.com \
--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