From: Gerhard Killesreiter <gerhard@killesreiter.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: broadcom in disguise...
Date: Thu, 25 May 2006 17:53:00 +0200 [thread overview]
Message-ID: <4475D2DC.304@killesreiter.de> (raw)
In-Reply-To: <4471DE09.5050405@xmission.com>
Brad Midgley wrote:
Hi Brad!
>>> A couple of manufacturers switched from csr to broadcom around the time
>>> bluecore4 and the other edr chips came out. Not sure why.
>>>
>>>
>> I find this highly annoying. I have written to typhoon and asked for an
>> explanation.
>>
>
> this is unfortunately a fairly standard practice across the computer
> hardware industry.
>
If they'd at least update their docs...
Anyway, I got an anwer from them (didn't really expect one)!
They claim that the chip can be addressed by the broadcom driver but
would definitly be a CSR chip.
Does that make any sense to anybody?
> bluetake has done the switcheroo as well but currently their BT007EX is
> our only source for a class 1 bluecore4 dongle so we like them again.
>
>
>>> If you've used the adapter in windows
>>> for sco audio
>>> then it might change some nvram settings.
>>>
>
> I really don't know much about the broadcom models or even if they do
> have nvram settings for this. It's possible they ship something that
> can't do sco out of the box but will do it after the windows driver
> initializes it. That's my "all out of ideas" suggestion.
>
Guess I will need to take it to a windows box then.
Cheers,
Gerhard
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-25 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 8:24 [Bluez-devel] SCO for non-CSR based devices? Gerhard Killesreiter
2006-05-11 14:20 ` Brad Midgley
2006-05-11 15:31 ` Peter Wippich
2006-05-10 14:53 ` Gerhard Killesreiter
2006-05-11 18:00 ` [Bluez-devel] documentation for a newbie Özkan Gümüs
2006-05-11 18:35 ` Jan Benes
2006-05-22 0:28 ` broadcom in disguise... (was: [Bluez-devel] SCO for non-CSR based devices?) Gerhard Killesreiter
2006-05-22 4:40 ` [Bluez-devel] Re: broadcom in disguise Brad Midgley
2006-05-22 9:49 ` Gerhard Killesreiter
2006-05-22 15:51 ` Brad Midgley
2006-05-25 15:53 ` Gerhard Killesreiter [this message]
2006-05-29 6:49 ` [Bluez-devel] " Brad Midgley
2006-05-29 11:40 ` Gerhard Killesreiter
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=4475D2DC.304@killesreiter.de \
--to=gerhard@killesreiter.de \
--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.