Re: [PATCH BlueZ 2/3] thermometer: Fix handling of missing Temperature Type

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

 



Hi Anderson,

2012/2/14 Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx>:
> According to HTS 1.0, it is not mandatory to have Temperature Type
> information (the Characteristic and the indication field are both
> unconditionally optional).
>

I'm afraid there is an slight conceptual error in this patch.
According to HTS 1.0, there are two *exclusive* methods to provide the
temperature type to a Colector: either by using a characteristic type
or providing it as a field within the measurement. This doesn't mean
that the temperature characteristic or field type are both
unconditionally optional because one of them *MUST* be used, but not
both of them at the same time. So there will always be a method to get
the temperature type either if it's a static value (characteristic
type) or a non-static value (temperature field). Health Thermometer
Service[3.2] ,[3.1] &  Health Thermometer Profile [4.7]


Regards.
Santiago
--
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