From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] getting bluetooth v1.2, success report
Date: Tue, 29 Mar 2005 12:20:21 +0200 [thread overview]
Message-ID: <200503291220.21937.cijoml@volny.cz> (raw)
In-Reply-To: <1112091360.9016.70.camel@pegasus>
Dne =FAt 29. b=F8ezna 2005 12:16 Marcel Holtmann napsal(a):
> Hi Marco,
>
> > 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)?
>
> this depends on. Not all firmwares will fit into every dongle. However
> we discussed this quite often and there is also a statement from a CSR
> in the mailing list archive about it.
>
> > - Widcomm delivers update-software too, will/should this work too with
> > the GenericCSR.dfu?
>
> Never tested, but in general it should do the same job.
>
> > - I now have to run hid2hci every time after I plug the dongle in (than=
ks
> > for the info marcel). What is this exactly doing, why is it necessary?
>
> You get a USB dongle with HID proxy support. Look at the mailing list
> archive for more details on what this is.
>
> > - 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?
>
> I thought this was fixed, but in general you can ignore the error.
It wasn't fixed. I see this error too.
>
> Regards
>
> Marcel
Michal
>
>
>
>
> -------------------------------------------------------
> 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=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
=2D-=20
S pozdravem
Michal Semler
-------------------------------------------------------
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-29 10:20 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
2005-03-29 10:30 ` Michal Semler
2005-03-29 10:16 ` Marcel Holtmann
2005-03-29 10:20 ` Michal Semler [this message]
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=200503291220.21937.cijoml@volny.cz \
--to=cijoml@volny.cz \
--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