From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Stefan Seyfried <seife@suse.de>
Subject: Re: [Bluez-devel] [PATCH] Input Service - Support for hidd configuration
Date: Sat, 16 Jun 2007 09:50:17 +0200 [thread overview]
Message-ID: <1181980217.6846.78.camel@aeonflux.inter-touch.com> (raw)
In-Reply-To: <200706082336.00557.dgollub@suse.de>
Hi Daniel,
> attachted an input service patch which implements support for the hidd
> configuration. This is needed to have a smooth transition from hidd daemon to
> the new shiny input service ...
>
> ( ... and especially this is needed to be able to return from vacation back to
> the office - without getting blamed by Seife for not working bluetooth input
> devices ;P )
>
> The patch reads the entries of hidd and stores it with store_device_info()
> function. The hidd doesn't get modified - this means the transition happens
> on every start of the input service. store_device_info() avoids duplicate
> entries. So there is still the possibility to have a working bluetooth input
> device when falling back to hidd.
if I read this correctly, then a hidd entry would overwrite a input
entry. We can't let that happen.
Also the format of hidd and input is different, but you are using the
same function to parse it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-16 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 21:35 [Bluez-devel] [PATCH] Input Service - Support for hidd configuration Daniel Gollub
2007-06-09 2:53 ` Mo.Shahin
2007-06-16 7:50 ` Marcel Holtmann [this message]
2007-06-22 15:41 ` Daniel Gollub
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=1181980217.6846.78.camel@aeonflux.inter-touch.com \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=seife@suse.de \
/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