From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco under FC3
Date: Thu, 06 Jan 2005 21:20:43 -0700 [thread overview]
Message-ID: <41DE0E1B.6000007@xmission.com> (raw)
In-Reply-To: <5256d0b0501061930711f3884@mail.gmail.com>
Peter,
My understanding is frequency hopping is in the firmware but eSCO is
(going to be) in the bluez stack.
Brad
Peter Robinson wrote:
>>and again, the development files from the AO library are missing. Check
>>your Fedora Core 3 distribution.
>
>
> as soon as I read this I knew what the problem was.
>
> a up2date -i libao-devel followed by removing the install and
> downloading the CVS version again and it built straight up :-)
>
> Time to do some testing...
>
> Not exactly related but what is the current supported Bluetooth
> version in the Linux stack. Does the stack change at all to support BT
> 1.0, 1.1 or 1.2 or is it all Firmware/Hardware Changes. If support is
> required in the stack what is the current bt version implemented as of
> 2.6.10? In particular wondering about the freq hopping and the voice
> improvements in v1.2
>
> I'll let you know how I go with the Headset.
>
> Regards
> Peter
>
>
> -------------------------------------------------------
> 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
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-01-07 4:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 15:51 [Bluez-devel] btsco under FC3 Bob Gustafson
2005-01-06 17:26 ` Marcel Holtmann
2005-01-07 3:30 ` Peter Robinson
2005-01-07 4:20 ` Brad Midgley [this message]
2005-01-07 3:43 ` Bob Gustafson
[not found] ` <v04020a21be03b42174eb@192.168.49.19>
2005-01-07 6:06 ` Peter Robinson
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 16:21 Bob Gustafson
2005-01-06 15:36 Bob Gustafson
2005-01-06 4:46 Peter Robinson
2005-01-06 7:28 ` Bob Gustafson
2005-01-06 12:24 ` Marcel Holtmann
2005-01-06 14:23 ` Bob Gustafson
2005-01-06 14:51 ` Marcel Holtmann
2005-01-06 15:33 ` Bob Gustafson
2005-01-07 6:15 ` Peter Robinson
2005-01-07 7:14 ` Brad Midgley
2005-01-07 7:19 ` Peter Robinson
2005-01-07 11:08 ` Lars Grunewaldt
2005-01-07 11:01 ` Henryk Plötz
2005-01-07 11:10 ` Lars Grunewaldt
2005-01-08 1:42 ` Peter Robinson
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=41DE0E1B.6000007@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.