From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A few questions about bluetooth-alsa project
Date: Mon, 2 Jul 2007 19:58:32 -0600 [thread overview]
Message-ID: <d89ddf300707021858u2e5e8f80k35794595254736f6@mail.gmail.com> (raw)
In-Reply-To: <46896137.90202@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1256 bytes --]
hey
So first up, I have built sample spec files that generate rpm files out
> of sbc and plugz. In case you are interested then I can share them with
> you all.
sure... I could put them in contrib/
Now, I have installed both plugz and sbc. I am trying to use sco for
> doing the two-way communication. I have copied over the
> plugz/alsa-plugins/asound.conf (as ~/.asoundrc) and changed the BT
> address to my headset's.
>
> I ran the headset daemon and I noticed that my gnome-volume applet looks
> different and shows a new control called PCM-2. But beyond this I am
> unable to do much.
most apps don't know about the plugin and you have to manually type in
"headset" for the alsa device. if the app doesn't let you type in the name,
you could make it the default device or hand-edit the config file.
I also noticed that the website states that I need kernel patches. Is
> this still true for kernels > 2.6.21 ??
I have not seen the flowcontrol patch land upstream.
I would really appreciate it if people could help me out with figuring
> out this headset integration.
you know this is a sort of testbed for this stuff. Marcel is allowing the
parts of the design that aren't broken to be rewritten into the bluez utils
audio service.
brad
[-- Attachment #1.2: Type: text/html, Size: 1974 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-03 1:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 20:33 [Bluez-devel] A few questions about bluetooth-alsa project Rogue
2007-07-03 1:58 ` Brad Midgley [this message]
2007-07-03 3:31 ` Marcel Holtmann
2007-07-03 15:55 ` Rogue
2007-07-03 16:40 ` Frederic Dalleau
2007-07-03 16:56 ` Frederic Dalleau
2007-07-11 20:14 ` Rogue
2007-07-03 18:14 ` 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=d89ddf300707021858u2e5e8f80k35794595254736f6@mail.gmail.com \
--to=bmidgley@gmail.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