public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Using BlueZ in commercial applications - Once	again.
Date: Fri, 06 Jul 2007 08:00:44 +0200	[thread overview]
Message-ID: <1183701644.6351.111.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <18a15270707050404y72f7d4e1i6473089816749123@mail.gmail.com>

Hi Ranulf,

>         > the socket-API being one form of such glue code
>         > (but because that requires a GPL'd header to actually
>         function, think of 
>         > AF_BLUETOOTH defined only in bluetooth/bluetooth.h, it's out
>         of the
>         > question) 
> 
> The number itself isn't covered by the GPL however. The constant name,
> I'm less sure about, but I see no reason why you couldn't define your
> own constant FAMILY_BLUETOOTH which happens to have the same value as
> a publically known magic value. 

contact a lawyer before making such statements. How do you learned about
that number. You read GPL code and this would make it derived work. Be
really careful. The licenses are in place for a reason. You wanna use
software from the community so you have to play with our rules. If you
don't want that, then you can always buy a Bluetooth stack from someone
else.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2007-07-06  6:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 15:19 [Bluez-devel] Using BlueZ in commercial applications - Once again Heiko Wundram|Beenic
2007-07-05  8:04 ` Marcel Holtmann
2007-07-05  9:08   ` Heiko Wundram (Beenic)
2007-07-05  9:20     ` Peter Wippich
2007-07-05  9:35       ` Heiko Wundram (Beenic)
2007-07-05 11:04         ` Ranulf Doswell
2007-07-05 12:14           ` Heiko Wundram (Beenic)
2007-07-06  6:00           ` Marcel Holtmann [this message]
2007-07-06 10:21             ` Ranulf Doswell
2007-07-06  6:09         ` Marcel Holtmann
2007-07-06  6:44           ` Heiko Wundram (Beenic)

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=1183701644.6351.111.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --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