All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: "'Brad Midgley'" <bmidgley@gmail.com>,
	"'Marcel Holtmann'" <marcel@holtmann.org>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: RE: Questions on connecting BlueZ/SBC with Ekiga
Date: Mon, 19 Jan 2009 06:17:14 +0100	[thread overview]
Message-ID: <019c01c979f5$340040b0$9c00c210$@de> (raw)
In-Reply-To: <d89ddf300901181735i5d516dc4r45fc83634fe1d7c7@mail.gmail.com>

Hello Brad,

> Can anyone comment on whether this is specific to the encoder/decoder?
> Is the patent an inevitable part of the codec or limited to a specific
> implementation?

It is part of the codec algorithm and thus part of any implementation.

> 
> > 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?
> 
> How is a computer with a qualified USB adapter different from any
> other qualified bluetooth device? Does the software have to be
> targeted for a specific portable computer as opposed to useful on any
> computer?

I am sorry to say what I do not have the contract between Philips and
Bluetooth SIG. Thus, only the legal department of Philips can answer your
question. I requested feedback from the legal department of Philips.
However, I am still awaiting an answer. I will inform you as soon as I get
it. 
The SBC issues does not seem to have a high priority because the amount of
money to make or loss is quite low.

Best regards,

 Christian

      reply	other threads:[~2009-01-19  5:17 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
2009-01-19  1:35       ` Brad Midgley
2009-01-19  5:17         ` Christian Hoene [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='019c01c979f5$340040b0$9c00c210$@de' \
    --to=hoene@uni-tuebingen.de \
    --cc=bmidgley@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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 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.