Return-Path: Subject: RE: Questions on connecting BlueZ/SBC with Ekiga From: Marcel Holtmann To: hoene@uni-tuebingen.de Cc: linux-bluetooth@vger.kernel.org In-Reply-To: <017201c97980$32f7b880$98e72980$@hoene@gmx.net> References: <016701c97976$e75578d0$b6006a70$@de> <1232291106.5095.6.camel@californication> <017201c97980$32f7b880$98e72980$@hoene@gmx.net> Content-Type: text/plain Date: Sun, 18 Jan 2009 17:01:23 +0100 Message-Id: <1232294483.5095.34.camel@californication> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: 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