public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: KeiHachi <keihachi@swissinfo.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Questions about BlueZ in  commercial use
Date: Wed, 30 Jun 2004 20:11:35 +0200	[thread overview]
Message-ID: <1088619095.4540.126.camel@pegasus> (raw)
In-Reply-To: <000d01c45ebe$72d6e660$0264a8c0@haruo>

Hi KeiHachi,

> > The problem is that they use multiple L2CAP connections with the same
> > PSM for different protocols. This is totally stupid, because you can
> > only differ between them on the order of their creation. However the
> > basic mode looks very simple. Right now it looks like that I will
> > support AVDTP as a sequential packet socket.
> 
> Probably it can be realized as a socket.
> But some functionalities, like a SEP concept, should be considered in deeply.

I already did that and in the fact of SEP it is nothing different from a
PSM or RFCOMM channel. Actually because of this I thought that a socket
based implementation is the best. Along time I prefered to keep AVDTP in
userspace. However the only difficult part is the discover, because if
you don't know the SEP you must use it to find the available ones and
this includes a L2CAP connection. I must see how this gets integrated in
a nice way.

> > No problem for me, because I don't like talking about theoretical stuff.
> > I prefer to talk about facts. If you know what you want, we can talk
> > about what is possible and what not. And I can help you with not driving
> > into a dead end.
> 
> Thank you, availing of your kind offer, I have one more question.
> 
> I know the product that uses BlueZ in it, as I found it on the BlueZ site before.
> http://www.bluez.org/qualification.html
> 
> In that case, how did you or other guys help them to qualify?
> For example, did that company paid some fee, or donation?
> Were you or other guys under obligation to help them based on a contract?
> 
> Of course if you have the obligation to keep its secrets, it is OK to say nothing.

There is no secret about it. Parts of the communication can be found in
the mailing list archive. The rest was not in public, but actually only
by accident.

What we had done was to fix the L2CAP and RFCOMM protocol layers and
extend the test programs to pass the qualification tests.

There was no contract and they didn't paid us.

Regards

Marcel




-------------------------------------------------------
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

  reply	other threads:[~2004-06-30 18:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27  9:47 [Bluez-devel] Questions about BlueZ in commercial use KeiHachi
2004-06-27 12:52 ` Nicholas A. Preyss
2004-06-27 14:45   ` KeiHachi
2004-06-27 17:13     ` Nicholas A. Preyss
2004-06-28 16:30       ` KeiHachi
2004-06-28 17:22         ` Marcel Holtmann
2004-06-27 18:29     ` Marcel Holtmann
2004-06-28 16:33       ` KeiHachi
2004-06-28 17:45         ` Marcel Holtmann
2004-06-28 14:39   ` Ademar de Souza Reis Jr.
2004-06-28 14:48     ` Marcel Holtmann
2004-06-28 15:19       ` Ademar de Souza Reis Jr.
2004-06-28 15:38         ` Marcel Holtmann
2004-06-28 15:59           ` Stephen Crane
2004-06-28 17:06           ` Ademar de Souza Reis Jr.
2004-06-28 17:15             ` Marcel Holtmann
2004-06-27 18:09 ` Marcel Holtmann
2004-06-27 19:10   ` Nicholas A. Preyss
2004-06-27 19:09     ` Marcel Holtmann
2004-06-27 20:34       ` Nicholas A. Preyss
2004-06-27 20:49         ` Marcel Holtmann
2004-06-27 21:42           ` Nicholas A. Preyss
2004-06-28  7:37             ` Marcel Holtmann
2004-06-28 16:28   ` KeiHachi
2004-06-28 17:13     ` Marcel Holtmann
2004-06-29 17:08       ` KeiHachi
2004-06-29 17:41         ` Marcel Holtmann
2004-06-30 16:22           ` KeiHachi
2004-06-30 18:11             ` Marcel Holtmann [this message]
2004-07-04  8:57               ` KeiHachi
2004-07-04 11:38                 ` Marcel Holtmann
2004-07-04 13:19                   ` Peter Favrholdt
2004-07-04 13:47                     ` 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=1088619095.4540.126.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=keihachi@swissinfo.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