All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] scooped by pocketpc (a2dp)
Date: Sun, 16 Jan 2005 00:44:46 -0700	[thread overview]
Message-ID: <41EA1B6E.3070303@xmission.com> (raw)
In-Reply-To: <41E93B4F.1010600@dark-reality.de>

Lars,

> all programs that use openh323/pwlib (latter for hardware abstraction)
> use alsalib, because pwlib can be compiled against alsalib or oss or both.

hmm. i see a menu for alsa devices but our userspace a2dp device 
(currently stubbed out, but not implemented) doesn't show up. i set it 
up as documented in btsco/bt/BUILD

> That leads to - at least - gnomemeeting and openphone supporting alsa
> directly :)

that looks like a good option, esp when gm supports sip

> I'm not that interested because my headset only supports the mono
> headset profile... ;)

a2dp does not address using a microphone, so if you use a2dp, you have 
to choose a different device for audio in.

> writing the a2dp alsa driver should be similar to the btsco alsa part,
> maybe we can build one thing for both purposes, or at least keep
> structures similar so that both projects can support each other best!

well i want to try putting a2dp in a userspace driver since that might 
be the best way to go. (that's an issue that may not be totally worked 
out but i think we decided that it looks attractive enough to at least 
try writing alsa-lib drivers)

if it works well, we might rewrite the sco driver to be in userspace.

brad


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-16  7:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 15:28 [Bluez-devel] scooped by pocketpc (a2dp) Brad Midgley
2005-01-15 15:48 ` Lars Grunewaldt
2005-01-16  7:44   ` Brad Midgley [this message]
2005-01-24  7:35     ` Brad Midgley
2005-01-24 12:28       ` Marcel Holtmann
2005-01-24 12:32     ` Marcel Holtmann
2005-01-15 16:35 ` [Bluez-devel] " Paul Ionescu
2005-01-15 17:26   ` Lars Grunewaldt
2005-01-15 17:27     ` [Bluez-devel] " Paul Ionescu
2005-01-16  0:29   ` [Bluez-devel] " Peter Robinson
2005-01-16  0:41     ` Lars Grunewaldt

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=41EA1B6E.3070303@xmission.com \
    --to=bmidgley@xmission.com \
    --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 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.