From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] to build a bluetooth stack that can be embedded
Date: Thu, 1 Jul 2004 11:37:28 +0200 [thread overview]
Message-ID: <20040701093728.GA4505@gmx.net> (raw)
In-Reply-To: <20040701074257.94807.qmail@web20501.mail.yahoo.com>
On 0, Pranab Shenoy <pranab_shenoy@yahoo.com> wrote:
> We want to build a bluetooth stack that can be embedded in a smart
> device. We wanna know if its possible, if not why and if yes can we
> build from the existing stack.
Yes, Yes (if you follow the terms of the GPL)
nicholas
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-01 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 7:42 [Bluez-devel] to build a bluetooth stack that can be embedded Pranab Shenoy
2004-07-01 9:37 ` Nicholas A. Preyss [this message]
2004-07-01 14:03 ` 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=20040701093728.GA4505@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-devel@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