From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hid2hci fails: broken pipe
Date: Mon, 19 Feb 2007 18:54:19 +0100 [thread overview]
Message-ID: <1171907659.26567.29.camel@violet> (raw)
In-Reply-To: <45D9E0ED.8090700@yahoo.com.au>
Hi Mat,
> My Digitus DN-3008 arrived in the post today, so I tried it out. I
> managed to get it to the same level of workingness as my DBT-120, i.e.,
> I can use my bluetooth mighty mouse with the thing, if I first run
> "hidd" manually. The next step is to switch it into HID mode with
> hid2hci. But this is failing with the error message:
>
> aeon:~# hid2hci -1
> Switching device 0a12:0001 to HID mode failed (Broken pipe)
>
> Can anyone suggest why this isn't working? What pipe? What's it
> talking to a pipe for in the first place?
it doesn't mean that it actually failed to switch the adapter. It might
have simply worked. The error messages from the USB subsystem are kinda
strange, but somehow expected since the device will disconnect from the
bus.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-19 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 17:39 [Bluez-devel] hid2hci fails: broken pipe bluez.mexon
2007-02-19 17:54 ` Marcel Holtmann [this message]
2007-02-19 19:26 ` bluez.mexon
2007-02-21 12:13 ` Marcel Holtmann
2007-02-22 5:47 ` bluez.mexon
2007-02-22 6:52 ` Marcel Holtmann
2007-02-23 6:10 ` bluez.mexon
2007-02-23 7:07 ` Marcel Holtmann
2007-02-23 12:04 ` bluez.mexon
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=1171907659.26567.29.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@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