public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] BlueZ and the ALSA support
Date: Sun, 21 Nov 2004 01:01:24 +0100	[thread overview]
Message-ID: <1100995285.7250.17.camel@pegasus> (raw)

Hi Folks,

I spent some hours to clean up the btsco CVS repository from the ALSA
Bluetooth project and also changed the code a little bit for easier use
by non technical people. It should now compile and work without the need
of reinstalling or changing any ALSA stuff. Here is a quick walktrough.

First the CVS repository must be checked out:

	cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa login
	cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa co btsco

After that is must be compiled:

	./bootstrap
	./configure
	make
	make install
	make maintainer-clean

And you need the kernel module:

	cd kernel
	make
	make install
	make clean

Now go ahead and use it like before.

As you may now realized the snd-bt-sco kernel driver is also inside this
repository and with a recent 2.6 kernel there are no problems with
compiling a kernel module outside the kernel source directory. However
if you haven't installed the running kernel by yourself you may need to
install the kernel source package from your distribution.

Every crappy header file is now removed and the needed IOCTL and the
HWDEP definition is added to the source directly in a compatible way.

The A2DP related programs are integrated into the Makefile and they are
also compiled, but for now they are not installed.

This should make the development a lot more easier :)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-11-21  0:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21  0:01 Marcel Holtmann [this message]
2004-11-21  2:10 ` [Bluez-devel] BlueZ and the ALSA support Lars Grunewaldt
2004-11-21  5:29 ` Brad Midgley
2004-11-21 17:14   ` Marcel Holtmann
2004-11-21 17:41     ` Lars Grunewaldt
2004-11-21 18:26       ` Marcel Holtmann
2004-11-21 20:13         ` Lars Grunewaldt
2004-11-21 20:39           ` Marcel Holtmann
2004-11-21 22:11             ` Lars Grunewaldt
2004-11-21 22:45               ` Marcel Holtmann
2004-11-21 22:59                 ` Lars Grunewaldt
2004-11-21 20:12     ` Brad Midgley
2004-11-21 20:25       ` Marcel Holtmann
2004-11-22  4:09         ` 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=1100995285.7250.17.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