From: Paul Webster <pjwebster@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Documentation
Date: Wed, 21 Sep 2005 09:38:19 +1000 [thread overview]
Message-ID: <dc98d8d9050920163852b27348@mail.gmail.com> (raw)
In-Reply-To: <dc98d8d905091417046437c4e7@mail.gmail.com>
Grrr. Delay on the documentation thing. spent the weekend wondering
why I had no love from my bluetooth module with the fresh kernel I'd
compiled. Left it, slept, did other stuff and looked again last night
to find "< > HCI USB driver". Fixed it and was back to getting my
BD_ADDR 00:00:00:00:00:00:00
This weekend......
On 9/15/05, Paul Webster <pjwebster@gmail.com> wrote:
> > The problem is that we all simply lack the time to fill all these gaps.=
And
> > perhaps Marcel still hopes that someone else will help out with writing=
good
> > user documentation. It's certainly his job to document command line
> > parameters, but writing and maintaining a good official introduction an=
d
> > HOWTOs for Bluetooth/BlueZ is a lot of work and it can be done by someo=
ne who
> > is not a programmer. I would go as far as saying that this kind of
> > documentation *should not* be written but only checked by the developer=
s.
> > Maybe an official bluez wiki would be the most efficient way to make pe=
ople
> > contribute documentation.
>
> I'm planning to do a bluez install on a laptop and desktop machine
> this weekend. Since both run LFS, it will be a fairly involved
> "bootscripts and all" install. I was planning on writing a LFS hint
> for the process, but if there was a bluez-wiki available, I'd gladly
> contribute my experiences.
>
> Paul W
>
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-09-20 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:27 [Bluez-users] Documentation Reinier Coetzer
2005-09-14 13:18 ` Marcel Holtmann
2005-09-14 13:44 ` Jon Kristian Nilsen
2005-09-14 22:02 ` Michael.S.G.
2005-09-14 23:18 ` Fred Schaettgen
2005-09-15 0:04 ` Paul Webster
2005-09-20 23:38 ` Paul Webster [this message]
2005-09-16 10:15 ` Stefan Behlert
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 9:23 Yannick Djoumbou Feunang
2004-03-26 9:22 Yannick Djoumbou Feunang
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=dc98d8d9050920163852b27348@mail.gmail.com \
--to=pjwebster@gmail.com \
--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.