From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm device names
Date: Tue, 26 Sep 2006 22:10:43 +0200 [thread overview]
Message-ID: <1159301443.800.29.camel@localhost> (raw)
In-Reply-To: <7d3798db0609261300ke3cad5dg88e4def7532aa6c2@mail.gmail.com>
Hi Robert,
> > > Hello all, I'm currently trying to make bluez work with a Maxell
> > > Digital Pen (the DP-201 for interested parties)...
> > >
> > > The question to make this happen is if it is possible to have generic
> > > rfcomm device names? I.e. can rfcomm be configured to use any device
> > > name that I can choose? (These pens only supply data via bluetooth to
> > > a specifically named port so for them to work with linux I need to be
> > > able to set this device/port name somehow)
> > >
> > > Specifically the pen works ok out of the box with the obex transfer
> > > protocol but I'm trying to enable the pens streaming protocol with
> > > connects using the serial interface and expects to find a commport
> > > with a specific name. (I'm aware that this is quite bad programming in
> > > the pens but I cannot change that)
> > >
> > > I'd appreciate any hints/ideas that would take me in the right
> > > direction. Sadly I failed to find any information in the archives for
> > > this issue.
> >
> > I am not sure if I understand you correct, but you simply have to write
> > your own RFCOMM server that registers a SDP record with the correct
> > service name in it.
>
> I think this is correct, however, for a little bit more feedback:
> So far I have others that have used this pen in Windows and they got
> it working by renaming the virtual serial port to the expected name
> (using the widcom stack). If the serial ports are exported as services
> then you're definately spot on (I guess I have some reading to do on
> the SDP for bluetooth).
I am still not sure what renaming means.
> Please forgive me for being confusing, I have had very little
> information to begin with. As for implementing a RFCOMM server and
> exporting it do I build it on top of existing bluez source code or can
> I hook the utility programs rfcomm together with the sdptool somehow?
You can't really hook these to up and I prefer if you write your own
application to make it work properly.
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
next prev parent reply other threads:[~2006-09-26 20:10 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 [this message]
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
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=1159301443.800.29.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