From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 28 Jul 2010 17:59:04 +0100 From: Tim Renouf To: Marcel Holtmann Cc: linux-bluetooth@vger.kernel.org Subject: Re: add dbus api to set class of device? Message-ID: <20100728165904.GA9840@aplixcorp.com> References: <20100728153323.GA9410@aplixcorp.com> <1280335558.2621.97.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1280335558.2621.97.camel@localhost.localdomain> List-ID: 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