From: Marcel Holtmann <marcel@holtmann.org>
To: Jean-Jacques BRUCKER <jean-jacques.brucker@sagem.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Réf. : Re: Réf. : Re: bluez : new bluetooth keyboard supported by hidd.
Date: Mon, 18 Sep 2006 10:04:32 +0200 [thread overview]
Message-ID: <1158566672.5645.11.camel@localhost> (raw)
In-Reply-To: <OF94D063E5.A6EB9011-ONC12571ED.0029C0F3-C12571ED.002ABA9E@sagem.com>
Hi Jean-Jacques,
> About the left space : it work but I have assigned it to Alt key. At
> the end we need a special kmap file to be able to use all features of
> this keybord, ( mine is an azerty keyboard), in this keymap file (or
> using xmodmap with X) we could reassign left space button to space
> event and Alt gr button to Alt and Alt gr event !
>
> I have assigned this button to Alt because I missed him (to switch
> between console for exemple), And to not loose a special keypress on
> the keyboard. (it already have a few keys... only 63 !).
the actual keyboard layout maybe needs a re-thinking. I leave this to
actual users of it.
> At the end my patch suggested an architecture to manage different
> peripherals. The code in is actual state will become a big mess if the
> number of differents peripheral to manage increase.
No it wasn't an architecture. It still was a hack. The decoding routine
for the keyboard was still named epox_decode(). A clean architecture
would have used a callback table or something similar. You can't design
an architecture if you don't have enough facts about the devices you are
trying to cover. Everything that is based on the Serial Port Profile and
which uses a proprietary protocol on top of RFCOMM is a problem and all
of them are basically unique.
I prefer the less intrusive approach and this was to use the class of
device and/or service name for detecting the (at the moment) two
different devices. I would pick the OUI part of the BD_ADDR only if I
have no other choice and trusting the remote name is also not a good
idea, because some input devices allow to change it.
And besides the Laserkey keyboard, I don't expect any other kind of
Bluetooth input device. The HID is a standard and if you buy a CSR chip,
you basically get the HID support for free. They did all the work for
running HID on the chip.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-09-18 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 7:46 Réf. : Re: Réf. : Re: bluez : new bluetooth keyboard supported by hidd Jean-Jacques BRUCKER
2006-09-18 8:04 ` Marcel Holtmann [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=1158566672.5645.11.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jean-jacques.brucker@sagem.com \
/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