November 2009 - Bluetooth-dev

Broadcom BT Performance 20x slower than Cambridge Silicon
by Antonio Iglesias 04 Nov '09

04 Nov '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com Packet logger comparison.pdf

1 0

Re: How to release or disable SCO audio connection
by Peter Sichel 03 Nov '09

03 Nov '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com On Sep 28, 2009, at 9:30 PM, Peter Sichel wrote: Thanks! - Peter Sichel Sustainable Softworks _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… My application (Phone Amego) connects with a Bluetooth phone using the Handsfree Profile for the purpose of CallerID and dialing. I've noticed some phones establish an audio connection with the Mac by default such that the speaker and microphone on the phone itself is disabled. I'm trying to figure out how to disable or close this audio connection. After further study, I understand SCO connections are established by the Link Manager which resides within the Bluetooth Module or controller on modern Macs. The HCI (Host Controller Interface) layer provides the interface to the Bluetooth Module, but I haven't found a published API to work with the HCI layer directly. Apple's Packet Logger is able to capture HCI events and shows the SCO connection setup and succeeding stream of SCO receive packets, so there is at least an internal API for this. If anyone knows of some sample code or other resources for working at the HCI layer, I sure could use a pointer. This email sent to site_archiver(a)lists.apple.com

1 0

Re: IOBluetooth.framework 64 bits support on 10.5
by Craig Dooley 02 Nov '09

02 Nov '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: IOBluetooth.framework 64 bits support on 10.5
by Camille Troillard 02 Nov '09

02 Nov '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=VuLWpmm4VcGaAvcA779H9ep9lZiyM9R0LfiUcByNO54=; b=nr9nlApsdO2rG+2K4MrbkNOJAFJpaxK7PCr98SuYwqWX8YXGLZgOUsTompJNBrodv/ vEM3bU+P9B0KFLuvDywA90yCI8Z8mJ/sfAd96y8xtk40t3GDq7YB4XLOzSxwJ5ZBIs9O iv3ep2xiTkg+8v6/6h/LRZ36a9tfnzhFVa3LU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=Kui5Ifgh4esOuqc3cMc7uZhdMTzqD09diFN7vtMbT+ZwRcxlo9PRjNaelzhzDRjv36 dNa3esYDpVSICdA0+MBPsKBSyb+8OMCIGpdJ/kg3FYzXKMiaQR1MjyLXJ6+PPpMeJ1oG BDAj34VYELgTuwHiEoFZCoJ6JlhJV3rh3xCvU= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE:IOBluetooth.framework 64 bits support on 10.5
by David Christmass 01 Nov '09

01 Nov '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1257080146; bh=bXv/47OM5OTASFlQuJkPl/y3+Kc44ZZw/rColaUSmmA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3621b9fhFZO7A7Ueqn+V5dFy+QNP+yP5N6X1ioJMwI5wc231qqmkVPa3ejlsD3h3KadhDTbI1vos1WHIcJB/I1QfSjo0vk6ZdwMzfrDjiU1cKmNE7aB6CzJXh9qmP7SFlkKTrVLCNKaRRVRTimgAbtjQKK6y+hovcZNDo26XZvg= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AxsmvPG9KK5b26jswA72B7Be1RE7+VOpCNlw5LXX74G0QLN4w4p/0Wy5tS0Y5YSPsYrrMyASVIBemjwnGErl9bS0GFsvDyOXNZF1Z5jk/6ynC5i3iTahUJInDiiEGupP1bzJW9cReVfsF657QX0zB8pZktoGgPR7G0k5Clo/53w=; Hi Camille, It has been the tradition in the past to build Applications which are platform specific. 68k coding for Moto chips differed to PPC builds and differed to CFM which could allow PPC to run 68K code and creating a Fat binary allows for integration of all systems of their kinds within time slots, beyond PPC integration is abbridged with Carbon, and later Cocca for want of a better word interpeter layers which patch code to machine specific platform, beyond this, when intel showed up, the same interpreter traditions existed in Rosseta, describing the platform you are building for exactly in the build processes will ensure that coverage exists for the platforms you are choosing to support. You might be forced to start from 32bit addressing perspectives because 64 bits are bigger words, to achieve cross compliance. Fitting 64bit on 32 bit words, well how would you stuff a small jar with so many goodies: two pints into a pint pot so to speak? You might have to think about compression, and even some kind of software based floating point numerator or FPU emulator to get the 64 bits understood by 32 bit systems: that involves additional provisions of interfacing to work on 32 bit systems, like a control panel for example or something, and suitable licensing for distribution arrangements. One the one hand building down for up is not going to give the later platforms full capacity, and building up for down is going to involve expanding operational system facilities in some form. My suggestion for you would be a multiple build process for dedicated systems, but that is what you are trying to avoid, I read. The hinderance is the material science of having software perform hardware tasks, which slows things down. That is where your at, and the choices you have to make. David _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0