From: Charles Bueche <charles@bueche.ch>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Olivier Bornet <Olivier.Bornet@smartdata.ch>,
BlueZ Developers List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Sun, 14 Dec 2003 21:01:24 +0100 [thread overview]
Message-ID: <1071432083.6305.24.camel@bluez.bueche.ch> (raw)
In-Reply-To: <1071411737.4356.56.camel@pegasus>
Hi,
On Sun, 2003-12-14 at 15:22, Marcel Holtmann wrote:
> Hi Charles,
>
> > Now, my mouse isn't jumpy at all anymore. The only glitch left is that I
> > have to press its "connect" button just after starting bthid if I want a
> > link. Is there a way to get this automated ?
>
> this shouldn't be needed, because the mouse reconnects if you start
> moving it. The only thing you need is a HID server process on your host.
I have to test more. What is your command line for this ? I use
/data/util/bthid-0.8-2.6/bthid -m -d -p 600 00:07:61:08:7E:2E
> > I don't like to criticize about missing docs, because I have the same
> > problem at my main contract as Solaris admin (too many things to do to
> > write proper docs). However, bluez suffer a bit from that problem. They
> > are loads of small HOWTOs, but I miss a sort of white paper to explain
> > bluetooth in general. Any pointer is welcome.
>
> If you understand german you are in the lucky position that I have
> written some articles for german magazines and most of them are also
> available online.
I can read it, I will look at your articles, thx for the hint. I have
already seen a nice presentation which helped to understand the
bluetooth layers. A long time ago, I developped low-level code in Z80
assembler and C for embedded systems, so I'm not completely lost :-)
> The missing of a general white paper is a good point. I have thought so
> many times about writing the one and only introduction into Linux and
> Bluetooth, but always the same things stopped me from doing this. The
> first is that no company pays me for working on BlueZ and so we come to
> the second, that my time is very limited.
You do a very good job in that limited time, given all these beginners
like me asking basic stuff on mailing lists :-)
Charles
--
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer
next prev parent reply other threads:[~2003-12-14 20:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38 ` Peter Klausler
2003-12-02 15:55 ` Edd Dumbill
2003-12-02 16:01 ` Edd Dumbill
2003-12-03 20:18 ` Charles Bueche
2003-12-03 20:35 ` Marcel Holtmann
2003-12-04 8:53 ` Olivier Bornet
2003-12-04 13:52 ` Marcel Holtmann
2003-12-04 13:57 ` Olivier Bornet
2003-12-04 14:10 ` Marcel Holtmann
2003-12-04 16:35 ` Olivier Bornet
2003-12-04 17:03 ` Marcel Holtmann
2003-12-09 20:31 ` Charles Bueche
2003-12-09 22:42 ` Olivier Bornet
2003-12-10 8:12 ` Charles Bueche
2003-12-10 8:30 ` Olivier Bornet
2003-12-13 15:56 ` Charles Bueche
2003-12-13 16:39 ` Marcel Holtmann
2003-12-13 18:51 ` Charles Bueche
2003-12-13 19:04 ` Marcel Holtmann
2003-12-14 13:55 ` Charles Bueche
2003-12-14 14:22 ` Marcel Holtmann
2003-12-14 20:01 ` Charles Bueche [this message]
2003-12-14 20:09 ` Marcel Holtmann
2003-12-10 1:41 ` Marcel Holtmann
2003-12-02 17:39 ` Marcel Holtmann
2003-12-02 17:42 ` Peter Klausler
2003-12-02 17:56 ` Marcel Holtmann
2003-12-03 10:10 ` Stephen Crane
2003-12-03 13:06 ` 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=1071432083.6305.24.camel@bluez.bueche.ch \
--to=charles@bueche.ch \
--cc=Olivier.Bornet@smartdata.ch \
--cc=bluez-devel@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