Re: Broken SDP parsing?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


-- 
Luiz Augusto von Dentz
Engenheiro de Computação
--
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

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux