_PTPCanonEOSDeviceInfo(3)

🎀 NAME 🎀

okay bestie, welcome to the _PTPCanonEOSDeviceInfo(3) manual page — that’s the title and the manual name folded right up in here, from the Library Functions Manual. This page is literally about _PTPCanonEOSDeviceInfo and the data fields listed below. No cap, that’s the whole name section. 💖

✨ SYNOPSIS ✨

🦋 Data Fields 🦋

Here’s the lineup, exactly as the page gives it:

uint32_t EventsSupported_len
uint32_t * EventsSupported
uint32_t DevicePropertiesSupported_len
uint32_t * DevicePropertiesSupported
uint32_t unk_len
uint32_t * unk

And here’s every single one, spelled out so you don’t miss a character:

• uint32_t EventsSupported_len — a uint32_t field, and the name is literally EventsSupported_len.
• uint32_t * EventsSupported — a pointer to uint32_t, named EventsSupported.
• uint32_t DevicePropertiesSupported_len — a uint32_t field, with all that DevicePropertiesSupported_len energy.
• uint32_t * DevicePropertiesSupported — a pointer to uint32_t, named DevicePropertiesSupported.
• uint32_t unk_len — a uint32_t field named unk_len.
• uint32_t * unk — a pointer to uint32_t, named unk.

That’s six fields total, bestie — the _len trio and their pointer partners. Slay. 💅

💖 Author 💖

This page didn’t get hand-written by a person in the group chat — it says: Generated automatically by Doxygen for libmtp from the source code. Iconic Doxygen behavior, honestly. 🫶

That’s the whole page, bestie. Footer energy: libmtp, Version 1.1.23 — and there’s no separate date line on this page, so that’s the sign-off tea. Byeeee 💋✨