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: Sun, 04 Jul 2004 13:38:37 +0200 [thread overview]
Message-ID: <1088941116.4639.17.camel@pegasus> (raw)
In-Reply-To: <000a01c461a4$e79be160$0364a8c0@haruo>
Hi KeiHachi,
> > 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.
>
> I see.
> You, Marcel, are the one of the best engineer in the world,
> so I anticipate the time when AVDTP will be completed.
many thanks for these nice words.
When I first looked deeper at the details of AVDTP, my plan was to get a
working demo of the VDP at the Linux konferenca 2004 in Portoroz. Anyhow
my work on the HID support will take longer as expected and I hope that
I can finish the Bluetooth HID boot protocol support for the kernel
integration within the next two days.
Actually I thought that I will find some time to write the basics of the
AVDTP implementation in August, but I got invited to the O'Reilly Euro
Foo Camp. I will attend there and my plan is to present something very
nice, but right now I am not sure what it will be. Any proposals?
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
next prev parent reply other threads:[~2004-07-04 11:38 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
2004-07-04 8:57 ` KeiHachi
2004-07-04 11:38 ` Marcel Holtmann [this message]
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=1088941116.4639.17.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