From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Report of working dongle: IOGear GBU311 and question
Date: Tue, 01 Mar 2005 09:44:39 +0100 [thread overview]
Message-ID: <1109666679.17256.129.camel@pegasus> (raw)
In-Reply-To: <4223E423.4030603@cloutier-vilhuber.net>
Hi Lars,
> I can happily report that my new IOGear GBU311 works under stock SuSE
> 9.2 (connections tested with Palm T3 and Sony-Ericsson T610, using
> OBEX-FTP, OBEX-transfer, DUN).
>
> However, I am curious: when plugging it in, the logs show a USB *HUB*,
> and registers keyboard and mouse drivers. Is this something SuSE
> specific, something driver-specific? Is SuSE misconfigured? or what does
> it mean when the USB dongle registers as a keyboard/mouse?
the registration as mouse and keyboard is fine, but actually this device
should only start working with a recent 2.6.11-rc5 kernel. What does the
content of /proc/bus/usb/devices shows you? Also show us "hciconfig -a".
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-01 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050228143635.6E7668844B@sc8-sf-spam1.sourceforge.net>
2005-03-01 3:40 ` [Bluez-users] Report of working dongle: IOGear GBU311 and question Lars Vilhuber
2005-03-01 8:44 ` Marcel Holtmann [this message]
2005-03-01 15:06 ` Fredy P.
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=1109666679.17256.129.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