From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] getting bluetooth v1.2
Date: Mon, 28 Mar 2005 19:48:20 +0200 [thread overview]
Message-ID: <1112032100.9016.42.camel@pegasus> (raw)
In-Reply-To: <1112031386.30560.6.camel@lynx.auton.cs.cmu.edu>
Hi Adam,
> Yes, the "if you are lucky" part is very important. The one-line patch
> may look simple, but it took a LONG time of experimenting to figure it
> out!
you can also make your dongle unusable when you try the wrong firmware
or if the btdfu aborts at the wrong time, because of a timeout.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-28 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 16:51 [Bluez-users] getting bluetooth v1.2 Marco Trudel
2005-03-27 17:08 ` Marcel Holtmann
2005-03-28 11:47 ` Marco Trudel
2005-03-28 12:04 ` Marcel Holtmann
2005-03-28 12:19 ` Marco Trudel
2005-03-28 13:15 ` Marcel Holtmann
2005-03-28 16:18 ` Marco Trudel
2005-03-28 17:21 ` Marcel Holtmann
2005-03-28 17:36 ` Adam Goode
2005-03-28 17:48 ` Marcel Holtmann [this message]
2005-03-29 8:07 ` [Bluez-users] getting bluetooth v1.2, success report Marco Trudel
2005-03-29 9:56 ` Michal Semler
2005-03-29 10:22 ` Marco Trudel
2005-03-29 10:30 ` Michal Semler
2005-03-29 10:16 ` Marcel Holtmann
2005-03-29 10:20 ` Michal Semler
2005-03-28 15:49 ` [Bluez-users] getting bluetooth v1.2 Adam Goode
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=1112032100.9016.42.camel@pegasus \
--to=marcel@holtmann.org \
--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