From: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
To: Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>
Cc: David Herrmann
<dh.herrmann-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
chen.ganir-l0cyMroinI0@public.gmane.org,
claudio.takahasi-430g2QfJUUCGglJvpFV4uA@public.gmane.org,
jprvita-430g2QfJUUCGglJvpFV4uA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Vijaykumar.Dadmode-kQvG35nSl+M@public.gmane.org
Subject: Re: [RFC 0/1] User-space I/O driver for HID subsystem (Bluetooth-LE HIDP)
Date: Fri, 16 Mar 2012 09:03:29 -0700 [thread overview]
Message-ID: <1331913809.14217.155.camel@aeonflux> (raw)
In-Reply-To: <alpine.LNX.2.00.1203161556540.18356-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
Hi Jiri,
> > I have hacked together a small driver which allows user-space I/O drivers to
> > provide HID devices. This is needed for Bluetooth-Low-Energy HID devices as the
> > Bluetooth-LE protocol is parsed in user-space.
>
> David,
>
> thanks for your effort.
>
> I haven't read the full discussion you have CCed me on yesterday, but I
> have one substantial question to start with -- is there a simple
> explanation in a few sentences why Bluetooth-LE can't be added as a
> in-kernel transport layer?
>
> Answering that is, I believe, something that should start the whole
> discussion.
that has been discussed. My point is that the Bluetooth SIG made a
mistake with their specification here. And my original words were much
harsher ;)
Let me make an analogy. It is like HID over XML. You don't want that in
the kernel.
Regards
Marcel
next prev parent reply other threads:[~2012-03-16 16:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 14:53 [RFC 0/1] User-space I/O driver for HID subsystem (Bluetooth-LE HIDP) David Herrmann
2012-03-16 14:53 ` [RFC 1/1] HID: User-space I/O driver support for HID subsystem David Herrmann
[not found] ` <1331909617-22106-2-git-send-email-dh.herrmann-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-03-16 16:00 ` Marcel Holtmann
2012-03-16 18:51 ` David Herrmann
2012-03-16 20:51 ` Marcel Holtmann
2012-03-16 17:00 ` Andre Guedes
2012-03-16 17:15 ` Marcel Holtmann
2012-03-16 19:01 ` David Herrmann
2012-03-16 20:45 ` Marcel Holtmann
2012-03-16 23:38 ` Vinicius Costa Gomes
2012-03-26 17:38 ` David Herrmann
[not found] ` <1331909617-22106-1-git-send-email-dh.herrmann-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-03-16 14:58 ` [RFC 0/1] User-space I/O driver for HID subsystem (Bluetooth-LE HIDP) Jiri Kosina
[not found] ` <alpine.LNX.2.00.1203161556540.18356-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2012-03-16 16:03 ` Marcel Holtmann [this message]
2012-03-16 16:04 ` Anderson Lizardo
[not found] ` <CAJdJm_NHvdHNUsYh1tOkXEd9u5cGLszDCsXTVrwG=TjRxbNFuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-16 17:28 ` Joao Paulo Rechi Vita
2012-03-16 17:50 ` Joao Paulo Rechi Vita
2012-03-16 17:57 ` Marcel Holtmann
2012-03-16 18:09 ` Dmitry Torokhov
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=1331913809.14217.155.camel@aeonflux \
--to=marcel-kz+m5ild9qbg9huczpvpmw@public.gmane.org \
--cc=Vijaykumar.Dadmode-kQvG35nSl+M@public.gmane.org \
--cc=chen.ganir-l0cyMroinI0@public.gmane.org \
--cc=claudio.takahasi-430g2QfJUUCGglJvpFV4uA@public.gmane.org \
--cc=dh.herrmann-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
--cc=jprvita-430g2QfJUUCGglJvpFV4uA@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).