All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Terence Rudkin <trexx@pobox.com>
Cc: Olivier Bornet <Olivier.Bornet@puck.ch>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Logitech Bluetooth  Mx900+keyboard support.
Date: Wed, 28 Jan 2004 09:00:33 +0100	[thread overview]
Message-ID: <1075276833.12766.56.camel@pegasus> (raw)
In-Reply-To: <1075234547.3064.13.camel@localhost.localdomain>

Hi Terence,

> I finally had a chance to patch kernel and try hid2hci  with this patch
> kernel.   I still got success. but hcitool dev never reported any
> devices.   I looked at the code in hid2hci, my diff is below. 
> 
> I first made the change at 204.  And found that the /dev/usb/hid was not
> opening.  Finding me /dev to be /dev/usb I changed line 79 to match my
> file structure.   

be more specific and make a unified diff.

> Now I get
> hciconfig
> hci0:   Type: USB
>         BD Address: 00:07:61:07:ED:A9 ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:131 acl:0 sco:0 events:14 errors:0
>         TX bytes:32 acl:0 sco:0 commands:13 errors:0
> 
> But not input from mouse and keyboard.

The dongle is now in HCI mode and this means that you have to handle the
HID protocol by yourself. Run the bthid daemon.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-01-28  8:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-18 20:20 [Bluez-users] Logitech Bluetooth Mx900+keyboard support Terence Rudkin
2004-01-18 20:44 ` Marcel Holtmann
2004-01-18 21:30   ` Michal Semler (volny.cz)
2004-01-18 22:11     ` Marcel Holtmann
2004-01-18 23:01   ` Terence Rudkin
2004-01-19  2:54   ` Terence Rudkin
2004-01-19 12:22     ` Marcel Holtmann
2004-01-20  3:09       ` Terence Rudkin
2004-01-20  8:12         ` Olivier Bornet
2004-01-20 11:25           ` Marcel Holtmann
2004-01-27 20:15             ` Terence Rudkin
2004-01-28  8:00               ` Marcel Holtmann [this message]
2004-01-28 16:18                 ` Terence Rudkin
2004-01-28 16:32                   ` Marcel Holtmann
2004-01-28 18:46                     ` Terence Rudkin
2004-01-28 19:16                       ` Marcel Holtmann
2004-01-28 21:44                         ` Terence Rudkin
2004-01-29  5:39                           ` Marcel Holtmann
2004-01-29  3:29                     ` Terence Rudkin
2004-01-29 13:12                       ` T3 Was " Gareth Reakes
2004-01-31 19:34                         ` Terence Rudkin
2004-01-29 19:41                       ` Charles Bueche
2004-01-29 19:52                         ` Marcel Holtmann
2004-01-20 11:27         ` 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=1075276833.12766.56.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Olivier.Bornet@puck.ch \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=trexx@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.