From: Manjunath Prabhu <manjunath.mp@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] l2test error
Date: Mon, 10 Jan 2005 18:46:05 +0530 [thread overview]
Message-ID: <2de4657605011005167be988d5@mail.gmail.com> (raw)
In-Reply-To: <1105360635.8652.3.camel@pegasus>
Hi marcel,
i found the bug, in my function i was returning the rssi value(return
rp.rssi) before i did a close(dd)........i just swaped the 2 lines and
the code works fine.......
when u pumped 5000 packets continously .....didn't the connection
close down after some 2000 odd packets ......i found that it does
....must be because of hci buffer getting full and some kind of queue
or buffer overflow??
Regards,
Manjunath
On Mon, 10 Jan 2005 13:37:15 +0100, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Manjunath,
>
> > i am running the l2test with some modifications to the code, the
> > connection reset i am getting after 512 packets is because of this
> > new code,
> >
> > You suggested that it could be an endian bug and asked me to check the
> > hardware.
> > so this is not the problem.....I have added a new function to measure
> > RSSI values along with the throughput l2test measures. The RSSI part
> > of the code is the same as used in 'hcitool'. The 'connection reset by
> > peer' is because on the receiver side i see another error in this RSSI
> > fuction, which resets the connection.
> >
> > the error i get is ,
> > "HCI device open failed:Too many open files"...
> >
> > This is because to get dd i use hci_open_dev (dev_id) fuction, and at
> > the end of the function i close(dd) or hci_close_dev(dd)....but i
> > still get the same error. After 512 packets i don't get the dev_id or
> > dd and hence the error.
>
> why don't you open dd once at the beginning of your program and use it
> every time? On exit you close dd. Show me your code.
>
> Regards
>
> Marcel
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-10 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 10:52 [Bluez-users] l2test error Manjunath Prabhu
2005-01-10 12:37 ` Marcel Holtmann
2005-01-10 13:16 ` Manjunath Prabhu [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=2de4657605011005167be988d5@mail.gmail.com \
--to=manjunath.mp@gmail.com \
--cc=bluez-users@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