public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: hoene@uni-tuebingen.de
Cc: linux-bluetooth@vger.kernel.org
Subject: RE: Questions on connecting BlueZ/SBC with Ekiga
Date: Sun, 18 Jan 2009 17:01:23 +0100	[thread overview]
Message-ID: <1232294483.5095.34.camel@californication> (raw)
In-Reply-To: <017201c97980$32f7b880$98e72980$@hoene@gmx.net>

Hi Christian,

> > > Due to legal reason we must use the BlueZ and are not allowed to include
> SBC
> > > into Ekiga.
> > 
> > What kind of legal reasons are you talking about here. The SBC
> > implementation is released under LGPL. Worst case issue here is that you
> > actually build an independent library out of it and just link it
> > dynamically. We were planning to do so anyway, but currently that is not
> > really sufficient for us. It would just create a maintenance overhead.
> 
> The SBC is covered by patents owned by Frans and Philips. Philips has made a
> legal agreement with Bluetooth SIG allowing SBC to be used in any Bluetooth
> device. Any other usages require permission from Philips.
> 
> Last year, a Philips' lawyer called me asking me to license SBC if it is
> added to Ekiga. I told them that I do not have money and asked finding
> another solution. However, until now Philips did not made a decision on how
> to process on this issues. I am awaiting it. Luckily, I am not yet sued ;-)

good to know since I was under the impression that SBC is royalty free
in all cases and not only Bluetooth. You might wanna check if it says
Bluetooth device or Bluetooth usage. Do they really bind it to devices
or to the transport?

Regards

Marcel



  reply	other threads:[~2009-01-18 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:12 Questions on connecting BlueZ/SBC with Ekiga Christian Hoene
2009-01-18 15:05 ` Marcel Holtmann
2009-01-18 15:19   ` Christian Hoene
2009-01-18 16:01     ` Marcel Holtmann [this message]
2009-01-19  1:35       ` Brad Midgley
2009-01-19  5:17         ` Christian Hoene

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=1232294483.5095.34.camel@californication \
    --to=marcel@holtmann.org \
    --cc=hoene@uni-tuebingen.de \
    --cc=linux-bluetooth@vger.kernel.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