Re: [Bluez-users] rfcomm device names

[Marcel Holtmann <marcel@holtmann.org>]

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.
> 
> 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.

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