linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Frey <mfrey@pepper.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HIDP backport for 2.4
Date: Tue, 27 Jul 2004 17:01:56 +0200	[thread overview]
Message-ID: <1090940516.4845.19.camel@pegasus> (raw)
In-Reply-To: <ABD9E52C-DFDC-11D8-BE76-00039390D626@pepper.com>

Hi Michael,

> > at the end of hidp_input_report() and see if this helps out for your
> > keyboard and mouse problems. What do "hidd -l" say after you have
> > connected the devices? What devices do you use?
> 
> root@(none):~# hidd -l
> 00:02:72:40:8A:97 HID Boot Device [0000:0000] connected
> 
> I am using a Keyboard with integrated mouse.  So I guess it is 
> technically one device.  The mouse is a track ball embedded in the 
> keyboard.  The keyboard is made by BlueLogic.

you should have said this earlier. Do you have a website for me? I need
more information about this device. Please use sdptest from libs2 CVS
repository to get the SDP record.

	./sdptest records 00:xx:xx:xx:xx:xx > sdp_record.txt

Send me that file. I also need the information from "hcitool inq" and
from "hcitool info" for that device.

Regards

Marcel




-------------------------------------------------------
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=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-07-27 15:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17  8:58 [Bluez-devel] HIDP backport for 2.4 Marcel Holtmann
2004-07-25 12:52 ` Marcel Holtmann
2004-07-25 16:57   ` Michael Frey
2004-07-26 17:24   ` Michael Frey
2004-07-26 17:47     ` Marcel Holtmann
2004-07-26 18:05       ` Michael Frey
2004-07-26 18:16         ` Marcel Holtmann
2004-07-26 18:49           ` Michael Frey
2004-07-26 21:01             ` Marcel Holtmann
2004-07-27  0:31               ` Michael Frey
2004-07-27  8:18                 ` Marcel Holtmann
2004-07-27 14:53                   ` Michael Frey
2004-07-27 15:01                     ` Marcel Holtmann [this message]
2004-07-27 15:14                       ` Michael Frey
2004-07-27 15:24                         ` Marcel Holtmann
     [not found]                           ` <86089F56-DFE5-11D8-BE76-00039390D626@pepper.com>
2004-08-01 15:57                             ` Marcel Holtmann
2004-08-11 21:19                               ` Michael Frey
2004-08-11 22:11                                 ` Marcel Holtmann
2004-08-13 17:27                                   ` Michael Frey
2004-08-13 17:53                                     ` Marcel Holtmann
2004-08-13 18:16                                       ` Michael Frey
2004-08-13 18:21                                         ` Marcel Holtmann

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=1090940516.4845.19.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mfrey@pepper.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;
as well as URLs for NNTP newsgroup(s).