public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dark Shadow" <shadowofdarkness@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Trouble loading firmware with bcm203x
Date: Sun, 17 Dec 2006 21:24:10 -0700	[thread overview]
Message-ID: <231dafb50612172024r39a509bbncd5b98568063ce22@mail.gmail.com> (raw)
In-Reply-To: <1166358018.6557.17.camel@aeonflux.holtmann.net>

On 12/17/06, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi,
>
> > Could this be my problem.
> > http://web.archive.org/web/20050310013858/www.holtmann.org/linux/bluetooth/usb.html
> >
> > It says
> > Device       usb-ohci                   usb-uhci      uhci
> > BCM 2033 no firmware load     works            works but slow
> >
> >
> > I have looked and all my usb ports on my laptop and dekstop are ohci.
> > I have found a really old laptop that has a uhci port but none of my
> > live disks work because it is decreped hardware so when I find one I
> > will see if the firmware loads better.
>
> no it is not your problem. You simply don't have a BCM2033 and that was
> the only one needed the firmware download.
>
> Yours looks like an HID proxy mode device it might need some extra love
> to switch it from HID into HCI mode. However that is always a magic
> sequence and for some devices the reset=1 is fully enough. Some others
> need some crazy init command. I prefer you try a clean vanilla kernel
> and check if the /proc/bus/usb/devices shows a Bluetooth device.
> Otherwise you have to sniff what Windows is doing to init your device
> and it would be good if someone sends me one of these to have it in my
> device library.
>
> Regards
>
> Marcel
>
I will compile a vanilla kernel to test. I unfortunately can't test in
Windows as I started single booting Linux years ago.

I really think mine needs a firmware upgrade because it has worked
before after running modprobe bcm203x. One time using firmware from
your package and one time I took a file called frmUpgrade.sys from the
windows driver cd renamed it BCM2033-MD.hex and ran it through your
hex2bin program to get a bin and used that. The frmUpgrade.sys

-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-12-18  4:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16  6:11 [Bluez-users] Trouble loading firmware with bcm203x Dark Shadow
2006-12-16  7:57 ` Arthur
2006-12-16  8:15   ` Dark Shadow
2006-12-16  9:44   ` Marcel Holtmann
2006-12-16  8:50     ` Arthur
2006-12-16  9:14     ` Dark Shadow
2006-12-16 20:56       ` Dark Shadow
2006-12-17 12:20         ` Marcel Holtmann
2006-12-18  4:24           ` Dark Shadow [this message]
2006-12-18  7:34             ` Dark Shadow
2006-12-19 18:55               ` Dark Shadow
2006-12-27  6:01                 ` Dark Shadow

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=231dafb50612172024r39a509bbncd5b98568063ce22@mail.gmail.com \
    --to=shadowofdarkness@gmail.com \
    --cc=bluez-users@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