Linux bluetooth development
 help / color / mirror / Atom feed
From: "Franck Arnaud" <franck@nenie.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] hidp 2.4 backport
Date: 22 May 2004 14:05:39 GMT	[thread overview]
Message-ID: <45540213.2004.5.22.14.5.39.99703@mem.nenie.org> (raw)

Hello,

I have an epox (CSR) bluetooth mouse and I'm using kernel 2.4. I 
tried bthid 0.10, which worked fine initially but I could not make 
it handle reconnections (after a long enough timeout, clicking 
the mouse just after the disconnection message seems to 
reconnect OK). This looks like the problem described in the doc, 
although the solution (pinging the mouse to keep it awake) is 
not acceptable.

It would be a pain at this time to upgrade to 2.6 in my setup, so 
I backported the 2.6.6-mh1 hidp module to 2.4:

http://www.nenie.org/misc/bluetooth/bluez-hidp-backport-2.4-26.tar.gz

it may be broken as I don't know anything about kernel 
programming :-) but it seems to work fine, except it seems you 
need the -t timeout option on hidd, otherwise it fails like with 
bthid (I do not understand why).

It may not be worth applying to the official 2.4 patches as I 
guess most people can upgrade to 2.6 more easily than me.



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-05-22 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 14:05 Franck Arnaud [this message]
2004-05-25 12:04 ` [Bluez-devel] hidp 2.4 backport 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=45540213.2004.5.22.14.5.39.99703@mem.nenie.org \
    --to=franck@nenie.org \
    --cc=bluez-devel@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