From: Douglas Russell <puggy@gentoo.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] MX900 page updated
Date: Fri, 25 Jun 2004 09:41:15 +0000 [thread overview]
Message-ID: <200406250941.15538.puggy@gentoo.org> (raw)
In-Reply-To: <1088107922.4296.135.camel@pegasus>
I know this has been covered above but I just thought I'd add a little more
info. Gentoo has got 2.7 libs and utils, but the dependancy system doesn't
work quite as well as necessary to take care of seemless rolling in of one
package to another, so anyone upgrading should then make sure bluez-sdp and
bluez-pan are unmerged before they upgrade. I'm working on making things like
kdebluetooth compile with 2.7 libs at the moment as currently they fail as
sdp are no longer independent libs. Should be ready soon. Also, I made a
howto for gentoo, which is largely based on your excellent work Charles but
updated for 2.7 (hidd) and customized.
http://dev.gentoo.org/~puggy/btmouse-howto/btmousehowto.html
Puggy
On Thursday 24 June 2004 20:12, Marcel Holtmann wrote:
> Hi Charles,
>
> > now that gentoo has a 2.6.7 kernel, I have tried Marcel's mh patch with
> > success, and I have updated my page about my setup :
>
> aren't there any Gentoo packages for bluez-libs and bluez-utils?
>
> > I'm not sure wheter I still need the uinput module since I switched to
> > hidd. I remember Marcel saying uinput is not needed with hidd. So who
> > sends events to /dev/input/mice ? hidd directly ?
>
> You don't need uinput anymore. The HIDP Module will do this all by
> itself. On my presentation at LinuxTag tomorrow I am going to show how
> this all works. I created some nice new graphics ;)
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-06-25 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 18:53 [Bluez-users] MX900 page updated Charles Bueche
2004-06-24 20:12 ` Marcel Holtmann
2004-06-25 7:28 ` Charles Bueche
2004-06-25 9:41 ` Douglas Russell [this message]
2004-06-25 12:39 ` Charles Bueche
2004-06-24 22:26 ` Bc. Michal Semler
2004-06-25 7:33 ` Charles Bueche
2004-06-25 8:07 ` karthik bala guru
2004-06-25 8:39 ` Charles Bueche
2004-06-25 9:53 ` karthik bala guru
2004-06-25 11:20 ` Charles Bueche
2004-06-25 11:39 ` karthik bala guru
2004-07-01 10:55 ` [Bluez-users] XHTML Parser and Generator Tools karthik bala guru
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=200406250941.15538.puggy@gentoo.org \
--to=puggy@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox