Lines Matching refs:PTP

38   maintained. libmtp tracks the PTP implementation in
169   gphoto2 (which can also talk PTP/MTP) is taking over the device
187 * Generic MTP/PTP disconnect misbehaviour: we have noticed that
190   by opening a PTP session to any MTP device, whenever it is
207   with devices that do not correctly handle closing PTP/MTP
261   Error 2: PTP Layer error 02ff: get_device_unicode_property(): failed
326   multiple PTP packages in a single transaction.)
334   gives an error in opening the PTP session. Apparently you can
434 Device sniffs are an easy read since the PTP/MTP protocol
438 PTP REQEUST:
514 transaction. The bulk transactions contain all the PTP/MTP layer
533 * 0x01 [0000 0001] : PTP debug
711 > PTP: Opening session
786 PTP/MTP devices does not actually contain "files", they contain
804 "real" file system. In PTP/MTP devices it is often not even possible,
814 Then the issue that in PTP/MTP it is legal for two files to have
833 file system like PTP/MTP. (See further below.)
863 requires it. The reason is that PTP/MTP is a transactional file system
874 So this is an inherent limitation of the PTP/MTP protocol.