public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] starting btsco-in-libalsa
Date: Thu, 09 Dec 2004 02:28:43 -0700	[thread overview]
Message-ID: <41B81ACB.1080807@xmission.com> (raw)

Guys,

I put some junk in the btsco cvs:

alsa-lib.patch
bt/

if you apply alsa-lib.patch and put bt inside alsa-lib/src/pcm then the 
idea is that you can build a userspace alsa driver.

currently it doesn't even compile... it's just based on the jack plugin 
and not yet reworked for bluetooth.

anyway, this is my next project. it depends on a couple of things in 
other parts of the project:

  it would be nice if 'make install' inside sbc/ would install the sbc 
includes and library (static libs would be ok)

  the avdtp library is just a skeleton right now... should I just ignore 
it for now and hardcode what is currently in a2play?

brad


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-12-09  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09  9:28 Brad Midgley [this message]
2004-12-09 10:57 ` [Bluez-devel] starting btsco-in-libalsa Marcel Holtmann
2004-12-09 11:48   ` [Bluez-devel] " suche.org
2004-12-09 12:07     ` Marcel Holtmann
2004-12-09 12:49       ` [Bluez-devel] Re2: " suche.org
2004-12-09 13:10         ` [Bluez-devel] " Marcel Holtmann
2004-12-09 17:31     ` Brad Midgley

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=41B81ACB.1080807@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox