From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ users In-Reply-To: <7d3798db0609270057y22845a4aoeeb4b18ee0b19a93@mail.gmail.com> References: <7d3798db0609260723y34fe4dcam37b9d9a9264ba282@mail.gmail.com> <1159284114.800.6.camel@localhost> <7d3798db0609261300ke3cad5dg88e4def7532aa6c2@mail.gmail.com> <1159301443.800.29.camel@localhost> <7d3798db0609262219g49e2b77aie498f6b1c7f9cbf7@mail.gmail.com> <1159342675.22162.2.camel@localhost> <7d3798db0609270057y22845a4aoeeb4b18ee0b19a93@mail.gmail.com> Date: Wed, 27 Sep 2006 10:09:17 +0200 Message-Id: <1159344557.22162.19.camel@localhost> Mime-Version: 1.0 Subject: Re: [Bluez-users] rfcomm device names Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net 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 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