public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Error messages from hid2hci
Date: Thu, 02 Dec 2004 07:55:54 +0100	[thread overview]
Message-ID: <1101970554.15615.63.camel@pegasus> (raw)
In-Reply-To: <qszis7lv8ho.fsf@mspacman.gpcc.itd.umich.edu>

Hi Scott,

> After upgrading my D-Link DBT-120 with the Apple firmware, I have to
> use hid2hci to put it in hci mode.  hid2hci usually seems to work
> fine, except it prints out an error message:
> 
> If I plug the device directly in, I get:
> 
>   Switching device 0a12:1000 to HCI mode failed (Protocol error)
> 
> Through a hub, I get:
> 
>     Switching device 0a12:1000 to HCI mode failed (Invalid or incomplete multibyte or wide character)
> 
> This is with a very recent Bluetooth kernel from BK, bluez-libs-2.10,
> and bluez-utils-2.10

I think we should not print out certain error codes, because the switch
into HCI will be still succeed. However the error is correct, because
the device resets before the URB is completed.

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-12-02  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02  0:39 [Bluez-users] Error messages from hid2hci Scott W Gifford
2004-12-02  6:55 ` 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=1101970554.15615.63.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