From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btsco: help with autoconf cleanup
Date: Fri, 12 Nov 2004 02:02:24 +0100 [thread overview]
Message-ID: <1100221344.12168.40.camel@pegasus> (raw)
In-Reply-To: <4193F258.3000003@xmission.com>
Hi Brad,
> >>what do you suggest for packing bits together in a portable way before
> >>putting them on the wire? is there some code somewhere that you can
> >>point to that works in userspace?
> >
> > actually I don't understand this question. Please explain to me what do
> > you wanna know.
>
> Yeah, I guess I just needed to read up more.
>
> I'm going to be assembling parts of frames like the media packet header.
> I started looking at l2cap_build_cmd to see how you do it in kernel
> space. I see htobs() is the equivalent of __cpu_to_le16 for 16-bit
> values and I see the __attribute__ ((packed)) directives that result in
> a packed struct that can be copied byte for byte into the buffer. I
> think I'm good to go.
>
> I'll probably be running the naming for some of the structures and
> members by you to see if they're ok to eventually go into the bluetooth
> headers.
please don't think about any kernel part at this time. It is not the
time to do any kernel work. The l2cap_build_cmd() is by the way the
wrong place to look at, because AVDTP is L2CAP payload.
If we get a program that can play pre-encoded SBC files on an A2DP
headphone then this is a good start. This program should be in userspace
first so we can learn through it. Remember that RFCOMM and HID were
implemented both in userspace first, before we did the kernel version.
After this is working, we need a subband codec implementation for the
ALSA library and then we should really start doing the kernel version of
the AVDTP. I don't wanna scare you, but it must look like the RFCOMM
one. It needs to do its own L2CAP connection setup.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-12 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 18:49 [Bluez-devel] btsco: help with autoconf cleanup Brad Midgley
2004-11-11 18:56 ` Marcel Holtmann
2004-11-11 21:04 ` Brad Midgley
2004-11-11 21:16 ` Marcel Holtmann
2004-11-11 23:14 ` Brad Midgley
2004-11-12 1:02 ` Marcel Holtmann [this message]
2004-11-15 17:31 ` David Woodhouse
2004-11-15 21:29 ` Brad Midgley
2004-11-16 6:39 ` Simon Vogl
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=1100221344.12168.40.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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