All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Renouf <tpraplix.vger@botech.co.uk>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: add dbus api to set class of device?
Date: Wed, 28 Jul 2010 17:59:04 +0100	[thread overview]
Message-ID: <20100728165904.GA9840@aplixcorp.com> (raw)
In-Reply-To: <1280335558.2621.97.camel@localhost.localdomain>

Hi Marcel

> I did mention before that JSR82 is the most stupid Bluetooth API that I
> have seen so far, didn't I? Personally I wouldn't even bother with JSR82
> and give up right away. It is really a pointless API.

Unfortunately I have to bother with it as our customers are device
manufacturers who are willing to pay for MIDP with JSR82 support. :-(

> In BlueZ the services bits of the class of device settings are modified
> dynamically based on the registered SDP service records. So you don't
> have to do anything. Just register the right SDP service record with the
> proper UUID and it will take care of this automatically.

Yes, I saw that in update_adapter_svclass_list. I guess the problem is
that JSR82 lets an app decide to set the "wrong" bit, and the
conformance tests test that functionality.

So if I did a patch along the lines I was suggesting, and submitted it
here, would it be rejected on the grounds that it is not needed for any
"sensible" functionality ?

Thanks.

-tpr

  reply	other threads:[~2010-07-28 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 15:33 add dbus api to set class of device? Tim Renouf
2010-07-28 16:45 ` Marcel Holtmann
2010-07-28 16:59   ` Tim Renouf [this message]
2010-07-28 17:40     ` 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=20100728165904.GA9840@aplixcorp.com \
    --to=tpraplix.vger@botech.co.uk \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.