From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BCM2035 BROKEN_ISOC?
Date: Tue, 19 Apr 2005 23:43:35 +0200 [thread overview]
Message-ID: <1113947015.2469.73.camel@pegasus> (raw)
In-Reply-To: <000a01c54527$eaaec310$0100a8c0@hppav>
Hi Oliver,
> BTW this device is commented in the list.
>
> Does it needs also to load firmware as BCM203x ?
>
> I saw the product and vendor ID for bcm2035 in the hci_usb driver but not in
> the complent bcm203x.
this one has the firmware in a flash storage.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-04-19 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 6:15 [Bluez-devel] BCM2035 BROKEN_ISOC? Suriyan Laohaprapanon
2005-04-19 10:40 ` Marcel Holtmann
2005-04-19 21:36 ` Oliver
2005-04-19 21:43 ` Marcel Holtmann [this message]
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=1113947015.2469.73.camel@pegasus \
--to=marcel@holtmann.org \
--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