From: Marcel Holtmann <marcel@holtmann.org>
To: Keith Pemberton <kbpember@cox.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] module writing entry points...
Date: Fri, 02 Apr 2004 01:28:32 +0200 [thread overview]
Message-ID: <1080862112.2774.21.camel@pegasus> (raw)
In-Reply-To: <1080859594.5650.3.camel@linuxcomp.gatep5.net>
Hi Keith,
> Could someone tell me where to look in the bluez code for the entry
> points to writing a module if there are any? I'm just trying to write a
> minidriver just because but I'm having trouble finding where to start.
> Any help to get me back on track is much appreciated. I have been doing
> a lot of reading of specifications and such but things are just not
> quite gelling yet... Thanks!
tell us what kind of driver are you planning to write. What protocol or
profile support do you have in mind?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-04-01 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 22:46 [Bluez-devel] module writing entry points Keith Pemberton
2004-04-01 23:28 ` 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=1080862112.2774.21.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kbpember@cox.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.