public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Valerio Valerio" <vdv100@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Listen a already open socket by the OS
Date: Fri, 13 Jun 2008 21:53:09 +0100	[thread overview]
Message-ID: <eba8281a0806131353m67d78395md62074bfa13bc9a9@mail.gmail.com> (raw)
In-Reply-To: <2d5a2c100806131229l79022c48w65489072f2e6ca36@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1740 bytes --]

Hi,

2008/6/13 Luiz Augusto von Dentz <luiz.dentz@gmail.com>:

> I supposed you are the OpenMoko student in charge of remote control.

Yap you are right :)

>
> You better join #bluez @ freenode to stay tunned about bluetooth and
> BlueZ, now about HID channels, we already are listen them in hcid, so
> you don't need to worry if you are running hcid for the server part.
> The tricky part is the client side, when the device act as a
> mouse/keyboard, Im afraid there is no library to assist you with HID
> protocol and I think you cannot connect in such psm without being root
> either. If Im correct about those points then I think it is better to
> code the missing HID support inside bluez-utils.


Yes the psm 17 (control channel) require root, because is one of the
reserved psm,  my previous problem is that I had the hidd server running in
the client side, if I disable it I can listen the sockets that I need
without problems.

If one of the BlueZ developer with knowledge of HID, give some orientation
for a while, maybe I can do some code that can be useful for other
developers and integrated in the bluez-utils.

Best regards,

-- 
Valério Valério

http://www.valeriovalerio.org


>
> --
> Luiz Augusto von Dentz
> Engenheiro de Computação
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #1.2: Type: text/html, Size: 2655 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-06-13 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 22:02 [Bluez-devel] Listen a already open socket by the OS Valerio Valerio
2008-06-13 19:29 ` Luiz Augusto von Dentz
2008-06-13 20:53   ` Valerio Valerio [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=eba8281a0806131353m67d78395md62074bfa13bc9a9@mail.gmail.com \
    --to=vdv100@gmail.com \
    --cc=bluez-devel@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