Linux bluetooth development
 help / color / mirror / Atom feed
From: "Michal Semler (volny.cz)" <cijoml@volny.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bthid updated
Date: Mon, 10 Nov 2003 12:25:09 +0100	[thread overview]
Message-ID: <200311101225.09925.cijoml@volny.cz> (raw)
In-Reply-To: <1068109845.1288.153.camel@pegasus>

Dne =E8t 6. listopadu 2003 10:10 Marcel Holtmann napsal(a):
> Hi Peter,
>
> > I've updated my bthid daemon with some tweaks that
> > may or may not have been necessary to get the new
> > Apple Bluetooth keyboard to work, and a new "-p"
> > option that enables regular pinging after inactivity,
> > which appears to be the key to keeping the Microsoft
> > keyboard from going to sleep so hard that it needs
> > to be power-cycled.  Michal Semler suggested the
> > technique, and I wish that I had thought of it before
> > I broke the keyboard's battery compartment cover from
> > overuse.
>
> if you have some extra time, please send me the information from
> "hcitool inq" and "hcitool info" of the Apple devices. And the output
> from the libs2 CVS "sdptest records" could be very helpful, too.
>
> Let's talk a little bit about the freezing of the Microsoft devices,
> because I already solved this for my own HID implementation, but I
> forgot to share my knowledge. The mouse and the keyboard drop both L2CAP
> connections after 12 minutes of idle time and try to disconnect the ACL
> link after that, but on the Linux side we don't handle this correctly.

Maybe M$ handle it incorrectly on theit side :)

> It seems that closing the two L2CAP connections at the same time causes
> problems. The problem must be inside the kernel HCI or L2CAP layer, but
> on my latest review I found nothing wrong. So I used this pseudo code
>
> 	if (we_close_connection) {
> 		close(control_psm);
> 		sleep(1);
> 		close(interrupt_psm);
> 	} else {	/* HID device after 12 minutes idle */
> 		close(interrupt_psm);
> 		sleep(1);
> 		close(control_psm);
> 	}
>
> If you don't do it this way the ACL connection between the host and the
> HID device will not be terminated. In general this is not a problem, but
> it gets unusable and so you have to power-cycle.
>
> Keeping the HID device alive with some kind of pinging is not a good
> idea, because it consumes to much power ;)

=46or now I prefer working solution if non other and better is known...

>
> > The Microsoft and Apple offerings remain the only Bluetooth
> > keyboards of commercial availability known to me.  Has anyone
> > seen another?
>
> Logitech seems to have some devices on the market. Last time I tried the
> old Logitech Presenter I found that your SDP implementation can't get
> the HID descriptor out of this device. I don't have this device handy,
> so I can't reproduce the error.
>
> Have you ever looked at the "User level driver support for input"? It
> maybe can replace your fake driver and I also backported it to 2.4, but
> Marcelo didn't picked it up.
>
> Regards
>
> Marcel

Michal

  reply	other threads:[~2003-11-10 11:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06  1:45 [Bluez-users] bthid updated Peter Klausler
2003-11-06  9:02 ` Gareth Reakes
2003-11-06  9:10 ` Marcel Holtmann
2003-11-10 11:25   ` Michal Semler (volny.cz) [this message]
2003-11-10 11:52     ` Marcel Holtmann
2003-11-10 13:06 ` Olivier Bornet
2003-11-15 18:02 ` Edd Dumbill
2003-11-15 19:39   ` Marcel Holtmann
2003-11-15 21:59     ` Edd Dumbill
2003-11-15 22:50       ` Edd Dumbill
2003-11-15 22:57       ` Marcel Holtmann
2003-11-16 13:14         ` Florian Echtler
2003-11-16 13:22           ` 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=200311101225.09925.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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