From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcitool: bug in printing names of class of device
Date: Fri, 29 Sep 2006 13:43:29 +0200 [thread overview]
Message-ID: <1159530209.6131.22.camel@localhost> (raw)
In-Reply-To: <451D057A.1070507@sentivision.com>
Hi Artur,
> In our company we've designed BT remote controller device. We set class
> of device to 0x5cc (Major class: Peripheral, Minor class: Combo
> keyboard/pointing device + Remote control). On Windows it is recognized
> correct (icon and description), but on Linux (bluez-utils 3.4) "hcitool
> scan --class --flush" prints "Device class: Invalid (0x005cc)".
>
> I've found that only devices with major class < 5 are recognized
> correctly. This is because is bug in hcitool.c in function cmd_scan():
>
> if ((cls[1] & 0x1f) > sizeof(*major_classes))
> ^^^^^^^^^^^^^^^^^^
> this is always sizeof(char**) and on 32bit machine is 4!
> It should be:
> sizeof(major_classes) / sizeof(char*),
thanks for looking into this. This is has been fixed in the CVS now.
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
prev parent reply other threads:[~2006-09-29 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 11:37 [Bluez-devel] hcitool: bug in printing names of class of device Artur Wodejko
2006-09-29 11:43 ` 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=1159530209.6131.22.camel@localhost \
--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