From: Brian Smith <brian.john.smith@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Gumstix / speed setting in Infineon PBA31308
Date: Mon, 20 Nov 2006 23:39:32 +0000 [thread overview]
Message-ID: <45623CB4.3070005@gmail.com> (raw)
In-Reply-To: <4562367E.90409@xmission.com>
Thanks again for the reply Brad. It is interesting for me to see how the
bluetooth hardware/software works. Thanks for your ongoing work on Linux
Bluetooth too.
Brad Midgley wrote:
> Brian
>
>
>> Do you know if the gumstix's NSSP is visible in userspace?
>>
>
> yes but you'll have to dig into the wiki to get the details and the
> results may be subpar even running as root with a negative nice value.
>
> I might have
>
>> a poke around in the kernel and try and get the audio stream working.
>> (there looks to be some docu in the kernel about it). I think
>> carwhisperer can get a SCO session open at least (I think). might play
>>
>
> You open an rfcomm connection to the headset and use some AT commands to
> do things. It's really quite simple (get the headset profile docs at
> bluetooth.com)
>
>
>> with that. Is your 'scoot' program available? Do you have any pointer so
>> more documentation on this stuff? If the audio is streamed direct to the
>>
>
> I won't write scoot after all... we're putting things together in a more
> general way.
>
>
>> CPU once sco is opened, why is it necessary for the hci connection to
>> run at 912k ? Is there a choice of whether to take the audio from hci or
>> direct from pcm then?
>>
>
> it's not necessary for sco. 921k would be nice for stereo audio.
>
> on csr adapters it's well known how to kick them back and forth between
> pcm and hci for sco but I don't know about this adapter.
>
> Brad
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-20 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 20:37 [Bluez-devel] Hiddev support Olivier Crête
2006-11-18 21:18 ` Douglas Ward
2006-11-20 8:30 ` Marcel Holtmann
2006-11-20 18:40 ` [Bluez-devel] Gumstix / speed setting in Infineon PBA31308 Brian Smith
2006-11-20 19:14 ` Brad Midgley
2006-11-20 21:43 ` Brian Smith
2006-11-20 23:13 ` Brad Midgley
2006-11-20 23:39 ` Brian Smith [this message]
2006-11-20 14:58 ` [Bluez-devel] Hiddev support Olivier Crête
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=45623CB4.3070005@gmail.com \
--to=brian.john.smith@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