All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] getting bluetooth v1.2, success report
Date: Tue, 29 Mar 2005 12:22:49 +0200	[thread overview]
Message-ID: <42492C79.700@gmx.ch> (raw)
In-Reply-To: <200503291156.57781.cijoml@volny.cz>



Michal Semler wrote:
> Dne út 29. března 2005 10:07 Marco Trudel napsal(a):
> 
>>Hello
>>
>>I downloaded the Bluetooth Firmware Updater from apple, putted my dongle
>>into the apple and run the updater. everything went perfectly fine...
>>i now have Build 1586 (HCI 18.2) and Bluetooth 1.2... nice!
>>
> Download it from dongle via btdfu - then it should have right timing.

I have no idea what you mean with this...


>>If someone has no mac operating system and is interested in the
>>GenericCSR.dfu, I can email it.
> 
> We all have it :)

no. not everyone has it.
maybe you already have it...


>>My last questions (hopefully) regarding this topic now are:
>>- What is dangerous about updating the dongle?
>>the procedure itself? only the linux btdfu tool (secure with mac)?
> 
> you can destroy it, but now are all dongles very cheap

So the procedure itself is dangerous...


>>- Widcomm delivers update-software too, will/should this work too with the
>>GenericCSR.dfu?
> 
> We know nothing about this software - it should be better then Marcel's btdfu, 
> coz they have specifications


>>- I now have to run hid2hci every time after I plug the dongle in (thanks
>>for the info marcel). What is this exactly doing, why is it necessary?
> 
> yes, it is

I know that it is, I wrote that.
My question was why it is necessary and what it's doing...


>>- doing hid2hci I get:
>>Switching device 0a12:1000 to HCI mode failed (Invalid or incomplete
>>multibyte or wide character)
>>but everything's fine after that. is this a problem? why the error?
> 
> error somewhere in usb subsystem - contact usb guys

regards
Marco

Content Security by MailMarshal


-------------------------------------------------------
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

  reply	other threads:[~2005-03-29 10:22 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
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 [this message]
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=42492C79.700@gmx.ch \
    --to=mtrudel@gmx.ch \
    --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 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.