public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] 2.6.10 multimedia keys
Date: Mon, 3 Jan 2005 23:50:19 +0100	[thread overview]
Message-ID: <200501032350.19104.cijoml@volny.cz> (raw)
In-Reply-To: <1104790659.8894.81.camel@pegasus>

I asked Vojtech from suse...hope he will help

M.

Dne po 3. ledna 2005 23:17 Marcel Holtmann napsal(a):
> Hi Michal,
>
> > > > Marcel pls write support for user space configuring hotkey keycodes
> > > > too, coz I have multimedia keys on my laptop and those keys returns
> > > > other key press keycodes than keys on MS desktop........than I can't
> > > > configure it well, coz 254 returns IE key on notebook and email key
> > > > on MS desktop and so on...
> > >
> > > some parts of this are not my job. The input guys must work on it. The
> > > Bluetooth HIDP is only a transport layer between L2CAP and the generic
> > > HID parser and/or the input subsystem.
> >
> > This is work for our driver I thought...We pass 254 to subsystem which
> > than work with it...so we should send for example 117 instead of 254
> > originally reported.
>
> what you talk about is a quirk and since the current USB HID parser
> already contains enough of them, I try to avoid as much of them as
> possible. In general the value is correct, but our problem is that we
> have to deal with PS/2 as protocol at the level of the input subsystem.
> However don't bother me about that quirk. Send in a patch or get the
> input guys to redesign parts of their subsystem.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-03 22:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 20:38 [Bluez-users] 2.6.10 multimedia keys Walt
2005-01-02 20:40 ` Michal Semler
2005-01-02 20:48   ` Marcel Holtmann
2005-01-02 21:47     ` Michal Semler
2005-01-03 13:54       ` Michael Firsching
2005-01-03 21:53         ` Michal Semler
2005-01-02 20:47 ` Marcel Holtmann
2005-01-03 20:44   ` Michal Semler
2005-01-03 20:56     ` Marcel Holtmann
2005-01-03 21:52       ` Michal Semler
2005-01-03 22:17         ` Marcel Holtmann
2005-01-03 22:50           ` Michal Semler [this message]
2005-01-03 23:01             ` Marcel Holtmann
2005-01-03 23:20               ` Michal Semler

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=200501032350.19104.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --cc=bluez-users@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