From: "Bc. Michal Semler" <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] DiNovo Multimedia keys... again...
Date: Wed, 8 Sep 2004 09:32:34 +0200 [thread overview]
Message-ID: <200409080932.34030.cijoml@volny.cz> (raw)
In-Reply-To: <1094627466.5384.2.camel@notepaq>
Dne st 8. z=E1=F8=ED 2004 09:11 Marcel Holtmann napsal(a):
> Hi Rui,
>
> > I'm successfully using the Logitech DiNovo keyboard and mouse in both
> > Desktop and Laptop in bluetooth. However, the multimedia keys are not
> > recognized.
> > The procedure I followed to install the keyboard is the following:
> >
> > $ modprobe hidp
> > $ hidd --server
> > $ hid2hci
> >
> > done! it works.
> >
> > I can see that the keyboard events with hcidump when pressing the
> > multimedia hotkeys (in this case, volume up, volume down and mute):
> > HCIDump - HCI packet analyzer ver 1.10
> > device: hci0 snap_len: 1028 filter: 0xffffffff
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 14
> >
> > L2CAP(d): cid 0x0041 len 10 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 10
> >
> > L2CAP(d): cid 0x0041 len 6 [psm 0]
> >
> > > ACL data: handle 0x0029 flags 0x02 dlen 14
> >
> > L2CAP(d): cid 0x0041 len 10 [psm 0]
> >
> > But they don't show up in xev (this is the Return key press and release
> > event. Multimedia keys doesn't cause any event to occurr):
> > KeyPress event, serial 26, synthetic NO, window 0x3c00001,
> > root 0x5e, subw 0x0, time 103253160, (391,131), root:(1299,323),
> > state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
> > " XLookupString gives 1 bytes: "
> >
> > KeyRelease event, serial 26, synthetic NO, window 0x3c00001,
> > root 0x5e, subw 0x0, time 103253248, (391,131), root:(1299,323),
> > state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
> > " XLookupString gives 1 bytes: "
> >
> > Any clue?
>
> try the 2.6.8-mh1 kernel patch and see if they are mapped now.
Marcel did you find a way how to map those multimedia keys on MS BT keyboar=
d?
Michal
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-09-08 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 14:01 [Bluez-users] DiNovo Multimedia keys... again Rui Lopes
2004-09-08 7:11 ` Marcel Holtmann
2004-09-08 7:32 ` Bc. Michal Semler [this message]
2004-09-08 7:50 ` Marcel Holtmann
2004-09-08 8:09 ` Bc. 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=200409080932.34030.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