linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] /dev/rfcomm256 ...?
Date: Wed, 22 Feb 2006 12:45:26 +0100	[thread overview]
Message-ID: <1140608726.4519.22.camel@localhost> (raw)
In-Reply-To: <4F27DFFA-D23F-4B18-B5BE-9A7D2052B746@epfl.ch>

Hi Thomas,

> >>>> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/
> >>>> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a  
> >>>> hard
> >>>> limit, or does anyone know a simple way to increase this? We
> >>>> currently have about 400 devices that should go into that file.
> >>>
> >>> yes, that is a hard limit. We only have 256 minor device numbers
> >>> available and that is actually quite a lot. Describe your use case,
> >>> because creating more than 256 TTY seems not like one of the best  
> >>> ways
> >>> to go.
> >>
> >> Thanks. We have 400 robots, numbered from 1 to 400 (with a couple of
> >> gaps) and equipped with a bluetooth chip (serial port profile). We
> >> don't need to communicate with more than 5 at the same time, but
> >> these 5 robots can be picked at random from the 400. Hence, we need
> >> to be able to establish a connection to all of them at any time.
> >>
> >> Up to now, we only used the first 200 and put all them in /etc/
> >> bluetooth/rfcomm.conf with "bind yes". This worked reasonably well
> >> (apart from the problems with concurrent access that I mentioned in
> >> another post). Is there a more elegant way?
> >
> > rewrite your application to use the RFCOMM socket directly. In this  
> > case
> > you don't have this limit at all.
> 
> Do you have a pointer to some documentation/tutorial?

some years ago, I wrote a detailed email how easy it is to convert a TTY
based application into a RFCOMM socket based application. Besides this
email there exists no further documentation. However you might wanna
take a look at the attest.c source code for an example.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-02-22 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22  9:01 [Bluez-users] /dev/rfcomm256 ...? Thomas Lochmatter
2006-02-22 10:15 ` Marcel Holtmann
2006-02-22 11:04   ` Thomas Lochmatter
2006-02-22 11:08     ` Marcel Holtmann
2006-02-22 11:26       ` Thomas Lochmatter
2006-02-22 11:45         ` Marcel Holtmann [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=1140608726.4519.22.camel@localhost \
    --to=marcel@holtmann.org \
    --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;
as well as URLs for NNTP newsgroup(s).