On Mon, 2009-03-09 at 10:08 -0300, Luiz Augusto von Dentz wrote: > Hi Bastien, > > On Sun, Mar 8, 2009 at 11:46 AM, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > > On Fri, 2009-03-06 at 01:00 +0000, Bastien Nocera wrote: > >> Heya, > >> > > <snip> > >> The first 2 chars in the IEEE1284 ID are supposed to be the length of > >> the string. This should enable me to make the CUPS backend's discovery > >> work again. > > > > This isn't quite enough it seems. > > > > >From DiscoverDevices on org.bluez.Device: > > <attribute id="0x0300"> > > <text value="" /> > > </attribute> > > > It may happen that bluetoothd and sdptool doesn't really share the sdp > xml parsing code. So perhaps we need to replicated your fix on > bluetoothd too or just make bluetoothd to use what you have done for > sdptool. Both use the code in common/sdp-xml.[ch] and convert_sdp_record_to_xml() in particular, which is why it makes no sense to me... I double-checked by adding some debug to convert_raw_data_to_xml() and the string for the attribute I'm interested in is empty, so it must be a problem parsing the raw data from the device, or there's something that strips this value somewhere in bluetoothd... -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
