public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] /usr/include/bluetooth/bnep.h
Date: Fri, 07 May 2004 10:28:14 +0200	[thread overview]
Message-ID: <1083918493.4420.109.camel@pegasus> (raw)
In-Reply-To: <200405070028.06843.cijoml@volny.cz>

Hi Michal,

> can you write more info about this module? What will it take care of?
> Only Human Interface Device Protocol? And hidd will serve events to it to 
> decode them instead of doing it by hidd?

the hidp kernel module is designed to implement only HIDP. It works
mostly the same way as BNEP and CMTP, but it needs a lot more
information from the SDP database of the remote device. Thus the
structures had to evolve over time and now I think I found the perfect
match on what the kernel has to know and what not. You can look at the
hidp_connadd_req struct in libs/include/hidp.h and see what I mean. The
problem of hidd at the moment is that it only fills in the sockets and
the report descriptor data. Once hidd had given the connection to the
hidp module everything else is done inside the kernel. This means that
you can even stop and restart hidd without losing your input device.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-05-07  8:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 15:32 [Bluez-users] /usr/include/bluetooth/bnep.h Edd Dumbill
2004-05-06 16:50 ` Marcel Holtmann
2004-05-06 16:57   ` Edd Dumbill
2004-05-07  8:38     ` Marcel Holtmann
2004-05-06 19:27   ` Michal Semler
2004-05-06 21:01     ` Marcel Holtmann
2004-05-06 21:53       ` Michal Semler
2004-05-07  8:20         ` Marcel Holtmann
2004-05-06 22:28       ` Michal Semler
2004-05-07  8:28         ` Marcel Holtmann [this message]
2004-05-07  9:53           ` Michal Semler
2004-05-07 16:14             ` Marcel Holtmann
2004-05-07 21:51               ` Michal Semler
2004-05-07 22:08                 ` Marcel Holtmann
2004-05-07 22:23                   ` Michal Semler
2004-05-07 22:56                     ` 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=1083918493.4420.109.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    /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