From: Marcel Holtmann <marcel@holtmann.org>
To: Jonathan Sass <jsass@magnifeye.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Microsoft Mouse
Date: Wed, 03 Nov 2004 11:07:02 +0100 [thread overview]
Message-ID: <1099476422.7125.91.camel@pegasus> (raw)
In-Reply-To: <C21DDF6B-2D7B-11D9-ADC1-0005027BA2B7@magnifeye.com>
Hi Jonathan,
you know that there is a "Reply to All" button in your mail client ;)
> Thank you your info and a mouse howto from
> http://dev.gentoo.org/~puggy/btmouse-howto/btmousehowto.html I now have
> my keyboard and mouse running. It was quite easy.
It is meant to be quite easy with any newer Linux distribution, where
the BlueZ packages and the kernel are up to date.
> My next step is a custom bluetooth device, are there documents that
> show me where I can intercept the data from the device within the linux
> kernel and route it to a particular application? Where does the data
> from the bluetooth device "show up" in the kernel.
This is all about socket programming. There is no need to look inside
the kernel.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next parent reply other threads:[~2004-11-03 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C21DDF6B-2D7B-11D9-ADC1-0005027BA2B7@magnifeye.com>
2004-11-03 10:07 ` Marcel Holtmann [this message]
2004-11-02 21:50 [Bluez-users] Microsoft Mouse Jonathan Sass
2004-11-03 0:05 ` 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=1099476422.7125.91.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=jsass@magnifeye.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox