public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm device names
Date: Wed, 27 Sep 2006 10:09:17 +0200	[thread overview]
Message-ID: <1159344557.22162.19.camel@localhost> (raw)
In-Reply-To: <7d3798db0609270057y22845a4aoeeb4b18ee0b19a93@mail.gmail.com>

Hi Robert,

> > > The serial ports in windows are mapped to COM1, COM2, COM3 and so on
> > > (like ttyS0, tttyS1 etc). This name (as I have understood it) needs to
> > > be mapped so that it appears as say STREAMING instead. For certain
> > > windows devices you can simply tell it to have a specific name and
> > > this is supposed to be enough.
> > >
> > > I realise it is possible that this could be achieved by a virtual
> > > device in linux linked to the correct rfcomm<x> port as well but my
> > > knowledge in this area is rather small at the moment.
> > >
> > > Since it seemed that it was Bluez that mapped the names for the rfcomm
> > > ports I figured that maybe it was through Bluez it could be achieved.
> >
> > that won't help you at all. The remote device doesn't see the actual
> > port name and so it can not make any difference. You can use udev to
> > name the TTY to whatever you like, but again, this doesn't change
> > anything for your remote device. I think that the word "renaming" was
> > wrong in the first place.
> >
> > You need to know for exactly what service record the remote device is
> > looking. Everything else is pure crap and has nothing do with it.
> 
> Yep, you're correct. I've finally realised that it I need to export a
> service with the correct name (just as you stated in your first reply)
> and that the actual device name is not important at all.
> 
> Can you provide pointers on how to do this with bluez? (I have not
> looked into application development on top of bluez yet).

check out the source code of dund and see how it registers service
records. All extra stuff you need can be found in sdptool.

Regards

Marcel



-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-09-27  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 14:23 [Bluez-users] rfcomm device names Robert Dahlström
2006-09-26 15:21 ` Marcel Holtmann
2006-09-26 20:00   ` Robert Dahlström
2006-09-26 20:10     ` Marcel Holtmann
2006-09-27  5:19       ` Robert Dahlström
2006-09-27  7:37         ` Marcel Holtmann
2006-09-27  7:57           ` Robert Dahlström
2006-09-27  8:09             ` 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=1159344557.22162.19.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