From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Broadcom [Fwd: RE: Chipset specification [Fwd: Web Site Feedback/Support Request - Bluetooth - General]]
Date: Mon, 14 Nov 2005 11:12:04 -0800 [thread overview]
Message-ID: <4378E184.9000805@xmission.com> (raw)
In-Reply-To: <4378E03C.90503@gmx.de>
Maik,
I don't think anyone would have a problem with you telling them you're
"with" the bluez group, but I suspect they're asking this way because
they want an NDA signed. That obviously wouldn't be acceptable.
Brad
> My exchange with Broadcom regarding chipset specs. They want "BlueZ" to
> contact them directly. Not that you tried that or anything...
>
>
> -------- Original Message --------
> Subject: RE: Chipset specification [Fwd: Web Site Feedback/Support
> Request - Bluetooth - General]
> Date: Mon, 14 Nov 2005 10:58:43 -0800
> From: Widcomm Support <support@widcomm.com>
> To: Maik Zumstrull <Maik.Zumstrull@gmx.de>
>
> We do not provide such info to 3rd party developers. If Bluez is looking
> for info so that they can use SCO on a Broadcom Bluetooth chipset then
> BlueZ should contact us directly for such info.
>
> -----Original Message-----
> From: Maik Zumstrull [mailto:Maik.Zumstrull@gmx.de]
> Sent: Monday, November 14, 2005 5:07 AM
> To: bt-support@broadcom.com
> Subject: Chipset specification [Fwd: Web Site Feedback/Support Request -
> Bluetooth - General]
>
>
> Thanks for obviously not even reading my message.
>
> I'm retrying with another contact address.
>
> As you can read in my original message, which is included below your
> automated reply, I would very much like to see the programming interface
> specifiction for your Bluetooth chipsets released to the public; or at
> least to the team developing the official Linux Bluetooth protocol
> stack, BlueZ.
>
>
> -------- Original Message --------
> Subject: Web Site Feedback/Support Request - Bluetooth - General
> Date: 14 Nov 2005 11:49:46 -0000
> From: website_feedback_bluetooth@broadcom.com
> To: Maik.Zumstrull@gmx.de
>
> Thank you for your inquiry. Broadcom Corporation acquired WIDCOMM Inc.
> software, which was licensed to various 3rd party companies who bundled
> our software with their Bluetooth devices. Unfortunately, some of these
> companies inadequately left Broadcom's support information in the
> software interface instead of replacing it with their own support
> information.
>
>
>
> Each of these companies customizes the software for their particular
> Bluetooth device therefore our off-the-shelf standard version of the
> software would not work with most 3rd company devices. Please contact
> the manufacturer or distributor of your device to obtain software
> upgrades.
>
>
>
> For your convenience we have gathered contact information for some known
> OEMs of our software:
>
>
>
> * Micro-Star International (MSI): support@msi.com.tw
>
> * Acer: euro_help@acer-euro.com
>
> * Tecom (BT3030): support@tecom.com.tw
>
> * Tecom (BT3030) software upgrades, documentation, and other support go
> to: http://www.tecom.com.tw
>
> * Compaq technical support:
> http://thenew.hp.com/country/us/eng/support.html
>
> * BlueTake (BT100S): http://www.bluetake.com/support.htm
>
> * Epox (BT-GD02 or BT-MD01): support@epox.nl
>
> * Epox, Germany: support@elito-epox.com
>
> * Epox, UK: support@epox-uk.com
>
> * BlueLink (you must first register):
> http://www.wirelessnetworksinc.com/register.php
>
> * Billionton: http://www.billionton.com/english/index.html
>
>
>
> You can also access this information on the Bluetooth End-User Support
> section at:
>
> http://www.broadcom.com/products/bluetooth_supportlinks.php
>
> If this section does not answer your questions please see the
> Bluetooth/WIDCOMM Technical Support section at:
> http://www.broadcom.com/products/bluetooth_support.php
>
>
>
> Regards,
>
> Broadcom Support Team
>
> Name: Maik Zumstrull
> Subject: Web Site Feedback/Support Request - Bluetooth - General Email
> Address: Maik.Zumstrull@gmx.de
>
> Feedback:
> Please release the complete specification of the Broadcom Bluetooth
> chipsets to the authors of the BlueZ Linux Bluetooth stack. At this
> point, important features, e.g. the use of Bluetooth Headsets, are not
> supported by BlueZ with Broadcom HCIs because it is unknown how to
> program the chips.
>
>
>
> I have a broadcom HCI in my laptop computer, but need to use an external
> dongle because SCO mapping can only be done with CSR HCIs under BlueZ at
> this point. According to the developers, this is due to lack of
> cooperation from your side.
>
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-14 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 19:06 [Bluez-devel] Broadcom [Fwd: RE: Chipset specification [Fwd: Web Site Feedback/Support Request - Bluetooth - General]] Maik Zumstrull
2005-11-14 19:12 ` Brad Midgley [this message]
2005-11-14 20:22 ` Robert Siemer
2005-11-14 20:33 ` Maik Zumstrull
2005-11-22 11:34 ` Marcel Holtmann
2005-11-14 20:35 ` 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=4378E184.9000805@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).