From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] General Debian bluez question
Date: Sat, 29 Jan 2005 02:31:32 +0100 [thread overview]
Message-ID: <1106962292.10580.10.camel@pegasus> (raw)
In-Reply-To: <1106956484.11673.213836256@webmail.messagingengine.com>
Hi Russell,
> I am hoping someone can answer a general Debian-bluez question.
>
> I have installed Debian sarge and upgraded to the sid kernel so I can
> apply the patch patch-2.6.10-mh2.gz.
>
> When installing sarge I also choose the bluez-utils package, but there
> is another package called kernel-patch-2.6-bluez. Should I also be
> patching the 2.6.10 kernel with this patch, as well as the "mh2" one?
I don't know what kernel-patch-2.6-bluez is, ask the maintainer. The
only official patch is the -mh patch.
> My Microsoft bluetooth mouse works fine without the debian patch - or at
> least it seems to! I'm just curious about whether I need both patches. I
> will continue to use the "mh2" patch do I can enjoy scroll-wheel
> support.
The -mh2 will give you report mode protocol support and this means the
scroll wheel should be useable.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-29 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 23:54 [Bluez-users] General Debian bluez question russellturner
2005-01-29 1:31 ` Marcel Holtmann [this message]
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=1106962292.10580.10.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.