From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Presentation slides are online
Date: Mon, 28 Jun 2004 16:02:12 +0200 [thread overview]
Message-ID: <1088431331.4614.6.camel@pegasus> (raw)
In-Reply-To: <20040628135038.GA28640@gmx.net>
Hi Nicholas,
> You now have some experience based data, which dongles accept the signed
> apple hciproxy firmware and which one render unusable?
the D-Link revision B3 and the Allnet ALL1575 seem to work fine. There
was another one that I've tested successfully on the LinuxTag, but I
can't remember from what manufacturer it was. The revision B4 of the
D-Link is not working at the moment. Looks like an USB chip or flash
timing problem.
Some other dongles can be updated with the same file, but in the case of
only 4 Mbit flash you will get HCI 16.14 firmware and not the HCI 18.1
with HID proxy support.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-06-28 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 9:03 [Bluez-users] Presentation slides are online Marcel Holtmann
2004-06-28 13:50 ` Nicholas A. Preyss
2004-06-28 14:02 ` Marcel Holtmann [this message]
2004-06-28 14:40 ` Bc. Michal Semler
2004-06-28 23:27 ` Marcel Holtmann
2004-06-28 16:56 ` Diego Liziero
2004-06-28 23:28 ` Marcel Holtmann
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=1088431331.4614.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nalp@gmx.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