public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ortwin Glück" <odi@odi.ch>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] boot vs. report protocol
Date: Wed, 21 Feb 2007 15:50:36 +0100	[thread overview]
Message-ID: <45DC5C3C.4070002@odi.ch> (raw)

Hi,

In net/bluetooth/core.c there is:

	if (session->input) {
		hidp_send_ctrl_message(session,
			HIDP_TRANS_SET_PROTOCOL | HIDP_PROTO_BOOT, NULL, 0);
		session->flags |= (1 << HIDP_BOOT_PROTOCOL_MODE);

		session->leds = 0xff;
		hidp_input_event(session->input, EV_LED, 0, 0);
	}


which effectively sets the boot protocol for all input devices. To
support some scroll wheel mice they need to be put into report mode, though:

	if (session->input) {
		hidp_send_ctrl_message(session,
			HIDP_TRANS_SET_PROTOCOL | HIDP_PROTO_REPORT, NULL, 0);

		session->leds = 0xff;
		hidp_input_event(session->input, EV_LED, 0, 0);
	}

I assume that's safe. Solaris for instance, initializes all devices in
report mode by default. It never even tries boot protocol.

Maybe it would make sense to have a userspace interface to switch the
mode from within hidd.


-------------------------------------------------------------------------
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

             reply	other threads:[~2007-02-21 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 14:50 Ortwin Glück [this message]
2007-02-21 15:08 ` [Bluez-devel] boot vs. report protocol Marcel Holtmann

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=45DC5C3C.4070002@odi.ch \
    --to=odi@odi.ch \
    --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